[
https://issues.apache.org/jira/browse/MNG-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17265558#comment-17265558
]
Hudson commented on MNG-3259:
-----------------------------
Build unstable in Jenkins: Maven » Maven TLP » maven » mng-5668-poc #15
See
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven/job/mng-5668-poc/15/
> Regression: Maven drops dependencies in multi-module build
> ----------------------------------------------------------
>
> Key: MNG-3259
> URL: https://issues.apache.org/jira/browse/MNG-3259
> Project: Maven
> Issue Type: Bug
> Components: Dependencies
> Affects Versions: 2.0.7, 2.0.8, 3.0-alpha-1
> Reporter: Joerg Schaible
> Assignee: John Dennis Casey
> Priority: Blocker
> Fix For: 2.0.9
>
> Attachments: MNG-3259-2.zip, MNG-3259.zip
>
> Time Spent: 5h
> Remaining Estimate: 0h
>
> 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 was sent by Atlassian Jira
(v8.3.4#803005)
