[
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 soooo 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
