You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Mark Hobson (JIRA)" <ji...@codehaus.org> on 2005/11/03 18:25:06 UTC
[jira] Created: (MNG-1412) .classpath should have nearest order
.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
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Closed: (MNG-1412) .classpath should have nearest order
Posted by "fabrizio giustina (JIRA)" <ji...@codehaus.org>.
[ 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MNG-1412) dependency sorting in classpath
Posted by "fabrizio giustina (JIRA)" <ji...@codehaus.org>.
[ 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MNG-1412) dependency sorting in classpath
Posted by "Mark Hobson (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1412?page=comments#action_52237 ]
Mark Hobson commented on MNG-1412:
----------------------------------
Yes, sorry, the ordering is the same as in maven itself - I didn't mean to imply otherwise. Moving to maven core gets my vote, thanks.
> 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MNG-1412) .classpath should have nearest order
Posted by "fabrizio giustina (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1412?page=comments#action_52058 ]
fabrizio giustina commented on MNG-1412:
----------------------------------------
Is there a reason for this order or it's only a "cosmetic" reason? AFAIK unless you have the same classes in multiple dependencies the order has no effect.
> .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
>
>
> 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Reopened: (MNG-1412) .classpath should have nearest order
Posted by "Mark Hobson (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1412?page=all ]
Mark Hobson reopened MNG-1412:
------------------------------
This is mainly required when dealing with resources within dependencies. An example would be that projects B and C both contain a log4j.properties file and you want to always pick up the nearest one. At the moment C's log4j.properties file would be used in preference to B's, which seems a bit unintuitive. Eclipse does allow you to manually reorder the classpath but this is tedious and error prone.
> .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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org