[
http://jira.codehaus.org/browse/MNG-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_124926
]
Joerg Schaible commented on MNG-3259:
-------------------------------------
Although I feel a bit uncomfortable, if such a problem suddenly vanished
without identification of the originating reason, I have to confirm that this
SNAPSHOT is the first version since M205 that builds our complete project tree
without any problem:
=========== %< =========
[SNIP]
...
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO] ------------------------------------------------------------------------
...
[SNIP]289 projects
...
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 44 minutes 3 seconds
[INFO] Finished at: Mon Feb 25 09:59:29 CET 2008
[INFO] Final Memory: 160M/254M
[INFO] ------------------------------------------------------------------------
=========== %< =========
This is really such a great relief! Thanks to all of you looking into this!
BTW John, when did you claim, M209 is gonna released? ;-) GO GO GO GO :D
> 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: John Casey
> Priority: Blocker
> Fix For: 2.0.9
>
> 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
