[MNG-2962] (False) transitive dependencies don't appear on the compiler classpath in some windows environments since m2.0.6.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Incomplete
• Affects Version/s: 2.0.6
• Component/s: Dependencies
• Environment: windows
• Assignee: Unassigned
• Reporter: Geoffrey De Smet
• Created: 25/Apr/07 04:04
• Updated: 29/Dec/09 13:16
• Resolved: 29/Dec/09 13:16

Description

Since m2.0.6 builds that work perfectly on linux machine A and sometimes even on a windows machine B, breaks on another windows machine C.

We have some "false transitive dependencies": transitive dependencies that should be direct dependencies.
(We currently do this to avoid having to duplicate the version number as the different projects don't have a common superpom.)
Making those dependencies direct dependencies fixes the problem with windows machine C, but the real problem is that the guy on linux machine A should get the problems too, before committing.

The compiler plugin version is locked down to 2.0.2, but are using maven 2.0.6. This did not occur in maven 2.0.5.

Attached you'll find the "mvn -X install" logs of the 2 windows machines.

The log of machine C is specifically interesting, as it shows "spring-beans:2.0.2" as a transitive dependency, yet it forgets it on the classpath in the compiler plugin:

[DEBUG] Adding managed depedendencies for unknown:atlas-spring
...
[DEBUG] org.springframework:spring-beans:jar:2.0.2:compile
...

[DEBUG] Classpath: [d:\sources\atlas-all\atlas-checkpoint\target\classes
.. (no org.springframework:spring-beans:jar:2.0.2)

Machine B instead has instead this at the classpath log part:

[DEBUG] Classpath: [d:\projects\sb\atlas_all\atlas-checkpoint\target\classes
...
C:\Documents and Settings\gds\.m2\repository\org\springframework\spring-beans\2.0.2\spring-beans-2.0.2.jar

Issue Links

• is related to: MNG-3259 Regression: Maven drops dependencies in multi-module build