[
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
