# Cyclic Dependency on 2 modules

**URL:** <https://talk.openmrs.org/t/cyclic-dependency-on-2-modules/19334>\
**Category:** Development\
**Created:** [August 7, 2018, 2:34pm UTC](https://talk.openmrs.org/t/cyclic-dependency-on-2-modules/19334 "2018-08-07T14:34:55Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![meizzz](https://talk.openmrs.org/user_avatar/talk.openmrs.org/meizzz/32/7168_2.png) [@meizzz](https://talk.openmrs.org/u/meizzz)\
**Post date:** [August 7, 2018, 2:34pm UTC](https://talk.openmrs.org/t/cyclic-dependency-on-2-modules/19334/1 "2018-08-07T14:34:55Z")

</div>

Hello everyone,

My team and i were developing 2 modules, for example, the module A and the module B, and the module B has a dependency of the module A. But now we arrived at time when we need a dependency on module A to have a dependency of the module B… Can we have cyclic dependency on modules on openmrs?

maybe @dkayiwa knows something about this?

Best Regards

---

<div class="post-metadata">

**Author:** ![wyclif](https://talk.openmrs.org/user_avatar/talk.openmrs.org/wyclif/32/19607_2.png) [@wyclif](https://talk.openmrs.org/u/wyclif)\
**Post date:** [August 7, 2018, 8:26pm UTC](https://talk.openmrs.org/t/cyclic-dependency-on-2-modules/19334/2 "2018-08-07T20:26:10Z")

</div>

My thinking is that if module B depends on A, and for some reason module A needs to use a feature from B, I would possibly move the feature to B if it’s not tightly coupled to module A.

---

<div class="post-metadata">

**Author:** ![meizzz](https://talk.openmrs.org/user_avatar/talk.openmrs.org/meizzz/32/7168_2.png) [@meizzz](https://talk.openmrs.org/u/meizzz)\
**Post date:** [August 8, 2018, 11:42am UTC](https://talk.openmrs.org/t/cyclic-dependency-on-2-modules/19334/3 "2018-08-08T11:42:54Z")

</div>

yeah, you prolly rigth, i will move everything to one module

Best Regards