You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Anders Lindgren (JIRA)" <ji...@codehaus.org> on 2012/01/23 15:18:02 UTC
[jira] (MDEP-342) maven-dependency-plugin goal build-classpath is
not written in correct order.
Anders Lindgren created MDEP-342:
------------------------------------
Summary: maven-dependency-plugin goal build-classpath is not written in correct order.
Key: MDEP-342
URL: https://jira.codehaus.org/browse/MDEP-342
Project: Maven 2.x Dependency Plugin
Issue Type: Bug
Components: build-classpath
Affects Versions: 2.4
Reporter: Anders Lindgren
When running the goal build-classpath, the order of the dependencies in the output is not the same as in the pom.
The dependency:tree is however producing output in correct order.
Also, when producing an executable jar using the maven-jar-plugin with addClasspath set to true, the result is correct.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MDEP-342) maven-dependency-plugin goal build-classpath is
not written in correct order.
Posted by "Anders Hammar (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MDEP-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=317462#comment-317462 ]
Anders Hammar commented on MDEP-342:
------------------------------------
Either I can't reproduce, or it migth be me missing something.
Using Maven 3.0.4 on Mac OS 10.8.2 with Apple JDK 1.6.0_37, I get (with attached test project):
mvn org.apache.maven.plugins:maven-dependency-plugin:2.4:build-classpath
/Users/anders/.m2/repository/commons-logging/commons-logging/1.1.1/commons-logging-1.1.1.jar:/Users/anders/.m2/repository/args4j/args4j/2.0.16/args4j-2.0.16.jar:/Users/anders/.m2/repository/com/thoughtworks/xstream/xstream/1.2.2/xstream-1.2.2.jar:/Users/anders/.m2/repository/xpp3/xpp3_min/1.1.3.4.O/xpp3_min-1.1.3.4.O.jar
The same result with v2.6 of the plugin as well. And this is also the order I see in the POM (including transitive deps).
In the manifest of the jar I get:
Class-Path: lib/commons-logging-1.1.1.jar lib/args4j-2.0.16.jar lib/xs
tream-1.2.2.jar lib/xpp3_min-1.1.3.4.O.jar
All seems fine!?
> maven-dependency-plugin goal build-classpath is not written in correct order.
> -----------------------------------------------------------------------------
>
> Key: MDEP-342
> URL: https://jira.codehaus.org/browse/MDEP-342
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Components: build-classpath
> Affects Versions: 2.4
> Reporter: Anders Lindgren
> Attachments: classpathorderproblem.zip
>
>
> When running the goal build-classpath, the order of the dependencies in the output is not the same as in the pom.
> The dependency:tree is however producing output in correct order.
> Also, when producing an executable jar using the maven-jar-plugin with addClasspath set to true, the result is correct.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MDEP-342) maven-dependency-plugin goal build-classpath is
not written in correct order.
Posted by "Anders Lindgren (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MDEP-342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anders Lindgren updated MDEP-342:
---------------------------------
Attachment: classpathorderproblem.zip
mvn dependency:build-classpath is not producing the classpath in the same order as mvn dependency:tree
> maven-dependency-plugin goal build-classpath is not written in correct order.
> -----------------------------------------------------------------------------
>
> Key: MDEP-342
> URL: https://jira.codehaus.org/browse/MDEP-342
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Components: build-classpath
> Affects Versions: 2.4
> Reporter: Anders Lindgren
> Attachments: classpathorderproblem.zip
>
>
> When running the goal build-classpath, the order of the dependencies in the output is not the same as in the pom.
> The dependency:tree is however producing output in correct order.
> Also, when producing an executable jar using the maven-jar-plugin with addClasspath set to true, the result is correct.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MDEP-342) maven-dependency-plugin goal build-classpath is
not written in correct order.
Posted by "Anders Hammar (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MDEP-342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anders Hammar reopened MDEP-342:
--------------------------------
> maven-dependency-plugin goal build-classpath is not written in correct order.
> -----------------------------------------------------------------------------
>
> Key: MDEP-342
> URL: https://jira.codehaus.org/browse/MDEP-342
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Components: build-classpath
> Affects Versions: 2.4
> Reporter: Anders Lindgren
> Fix For: 2.3
>
> Attachments: classpathorderproblem.zip
>
>
> When running the goal build-classpath, the order of the dependencies in the output is not the same as in the pom.
> The dependency:tree is however producing output in correct order.
> Also, when producing an executable jar using the maven-jar-plugin with addClasspath set to true, the result is correct.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MDEP-342) maven-dependency-plugin goal build-classpath is
not written in correct order.
Posted by "Anders Lindgren (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MDEP-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=317465#comment-317465 ]
Anders Lindgren commented on MDEP-342:
--------------------------------------
Hi,
Yes, I agree, I just re-tested with 2.6 and it works fine. (Seems to have been fixed in 2.3)
I will close this ticket.
the "list" goal still produces the output in another order, but that might be fine.
> maven-dependency-plugin goal build-classpath is not written in correct order.
> -----------------------------------------------------------------------------
>
> Key: MDEP-342
> URL: https://jira.codehaus.org/browse/MDEP-342
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Components: build-classpath
> Affects Versions: 2.4
> Reporter: Anders Lindgren
> Attachments: classpathorderproblem.zip
>
>
> When running the goal build-classpath, the order of the dependencies in the output is not the same as in the pom.
> The dependency:tree is however producing output in correct order.
> Also, when producing an executable jar using the maven-jar-plugin with addClasspath set to true, the result is correct.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MDEP-342) maven-dependency-plugin goal build-classpath is
not written in correct order.
Posted by "Anders Lindgren (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MDEP-342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anders Lindgren closed MDEP-342.
--------------------------------
Resolution: Fixed
Fix Version/s: 2.3
Problem with build-classpath has been resolved
> maven-dependency-plugin goal build-classpath is not written in correct order.
> -----------------------------------------------------------------------------
>
> Key: MDEP-342
> URL: https://jira.codehaus.org/browse/MDEP-342
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Components: build-classpath
> Affects Versions: 2.4
> Reporter: Anders Lindgren
> Fix For: 2.3
>
> Attachments: classpathorderproblem.zip
>
>
> When running the goal build-classpath, the order of the dependencies in the output is not the same as in the pom.
> The dependency:tree is however producing output in correct order.
> Also, when producing an executable jar using the maven-jar-plugin with addClasspath set to true, the result is correct.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MDEP-342) maven-dependency-plugin goal build-classpath is
not written in correct order.
Posted by "Anders Hammar (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MDEP-342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anders Hammar closed MDEP-342.
------------------------------
Resolution: Cannot Reproduce
Fix Version/s: (was: 2.3)
Changing to "cannot reproduce".
> maven-dependency-plugin goal build-classpath is not written in correct order.
> -----------------------------------------------------------------------------
>
> Key: MDEP-342
> URL: https://jira.codehaus.org/browse/MDEP-342
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Components: build-classpath
> Affects Versions: 2.4
> Reporter: Anders Lindgren
> Attachments: classpathorderproblem.zip
>
>
> When running the goal build-classpath, the order of the dependencies in the output is not the same as in the pom.
> The dependency:tree is however producing output in correct order.
> Also, when producing an executable jar using the maven-jar-plugin with addClasspath set to true, the result is correct.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira