[jira] Updated: (MNG-3259) Regression: Maven drops dependencies in multi-module build
[ http://jira.codehaus.org/browse/MNG-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell updated MNG-3259: -- Affects Version/s: (was: 2.0.8) (was: 2.0.7) 3.0-alpha-1 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: 3.0-alpha-1 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
[jira] Updated: (MNG-3259) Regression: Maven drops dependencies in multi-module build
[ http://jira.codehaus.org/browse/MNG-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell updated MNG-3259: -- Fix Version/s: 2.0.9 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, 3.0-alpha-1 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
[jira] Updated: (MNG-3259) Regression: Maven drops dependencies in multi-module build
[ http://jira.codehaus.org/browse/MNG-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell updated MNG-3259: -- Affects Version/s: 2.0.7 2.0.8 Fix Version/s: (was: 2.0.9) 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, 3.0-alpha-1 Reporter: Joerg Schaible Assignee: John Casey Priority: Blocker 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
[jira] Updated: (MNG-3259) Regression: Maven drops dependencies in multi-module build
[ http://jira.codehaus.org/browse/MNG-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox updated MNG-3259: --- Fix Version/s: (was: 2.0.8) 2.0.9 I think we need to bump this to 2.0.9. After looking at it for a while, I have a general idea of the problem, but the fix has a high probability of breaking things further. There are several ways to work around this particular issue and from what I've seen, it occurs only in a very specific case: you are excluding a dependency from being pulled in transitively but then need the same dependency in the test scope. 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
[jira] Updated: (MNG-3259) Regression: Maven drops dependencies in multi-module build
[ http://jira.codehaus.org/browse/MNG-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joerg Schaible updated MNG-3259: Attachment: MNG-3259-2.zip Improved demo project. 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 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
[jira] Updated: (MNG-3259) Regression: Maven drops dependencies in multi-module build
[ http://jira.codehaus.org/browse/MNG-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox updated MNG-3259: --- Fix Version/s: 2.0.8 I verified this on 2.0.7/8 and 2.1 using java 1.5. It seems ok with 1.6 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.zip 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
[jira] Updated: (MNG-3259) Regression: Maven drops dependencies in multi-module build
[ http://jira.codehaus.org/browse/MNG-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joerg Schaible updated MNG-3259: Attachment: MNG-3259.zip Attachment with zipped demo project. Build instructions: - extract ZIP - go into extracted root directory - install parent pom first: mvn -f parent/pom.xml - install multi-module: mvn install The build should fail (*). Go into module5 and build from there: mvn install This time it should succeed. *) Before I've zipped the project I tried to replace any occurrence of XXX with 3259 in the 7 pom.xml files, but after that action M208 can suddenly build this! Therefore I've added also an install.log to the project root that demonstrates the problem. This means additionally that this build might behave differently on different JDKs. I highly assume that there are still some HashMaps used internally that have influence about the sequence the dependencies are processed, therefore I'd expect Maven to behave differently, e.g. this sequence is different for HashMaps in JDK 6 and the project can be build running M208 with JDK 6! See also first lines of install.log for my environment: Maven version: 2.0.8-SNAPSHOT Java version: 1.4.2_13 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 Priority: Blocker Attachments: MNG-3259.zip 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
