Further confusing use case:
Parent
Project A 1.0 - Jar
Project B 1.0 - Jar -> depends on A
Project C 1.0 - War -> depends on B only but gets A transitively
Even though A B and C are all siblings. Because A is brought in
transitively, it has the fully decorated name with the version but B
does not. If I depend directly on A and B, then both A and B loose the
version.
-----Original Message-----
From: Brian E. Fox [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 28, 2006 4:08 PM
To: Maven Developers List
Subject: some major issues with reactors and dependency handling
I've seen some major issues with the way maven handles dependencies in a
multi project setting. Consider the following project:
parent
Project A 1.0 - Jar
Project B 1.0 - War
If I build the parent, when project A is included in the war, it's
included as project-a.jar. If I build Project B, then the jar is
included as project-a-1.0.jar
This is just one example of some weird issues, I know that people have
mentioned problems similar to this with compiling. Maven is all about
reproducibility, but this one clearly breaks that because the produced
artifact is completely dependant on if it was build standalong or part
of a reactor. Can any of the maven developers explain what was attempted
to be solved by this and if/when we might see it get fixed.
Some jiras I can see that are related to this:
http://jira.codehaus.org/browse/MWAR-7
http://jira.codehaus.org/browse/MOJO-286
I don't yet see an actual issue related to this, just the side effects
of it on the WAR and Dependency plugin. Should I create a separate one
in the MNG group?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
