[jira] Commented: (MASSEMBLY-247) versions of included dependencies in multi-module projects are not deterministic
[ http://jira.codehaus.org/browse/MASSEMBLY-247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116601 ] Tarek El-Sibay commented on MASSEMBLY-247: -- Hi, i have this problem on windows XP but with eclipse 3.2 and without the M2Eclipse plugin. And this problem occured too with a non snapshot version, commons-lang-2.1 was included instead of commons-lang-2.2. But we will try your workaround! Regards Tarek > versions of included dependencies in multi-module projects are not > deterministic > > > Key: MASSEMBLY-247 > URL: http://jira.codehaus.org/browse/MASSEMBLY-247 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug >Affects Versions: 2.1, 2.2-beta-1, 2.2-beta-2 > Environment: Maven 2.0.4 an assembly plugin 2.2-SNAPSHOT >Reporter: Tarek El-Sibay > Attachments: assembly-dependency-problem.zip > > > There is a problem with including dependency jars in an assembly. The > resoultion of the version of the dependencies is not deterministic. The > attached zipfile contains three projects, assembly, module-One and modue-Two. > the assembly project is the aggregator of module-One and module-Two. > module-One has a dep to junit 3.8.1, module-Two to junit 4.0. The assembly > project contains a DependencyManagement with a dependency to junit 4.0. > After executing 'mvn clean package ' in the assembly project the resulting > zip file assembly-1.0-SNAPSHOT-luna.zip contains junit 3.8.1, after 'mvn > clean install' it contains junit 4.0. > Sometimes its the other way around, but playing with both commands shows that > the resulting version of junit is not deterministic. -- 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] Commented: (MASSEMBLY-247) versions of included dependencies in multi-module projects are not deterministic
[ http://jira.codehaus.org/browse/MASSEMBLY-247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116586 ] Anders Eriksson commented on MASSEMBLY-247: --- It seems that we've experienced this problem too. With several versions of SNAPSHOT jars in the local repository it seems like the assembly plugin takes any arbitrary jar from the local repository. For example the following files in the local repository lillmacen:0.2.0-SNAPSHOT anders$ ls -latr *.jar -rw-r--r-- 1 anders staff 7432 22 Nov 15:39 fas3-core-api-0.2.0-20071121.140025-4.jar -rw-r--r-- 1 anders staff 9255 29 Nov 13:08 fas3-core-api-0.2.0-20071128.090034-6.jar -rw-r--r-- 1 anders staff 23911 12 Dec 13:39 fas3-core-api-0.2.0-SNAPSHOT.jar -rw-r--r-- 1 anders staff 23911 12 Dec 13:39 fas3-core-api-0.2.0-20071212.120216-27.jar would not necessarily pick our intended fas3-core-api-0.2.0-SNAPSHOT.jar The POM snippet looks like this: maven-assembly-plugin jar-with-dependencies make-assembly package attached Our workaround is to completely empty the local repository and have it reinstalled with only the latest SNAPSHOT before trying to use the assembly plugin. This problem have so far only been seen on Windows XP (even if the explaining example above shows files from a Mac) using Eclipse 3.3 and the M2Eclipse plugin http://m2eclipse.codehaus.org/ which I believe is built on Maven 2.1. > versions of included dependencies in multi-module projects are not > deterministic > > > Key: MASSEMBLY-247 > URL: http://jira.codehaus.org/browse/MASSEMBLY-247 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug >Affects Versions: 2.1, 2.2-beta-1, 2.2-beta-2 > Environment: Maven 2.0.4 an assembly plugin 2.2-SNAPSHOT >Reporter: Tarek El-Sibay > Attachments: assembly-dependency-problem.zip > > > There is a problem with including dependency jars in an assembly. The > resoultion of the version of the dependencies is not deterministic. The > attached zipfile contains three projects, assembly, module-One and modue-Two. > the assembly project is the aggregator of module-One and module-Two. > module-One has a dep to junit 3.8.1, module-Two to junit 4.0. The assembly > project contains a DependencyManagement with a dependency to junit 4.0. > After executing 'mvn clean package ' in the assembly project the resulting > zip file assembly-1.0-SNAPSHOT-luna.zip contains junit 3.8.1, after 'mvn > clean install' it contains junit 4.0. > Sometimes its the other way around, but playing with both commands shows that > the resulting version of junit is not deterministic. -- 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] Commented: (MASSEMBLY-247) versions of included dependencies in multi-module projects are not deterministic
[ http://jira.codehaus.org/browse/MASSEMBLY-247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116152 ] Tarek El-Sibay commented on MASSEMBLY-247: -- hello! no comments, no hints, no solving. Nobody interested in the bug? did i made something wrong with this bug report? What can i do? Tarek > versions of included dependencies in multi-module projects are not > deterministic > > > Key: MASSEMBLY-247 > URL: http://jira.codehaus.org/browse/MASSEMBLY-247 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug >Affects Versions: 2.1, 2.2-beta-1, 2.2-beta-2 > Environment: Maven 2.0.4 an assembly plugin 2.2-SNAPSHOT >Reporter: Tarek El-Sibay > Attachments: assembly-dependency-problem.zip > > > There is a problem with including dependency jars in an assembly. The > resoultion of the version of the dependencies is not deterministic. The > attached zipfile contains three projects, assembly, module-One and modue-Two. > the assembly project is the aggregator of module-One and module-Two. > module-One has a dep to junit 3.8.1, module-Two to junit 4.0. The assembly > project contains a DependencyManagement with a dependency to junit 4.0. > After executing 'mvn clean package ' in the assembly project the resulting > zip file assembly-1.0-SNAPSHOT-luna.zip contains junit 3.8.1, after 'mvn > clean install' it contains junit 4.0. > Sometimes its the other way around, but playing with both commands shows that > the resulting version of junit is not deterministic. -- 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
