[
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
