[ 
http://jira.codehaus.org/browse/MNG-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

John Casey closed MNG-3259.
---------------------------

    Resolution: Fixed

I just tested this on OS X and WinXP, using maven 2.0.7, 2.0.8, and 
2.0.9-SNAPSHOT from revId: 630321. All of my tests used JDK 1.4. 

In the cases of 2.0.8 and 2.0.9-SNAPSHOT on OS X, it didn't fail.

In the cases of 2.0.7 and 2.0.8 on WinXP, it failed.

In the case of 2.0.9-SNAPSHOT on WinXP, it didn't fail.

I'm not sure, but it looks like it has been fixed inadvertently...not a great 
thing to say, but there you go. I'd welcome some more eyes on this issue, to 
see if you can prove me wrong/crazy/something.

I built a distro from that revision, and parked it here:

http://people.apache.org/~jdcasey/maven-drops/2.0.9-SNAPSHOT

Please reopen this issue if you can't replicate my success.

> 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

        

Reply via email to