[ http://jira.codehaus.org/browse/MNG-1412?page=all ]
fabrizio giustina updated MNG-1412:
-----------------------------------
Component: (was: maven-eclipse-plugin)
Summary: dependency sorting in classpath (was: .classpath should have
nearest order)
Checking the classpath used by maven when running tests and the .classpath
file generated by the eclipse plugin it seems that the order is preserved.
Since the purpose of the plugin is to make the eclipse environment match as
close as possible the maven one, this should not be changed (do you get
different result with your log4.properties case when running maven directly?).
If dependencies should be sorted in a different order, this should be done in
the maven core: I am moving this issue from the eclipse component to core
(leaving component as unknown, since there is no more "core" or "dependency
resolution" component)
> dependency sorting in classpath
> -------------------------------
>
> Key: MNG-1412
> URL: http://jira.codehaus.org/browse/MNG-1412
> Project: Maven 2
> Type: Bug
> 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]
