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

Ralph Goers commented on MNG-3259:
----------------------------------

I downloaded MNG-3259-2.zip.  I updated maven-2.0.x to the latest code. I ran 
the build from my ubuntu VM on Windows. It worked. The output from mvn -v there 
is: 
Maven version: 2.0.9-SNAPSHOT
Java version: 1.5.0_14
OS name: "linux" version: "2.6.22-14-generic" arch: "i386" Family: "unix"

I then ran the test in cygwin on Windows. It worked. mvn -v shows 
Maven version: 2.0.9-SNAPSHOT
Java version: 1.5.0_09
OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"

I then went to a "normal" Windows command shell and ran mvn clean and then mvn 
install. It completed successfully. The output from mvn -v was
Maven version: 2.0.9-SNAPSHOT
Java version: 1.5.0_09
OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"

> 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.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