[MANTTASKS-22] artifact:dependencies does not respect in the generated classpath the order of the dependencies

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.4
• Fix Version/s: 2.0.8
• Component/s: dependencies task
• Environment: Windows 2005; Ant 1.6.5; JDK 1.4.2_10
• Assignee: Herve Boutemy
• Reporter: Aurélien Lacenaire
• Created: 06/Jan/06 08:19
• Updated: 05/Nov/07 15:51
• Resolved: 05/Nov/07 15:51

Description

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.

Issue Links

• is related to: MNG-1412 dependency sorting in classpath
• is related to: MNG-3111 Classpath order incorrect