[ http://jira.codehaus.org/browse/MNG-1412?page=comments#action_68663 ]
Martin Zeltner commented on MNG-1412: ------------------------------------- I've patched Maven so you get the same order of artifacts how they are defined in poms. I've just replaced "java.util.HashMap" with "java.util.LinkedHashMap" and "java.util.HashSet" with "java.util.LinkedHashSet" in following modules of project "components": maven-artifact, maven-artifact-manager and maven-project. I don't know if there are other modules where this replacement should be made, for example the execution order of mojos in the same phase. Appended you can find the patch files for the revision of yesterday. Cheers, Martin > dependency sorting in classpath > ------------------------------- > > Key: MNG-1412 > URL: http://jira.codehaus.org/browse/MNG-1412 > Project: Maven 2 > Type: Bug > Versions: 2.0 > Reporter: Mark Hobson > Assignee: fabrizio giustina > Fix For: 2.1 > > > The .classpath file entries should be ordered by nearest transitiveness (if > that's a word). > For example, I have project A that depends on B that depends on C. The > classpath for A is generated in the order C, B. Ideally the classpath should > be in order of how near they are to the project, i.e. B, C. -- 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
