[
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
