[
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
