You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Herve Boutemy (JIRA)" <ji...@codehaus.org> on 2008/02/03 12:34:00 UTC
[jira] Closed: (MNG-1412) dependency sorting in classpath
[ http://jira.codehaus.org/browse/MNG-1412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Herve Boutemy closed MNG-1412.
------------------------------
Assignee: Herve Boutemy (was: fabrizio giustina)
Resolution: Fixed
Fix Version/s: (was: 2.0.x)
2.0.9
fixed on 2007/12/07 in r601095 (r601096 in trunk)
Integration test just added in r617974
> 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