[ http://jira.codehaus.org/browse/MNG-1935?page=all ]
Kenney Westerhof updated MNG-1935: ---------------------------------- Fix Version/s: (was: 2.0.5) 2.0.6 > artifact:dependencies does not respect in the generated classpath the order > of the dependencies > ----------------------------------------------------------------------------------------------- > > Key: MNG-1935 > URL: http://jira.codehaus.org/browse/MNG-1935 > Project: Maven 2 > Issue Type: Bug > Components: Artifacts and Repositories, Ant tasks > Affects Versions: 2.0.1 > Environment: Windows 2005 > Ant 1.6.5 > JDK 1.4.2_10 > Reporter: Aurélien Lacenaire > Fix For: 2.0.6 > > > For example, if I put the dependencies in this order, in the generated > classpath (dependency.classpath) the order of the jars seems to be different : > <artifact:dependencies pathId="dependency.classpath" > filesetId="dependency.fileset" useScope="runtime"> > <remoteRepository refid="remote.repository"/> > <dependency groupId="projects" artifactId="abc" version="1.0"/> > <dependency groupId="projects" artifactId="def" version="1.0"/> > <dependency groupId="projects" artifactId="ghi" version="1.0"/> > </artifact:dependencies> > the order in the generated classpath dependency.classpath is not the same as : > <path id="dependency.classpath"> > <pathelement location="${jars.location}/abc-1.0.jar"/> > <pathelement location="${jars.location}/def-1.0.jar"/> > <pathelement location="${jars.location}/ghi-1.0"/> > </path> > And my projects have to use those jars in a specific order, otherwhise the > build fails. -- 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