[
http://jira.codehaus.org/browse/MNG-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112180
]
Brian Fox commented on MNG-3259:
--------------------------------
This is related to natural set ordering as assumed. The problem seems to be
that the testClasspathElements is missing these artifacts (xstream etc) but
they are present when running dependency:resolve or tree. The case that works,
sets xstream to compile first then test, the case that doesn't sets it to test
then compile. Somewhere in the artifact collector, the scope is getting slammed
and then I think the tree is being trimmed for a closer dependency that is
excluded. It's a complex example that has dependencyMgt, exclusions and reactor
siblings all involved. Could you have found a more complex case ;-)
I'm getting close...
> Regression: Maven drops dependencies in multi-module build
> ----------------------------------------------------------
>
> Key: MNG-3259
> URL: http://jira.codehaus.org/browse/MNG-3259
> Project: Maven 2
> Issue Type: Bug
> Components: Dependencies
> Affects Versions: 2.0.7, 2.0.8
> Reporter: Joerg Schaible
> Assignee: Brian Fox
> Priority: Blocker
> Fix For: 2.0.8
>
> Attachments: MNG-3259-2.zip, MNG-3259.zip
>
> Time Spent: 5 hours
> Remaining Estimate: 0 minutes
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
