[ http://jira.codehaus.org/browse/MNG-1412?page=all ]
fabrizio giustina closed MNG-1412:
----------------------------------
Resolution: Won't Fix
Please reopen the issue if you can find a valid reason why this kind of order
is needed; in the meanwhile I'm closing the issue since the order actually used
for the eclipse classpath is the same order used by maven during compilation
and IMHO this is definitively the correct behaviour.
> .classpath should have nearest order
> ------------------------------------
>
> Key: MNG-1412
> URL: http://jira.codehaus.org/browse/MNG-1412
> Project: Maven 2
> Type: Bug
> Components: maven-eclipse-plugin
> Versions: 2.0
> Reporter: Mark Hobson
> Assignee: fabrizio giustina
>
>
> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
