build - Maven multi module circular dependency -


i have multi module maven project these dependencies : module-gui -> module-business

each module has own specific domain object :
gui module => view domain objects
business module => business domain objects.

for business logic have map view objects gui module business domain objects business module business module !
gives me trouble because cause maven circular dependency.
module-gui depends on module-business can't add dependency on module-gui module-business have access on gui domain objects.

i move domain objects common module break circle dependency think it's better put objects in right module (view objects view module , business objects business module) maybe i'm totally wrong :).

do know if there practice kind of problem ?

you should use maven multi-module when want execute same action, compile example, on many projects.

if want compile application tiers in maven multi-module project have find trade-off between module consistency , build automation.

so think, in given architecture, solutions compromise: declaring compiling dependency, , avoiding circular ones, lets leverage maven reactor sort compilation modules leaving free sorting them.

on other hand might revise architecture decoupling view , business tier using controller tier transform view domain objects business domain objects (view --> business), , transform business domain objects view domain objects (view <-- business).


Comments

Popular posts from this blog

get url and add instance to a model with prefilled foreign key :django admin -

android - Keyboard hides my half of edit-text and button below it even in scroll view -

css - Make div keyboard-scrollable in jQuery Mobile? -