Hi,
My application is divided into several transitively dependent
projects. Here's a simplified example:
libA.jar
libB.jar depends on libA.jar
libC.jar depends on libB.jar
appA.jar depends on libC.jar
appB.jar depends on libC.jar
Each of these JARs is in its own POM, which specifies the dependencies
stated above. I'm actively developing all of these projects
simultaneously, so I want Maven to compile the source code of any
dependency that's out-of-date (just like Ant's <javac> task). For
example, if I'm testing appA, and I change something in libB, I should
only have to run "mvn compile" on the appA project, since Maven knows
that appA depends transitively on libB. Unfortunately, this doesn't
happen. I have to manually figure out which dependent project is out
of date, compile it, and then compile appA. Needless to say, this is
tedious and time-consuming.
I've been reading that modules are the solution to this problem.
There's a write-up about them here:
http://docs.codehaus.org/display/MAVENUSER/Multi-modules+projects
However, the solution in the write-up doesn't seem like it would work,
at least not in my situation. It says I have to specify libC's parent
module, but which parent do I choose? As you can see above, it has two
parents: appA and appB. How can I reconcile this? Thanks,
Trevor
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
