Affects Version/s: 3.0.1, 3.0.2, 3.0.3
Fix Version/s: 3.0.4
Environment:Fedora Linux, Sun JDK 1.6.0_24, MacOS X 10.6.7, AppleJDK 1.6.0_24
Number of attachments :
See the attached build logs "build_failed.log" and "build_succesful.log". They were both created from using the attached POM. The only difference is that in the successful build the dependency
is moved to the very top of the dependency list. When diffing the two build logs, the most important difference is that in the failed log maven picks up these dependencies:
while in the successful build, the same dependency looks like this:
This translates for the successful build into:
[DEBUG] Classpath: [/Users/henning/private/source/services/thetargetproject/target/classes
and for the failed build:
[DEBUG] Classpath: [...]
(note that even for the successful build, the aopalliance dependency still got dropped).
This behaviour started with maven 3.x, all permutations of the dependencies build fine with maven 2.2.1
This problem can be reproduced in all maven 3.0.x versions (.1, .2 and .3).
In both cases, the transitive dependencies of guice 3.0 (javax.inject:javax.inject and aopalliance:aopalliance) should always be present.
The same behaviour occurs in the exec-maven-plugin which uses the runtime dependency path to execute java code.