[
http://jira.codehaus.org/browse/MNG-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112378
]
Joerg Schaible commented on MNG-3259:
-------------------------------------
Oh, please don't. I already reported the problem as regression for 2.0.7, but
was not able to find a test case to reproduce the effect:
http://mail-archives.apache.org/mod_mbox/maven-dev/200706.mbox/<F0D7281DAB048B438E8F5EC4ECEFBDDC0173C7E3%40esmail.elsag.de>.
I follow all the issues about dependency problems quite close and I really
thought that the causing issue has been fixed - unless I tried the new RC.
And, no, we're stuck to 2.0.5, because we don't have a workaround. As said, if
we add the missing artifact directly with scope test, the test fails with
another missing class. IMHO it is quite scary, that Maven drops dependencies
under some circumstances. And staying with M205 starts to be a real pain, since
quite some new versions of plugins require now newer versions.
I can also confirm Asgeir's comment, the build does not fail for me on Linux,
so it seems to be bound to a Windows installation - for whatever weird reason,
but see also:
MNG-2962
MNG-3061
At least the natural order should not make any difference, then we would have a
chance of sorting the deps accordingly. Can you simply replace the usage of the
involved ordinary HashMaps with LinkedHashMaps?
> 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
