[MNG-3259] Regression: Maven drops dependencies in multi-module build

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 2.0.7, 2.0.8, 3.0-alpha-1
• Fix Version/s: 2.0.9
• Component/s: Dependencies
• Assignee: John Dennis Casey
• Reporter: Joerg Schaible
• Created: 26/Oct/07 06:52
• Updated: 15/Jan/21 11:46
• Resolved: 22/Feb/08 15:12

Description

Under some circumstances Maven "forgets" about test dependencies in multi-module builds. The affected module can be build only if the build is started from its local project directory. If the build is run from a parent directory, the test fails because of missing classes. This issue applies to M207 and recent M208-RC1, the project can be build without problems with M205 (M206 is completely bogus). The problem was for us already the show stopper for M207 and I thought with some of the now resolved issues it has been gone, but I was wrong. I did not report it earlier, because I was never able to reproduce the problem with a minimal build ... until now and it took me about 3 days to create a demonstrating multi module project.

Issue Links

• is depended upon by: MNG-3829 3.0-alpha-1 release: get the core ITs passing
• relates to: MNG-2962 (False) transitive dependencies don't appear on the compiler classpath in some windows environments since m2.0.6.