[jira] Commented: (MNG-1412) dependency sorting in classpath
[ http://jira.codehaus.org/browse/MNG-1412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_122255 ] Martin Zeltner commented on MNG-1412: - Hurray! ;-) Have a nice day! Martin > dependency sorting in classpath > --- > > Key: MNG-1412 > URL: http://jira.codehaus.org/browse/MNG-1412 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies >Affects Versions: 2.0 >Reporter: Mark Hobson >Assignee: Herve Boutemy > Fix For: 2.0.9 > > Attachments: artifact-order_maven-artifact-manager.txt, > artifact-order_maven-artifact.txt, artifact-order_maven-project.txt, > MNG-1412-maven-2.0.x-r507746.patch, MNG-1412_dependency_sorting.tgz > > > 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
[jira] Commented: (MNG-1412) dependency sorting in classpath
[ http://jira.codehaus.org/browse/MNG-1412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_121230 ] Robert Weissmann commented on MNG-1412: --- Hi, many votes on changes on this one, but sine 2005 there is no response from the Asignee "fabrizio giustina". Is he still around ? And if not, how does this work that someone else takes over in case he left ? Maybe this is a dead thread. Anyone knows how this works ? Cheers, Robert. > dependency sorting in classpath > --- > > Key: MNG-1412 > URL: http://jira.codehaus.org/browse/MNG-1412 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies >Affects Versions: 2.0 >Reporter: Mark Hobson >Assignee: fabrizio giustina > Fix For: 2.1 > > Attachments: artifact-order_maven-artifact-manager.txt, > artifact-order_maven-artifact.txt, artifact-order_maven-project.txt, > MNG-1412-maven-2.0.x-r507746.patch > > > 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
[jira] Commented: (MNG-1412) dependency sorting in classpath
[ http://jira.codehaus.org/browse/MNG-1412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_121029 ] richard rattigan commented on MNG-1412: --- This should definitely be fixed. I would suggest depth-first traversal, in the order specified in the pom would work best. The first occurrence of a dependency visited in this order should determine it's position in the classpath. This should be very easy to implement, and it would allow full control over classpath ordering by the normal mechanisms of adding dependencies and excluding transitive dependencies. In addition, the relationship between the poms and the classpath would be very natural and intuitive. Patching jars should be a last resort - unless you're a proponent of fragile development methodologies... > dependency sorting in classpath > --- > > Key: MNG-1412 > URL: http://jira.codehaus.org/browse/MNG-1412 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies >Affects Versions: 2.0 >Reporter: Mark Hobson >Assignee: fabrizio giustina > Fix For: 2.1 > > Attachments: artifact-order_maven-artifact-manager.txt, > artifact-order_maven-artifact.txt, artifact-order_maven-project.txt, > MNG-1412-maven-2.0.x-r507746.patch > > > 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
[jira] Commented: (MNG-1412) dependency sorting in classpath
[ http://jira.codehaus.org/browse/MNG-1412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118745 ] Robert Weissmann commented on MNG-1412: --- I totally agree with Yuri and Bryan, there should be a simple algorithm delivering ALWAYS the same classpath order based on the dependency or some parameter, so I can influence it. This should not be s difficult, but would be very helpfull, expecially during migration phases, version changes and testings. In a production release Nicolas you are absolutely right, there should be no such dependency on the classpath order. But in all other cases it is extremly helpfull. I hope this will be fixed soon (I conciously say "fixed", because for me this is definitely a bug - I was supprised that there is no parameter to set the order). Thanks to all the guys working hard on this project. Happy new year for 2008 ;-). > dependency sorting in classpath > --- > > Key: MNG-1412 > URL: http://jira.codehaus.org/browse/MNG-1412 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies >Affects Versions: 2.0 >Reporter: Mark Hobson >Assignee: fabrizio giustina > Fix For: 2.1 > > Attachments: artifact-order_maven-artifact-manager.txt, > artifact-order_maven-artifact.txt, artifact-order_maven-project.txt, > MNG-1412-maven-2.0.x-r507746.patch > > > 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
[jira] Commented: (MNG-1412) dependency sorting in classpath
[ http://jira.codehaus.org/browse/MNG-1412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_117661 ] Yuri Schimke commented on MNG-1412: --- Yes you are probably right, its mainly architectural issues i.e. patch jars. But fixing it would save so much trouble for so many people. So why argue so passionately about not fixing it, when its a simple fix. If you need a "good" reason to fix it, then It is bizarre that there is no predictable order for the classpath, even alphabetical would be better than quasi-random. > dependency sorting in classpath > --- > > Key: MNG-1412 > URL: http://jira.codehaus.org/browse/MNG-1412 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies >Affects Versions: 2.0 >Reporter: Mark Hobson >Assignee: fabrizio giustina > Fix For: 2.1 > > Attachments: artifact-order_maven-artifact-manager.txt, > artifact-order_maven-artifact.txt, artifact-order_maven-project.txt, > MNG-1412-maven-2.0.x-r507746.patch > > > 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
[jira] Commented: (MNG-1412) dependency sorting in classpath
[ http://jira.codehaus.org/browse/MNG-1412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_117443 ] nicolas de loof commented on MNG-1412: -- I can understand this classpath ordering requirement for a command line application point of view, where the classpath variable is under control, but what in a JEE context where all jars are put in WEB-INF/lib and not ordering can be specified ? Having a project to depend on classpath ordering is simply a nonsense for me. This sounds like a hack to bypass some architecture issues. You have multiple log4j.properties in classpath ? Having multiple result for a resource lookup is a valid Java case (@see Classloader.getResources()) but IS NOT supported by log4j ! - Why do those jars have a log4j.properties if they are not runnable artifacts ? - Why not setup log4j programmatically or using -Dlog4j.configuration ? for testing purpose, the taget/classes and taget/test-classes are set prior to dependencies in classpath, like the WEB-INF/classes is on a JEE webapp. You need to patch some 3d party jar ? Create a new project, use the dependency plugin to unpack it, add your custom patched classes and package your own modified artifact ! > dependency sorting in classpath > --- > > Key: MNG-1412 > URL: http://jira.codehaus.org/browse/MNG-1412 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies >Affects Versions: 2.0 >Reporter: Mark Hobson >Assignee: fabrizio giustina > Fix For: 2.1 > > Attachments: artifact-order_maven-artifact-manager.txt, > artifact-order_maven-artifact.txt, artifact-order_maven-project.txt, > MNG-1412-maven-2.0.x-r507746.patch > > > 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
[jira] Commented: (MNG-1412) dependency sorting in classpath
[ http://jira.codehaus.org/browse/MNG-1412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_109773 ] Michael Buckley commented on MNG-1412: -- I vote for a stable order in the .classpath file. We commit these to SVN to simplify eclipse usage, and rebuilding them on different machines generates spurious diffs. If fact, just adding -DdownloadSources=true generates different orders. > dependency sorting in classpath > --- > > Key: MNG-1412 > URL: http://jira.codehaus.org/browse/MNG-1412 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies >Affects Versions: 2.0 >Reporter: Mark Hobson >Assignee: fabrizio giustina > Fix For: 2.1 > > Attachments: artifact-order_maven-artifact-manager.txt, > artifact-order_maven-artifact.txt, artifact-order_maven-project.txt, > MNG-1412-maven-2.0.x-r507746.patch > > > 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
[jira] Commented: (MNG-1412) dependency sorting in classpath
[ http://jira.codehaus.org/browse/MNG-1412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94668 ] Knut Forkalsrud commented on MNG-1412: -- I would think the most common example for this would be log4j static initialization We don't want to configure logging explicitly in unit tests, so we rely on log4j's builtin lookup of "log4j.properties". Unfortunately way too many third party jars contain one of these so we need the directory target/test-classes to be first on the classpath. One can argue that log4j's approach isn't the best, but it is the standard for practical purposes. > dependency sorting in classpath > --- > > Key: MNG-1412 > URL: http://jira.codehaus.org/browse/MNG-1412 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.0 >Reporter: Mark Hobson >Assignee: fabrizio giustina > Fix For: 2.1.x > > Attachments: artifact-order_maven-artifact-manager.txt, > artifact-order_maven-artifact.txt, artifact-order_maven-project.txt, > MNG-1412-maven-2.0.x-r507746.patch > > > 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
[jira] Commented: (MNG-1412) dependency sorting in classpath
[ http://jira.codehaus.org/browse/MNG-1412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_93315 ] Bryan Cooper commented on MNG-1412: --- Perhaps an ordering attribute on the dependency itself would help in ordering. By default, the attribute doesn't need to be specified in the pom, but, be used by the module responsible for ordering the dependencies to store the default pom order of dependencies. This would also enable a simple sort via the Collections.sort utility. junit junit 3.8.1 test 1<-- New attribute The attribute should be respected for building classpaths and even for adding a classpath to a manifest file. Also, transitive dependencies shoud be included directly prior to their first occurrance, but, not before. Hope to see some news on this issue soon. > dependency sorting in classpath > --- > > Key: MNG-1412 > URL: http://jira.codehaus.org/browse/MNG-1412 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.0 >Reporter: Mark Hobson >Assignee: fabrizio giustina > Fix For: 2.1.x > > Attachments: artifact-order_maven-artifact-manager.txt, > artifact-order_maven-artifact.txt, artifact-order_maven-project.txt, > MNG-1412-maven-2.0.x-r507746.patch > > > 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
[jira] Commented: (MNG-1412) dependency sorting in classpath
[ http://jira.codehaus.org/browse/MNG-1412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91134 ] coding commented on MNG-1412: - Hi, The order of dependencies in the classPathElement does not follow the order as in pom.xml. It is never the same, I ran it on LINUX/Windows.. used the latest of Maven 2.04/2.0.5/2.0.6 .. with the latest JDK's.. but nothing helps. There is one behaviour I have noticed that when if the dependency you are trying to order is in the build path then only the order is not correct... Please help > dependency sorting in classpath > --- > > Key: MNG-1412 > URL: http://jira.codehaus.org/browse/MNG-1412 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.0 >Reporter: Mark Hobson > Assigned To: fabrizio giustina > Fix For: 2.1.x > > Attachments: artifact-order_maven-artifact-manager.txt, > artifact-order_maven-artifact.txt, artifact-order_maven-project.txt, > MNG-1412-maven-2.0.x-r507746.patch > > > 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
[jira] Commented: (MNG-1412) dependency sorting in classpath
[ http://jira.codehaus.org/browse/MNG-1412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90904 ] Carlos Sanchez commented on MNG-1412: - if this is going to be implemented then a method that return something like a ListOrderedSet must be added. If you return an ordered Set it will be confusing. http://jakarta.apache.org/commons/collections/apidocs-COLLECTIONS_3_0/org/apache/commons/collections/set/ListOrderedSet.html > dependency sorting in classpath > --- > > Key: MNG-1412 > URL: http://jira.codehaus.org/browse/MNG-1412 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.0 >Reporter: Mark Hobson > Assigned To: fabrizio giustina > Fix For: 2.1.x > > Attachments: artifact-order_maven-artifact-manager.txt, > artifact-order_maven-artifact.txt, artifact-order_maven-project.txt, > MNG-1412-maven-2.0.x-r507746.patch > > > 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
[jira] Commented: (MNG-1412) dependency sorting in classpath
[ http://jira.codehaus.org/browse/MNG-1412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89465 ] Sebastien Brunot commented on MNG-1412: --- I've tried the new 2.0.5 version and the problem is still present in my case. For some reasons (that i cannot change), i'm using a library library-patch.jar that redefines a class of library.jar adding some extra methods to it. Whatever the order in which i declare the library-patch.jar and library.jar dependencies of my project, library.jar is always the first one in the classpath. So my project, which expect the patch class from library-patch.jar is not compiling. :-( > dependency sorting in classpath > --- > > Key: MNG-1412 > URL: http://jira.codehaus.org/browse/MNG-1412 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.0 >Reporter: Mark Hobson > Assigned To: fabrizio giustina > Fix For: 2.1.x > > Attachments: artifact-order_maven-artifact-manager.txt, > artifact-order_maven-artifact.txt, artifact-order_maven-project.txt, > MNG-1412-maven-2.0.x-r507746.patch > > > 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
[jira] Commented: (MNG-1412) dependency sorting in classpath
[ http://jira.codehaus.org/browse/MNG-1412?page=comments#action_76083 ] Justin Edelson commented on MNG-1412: - Is this fix going to be in 2.1? I'm using a patched version of 2.0.4 as a result of it and have to distribute the three patched jars to all of our developers. > dependency sorting in classpath > --- > > Key: MNG-1412 > URL: http://jira.codehaus.org/browse/MNG-1412 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.0 >Reporter: Mark Hobson > Assigned To: fabrizio giustina > Fix For: 2.1 > > Attachments: artifact-order_maven-artifact-manager.txt, > artifact-order_maven-artifact.txt, artifact-order_maven-project.txt > > > 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
[jira] Commented: (MNG-1412) dependency sorting in classpath
[ http://jira.codehaus.org/browse/MNG-1412?page=comments#action_73654 ] Holger Hoffstätte commented on MNG-1412: Following up on my own comment about ordering for eclipse .classpath files: MECLIPSE-152 > dependency sorting in classpath > --- > > Key: MNG-1412 > URL: http://jira.codehaus.org/browse/MNG-1412 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.0 >Reporter: Mark Hobson > Assigned To: fabrizio giustina > Fix For: 2.1 > > Attachments: artifact-order_maven-artifact-manager.txt, > artifact-order_maven-artifact.txt, artifact-order_maven-project.txt > > > 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
[jira] Commented: (MNG-1412) dependency sorting in classpath
[ http://jira.codehaus.org/browse/MNG-1412?page=comments#action_73585 ] Pablo Gutierrez commented on MNG-1412: -- Sometimes there is a need to specify the order of the dependencies. Rigth now I'm in a situation where one jar overwrites some classes (not all) of some purchased library as didn't perform what we wanted. So in our jnlp's and scripts for launching our applications we have to specify one strict classpath order on jars. We are moving to Maven 2 but ran into this problem. Where can I download this fix? I need to use svn and build maven? Thanks > dependency sorting in classpath > --- > > Key: MNG-1412 > URL: http://jira.codehaus.org/browse/MNG-1412 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.0 >Reporter: Mark Hobson > Assigned To: fabrizio giustina > Fix For: 2.1 > > Attachments: artifact-order_maven-artifact-manager.txt, > artifact-order_maven-artifact.txt, artifact-order_maven-project.txt > > > 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
[jira] Commented: (MNG-1412) dependency sorting in classpath
[ http://jira.codehaus.org/browse/MNG-1412?page=comments#action_72313 ] Holger Hoffstätte commented on MNG-1412: I want to add another point of view and request ordering of exported jars *by name*, at least as option. While I can understand Mark's use case for controlling export ordering (POM order is a good step forward from the current way), I like to think of the need for a properly ordered classpath as a build management bug in the first place. This should just not be an issue for IDE development; I'd venture the guess that quickly finding classes in a list of jars is the much more common case. 99% of the time I am simply not interested in detailed dependency trees, and for launching I can still rearrange in the launch config. Looking at the patches it seems to me that an optional name ordering should not be much more complicated, e.g. by throwing everything into a TreeMap before output. > dependency sorting in classpath > --- > > Key: MNG-1412 > URL: http://jira.codehaus.org/browse/MNG-1412 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.0 >Reporter: Mark Hobson > Assigned To: fabrizio giustina > Fix For: 2.1 > > Attachments: artifact-order_maven-artifact-manager.txt, > artifact-order_maven-artifact.txt, artifact-order_maven-project.txt > > > 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
[jira] Commented: (MNG-1412) dependency sorting in classpath
[ 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
