Well you just can't do that, that's indeed a circular dependency.
Either you merge them, or you extract the common logic to a 3 module.
(The concept of "Maven module" totally unrelated to that of "Magnolia
module". One "jar" can contain 9737 magnolia modules, and not all jars
deployed in magnolia must be magnolia modules)
-g
On Mar 31, 2009, at 4:31 PM, Matteo Pelucco wrote:
Hi all, I need a little help to configure maven.
We use Dynamic Web Project on Eclipse to run Magnolia and we attach
to that project our modules jar (right click, module dependancies).
We have 1 module parent pom, called "parent".
Every module declare "parent" as parent project.
I have 2 modules: A and B.
A should uses some B's classes, B should uses some A's classes.
I can not say to A's pom: depends on B and viceversa, to avoid
circular dependencies.
The solution should use <modules> declaration on "parent", but it
seems not to be enough. After doing that, what should I do?
Hope it is clear..
Matteo
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
