You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jesse Glick (JIRA)" <ji...@codehaus.org> on 2010/10/19 01:09:32 UTC
[jira] Created: (MNG-4870) dependency:tree omits batik-js
dependency:tree omits batik-js
------------------------------
Key: MNG-4870
URL: http://jira.codehaus.org/browse/MNG-4870
Project: Maven 2 & 3
Issue Type: Bug
Components: Dependencies
Affects Versions: 3.0
Environment: Maven 3.0, Ubuntu, JDK 6.
Reporter: Jesse Glick
Attachments: test_test-dependency-tree_jar_1.0-SNAPSHOT_101018-185145.zip
(Not sure what the right place to file this is. {{maven-dependency-tree 1.2}} gives {{MNG}} as the JIRA component by inheritance.)
{{mvn dependency:tree}} on the attached project lists {{batik-script}} by way of {{batik-bridge}} as expected, but then fails to show {{batik-js}} as a dependency of that. If you list {{batik-script}} as a direct dependency, {{batik-js}} is correctly shown.
Possibly related is that Maven 2.2.1 also fails to find {{batik-js}} in {{MavenProject.getRuntimeArtifacts}}, so {{clean package}} fails, whereas this works fine under Maven 3.0. Yet just running the dependency plugin under M3 does not suffice to pick up this fix, wherever it was - MNG-4690?
Although the Batik JARs are built from an odd source tree, the artifacts as present in the local repository look normal enough; all of the dependencies involved are simple compile scope without exclusions etc.
Marking "major" since this seems to cause MNBMODULE-102 (producing build errors for certain projects); also I have noticed that the dependency graph feature in the NB IDE omits {{batik-js}}, and there may be other user-visible effects of this bug.
--
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
[jira] (MSHARED-167) dependency:tree omits batik-js
Posted by "Herve Boutemy (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MSHARED-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Herve Boutemy closed MSHARED-167.
---------------------------------
Resolution: Fixed
Fix Version/s: maven-dependency-tree-2.0
Assignee: Herve Boutemy
new DependencyGraphBuilder component created in [r1348663|http://svn.apache.org/viewvc?rev=1348663&view=rev]
this component has a Maven 2 implementation using "usual" DependencyTreeBuilder and a Maven 3 implementation using Maven 3 with Aether
Default implementation detects current Maven version and automatically switches between the 2
> dependency:tree omits batik-js
> ------------------------------
>
> Key: MSHARED-167
> URL: https://jira.codehaus.org/browse/MSHARED-167
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-dependency-tree
> Affects Versions: maven-dependency-tree-1.2
> Environment: Maven 3.0, Ubuntu, JDK 6.
> Reporter: Jesse Glick
> Assignee: Herve Boutemy
> Fix For: maven-dependency-tree-2.0
>
> Attachments: test_test-dependency-tree_jar_1.0-SNAPSHOT_101018-185145.zip
>
>
> (Not sure what the right place to file this is. {{maven-dependency-tree 1.2}} gives {{MNG}} as the JIRA component by inheritance.)
> {{mvn dependency:tree}} on the attached project lists {{batik-script}} by way of {{batik-bridge}} as expected, but then fails to show {{batik-js}} as a dependency of that. If you list {{batik-script}} as a direct dependency, {{batik-js}} is correctly shown.
> Possibly related is that Maven 2.2.1 also fails to find {{batik-js}} in {{MavenProject.getRuntimeArtifacts}}, so {{clean package}} fails, whereas this works fine under Maven 3.0. Yet just running the dependency plugin under M3 does not suffice to pick up this fix, wherever it was - MNG-4690?
> Although the Batik JARs are built from an odd source tree, the artifacts as present in the local repository look normal enough; all of the dependencies involved are simple compile scope without exclusions etc.
> Marking "major" since this seems to cause MNBMODULE-102 (producing build errors for certain projects); also I have noticed that the dependency graph feature in the NB IDE omits {{batik-js}}, and there may be other user-visible effects of this bug.
--
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] Commented: (MSHARED-167) dependency:tree omits batik-js
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSHARED-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=240036#action_240036 ]
Benjamin Bentmann commented on MSHARED-167:
-------------------------------------------
The tree calculated by Maven 3.0 core is correct:
{noformat}
[DEBUG] test:test-dependency-tree:jar:1.0-SNAPSHOT
[DEBUG] org.apache.xmlgraphics:batik-swing:jar:1.7:compile
[DEBUG] org.apache.xmlgraphics:batik-awt-util:jar:1.7:compile
[DEBUG] org.apache.xmlgraphics:batik-bridge:jar:1.7:compile
[DEBUG] org.apache.xmlgraphics:batik-anim:jar:1.7:compile
[DEBUG] org.apache.xmlgraphics:batik-parser:jar:1.7:compile
[DEBUG] org.apache.xmlgraphics:batik-script:jar:1.7:compile
[DEBUG] org.apache.xmlgraphics:batik-js:jar:1.7:compile
[DEBUG] org.apache.xmlgraphics:batik-xml:jar:1.7:compile
[DEBUG] xalan:xalan:jar:2.6.0:compile
[DEBUG] org.apache.xmlgraphics:batik-css:jar:1.7:compile
[DEBUG] org.apache.xmlgraphics:batik-dom:jar:1.7:compile
[DEBUG] org.apache.xmlgraphics:batik-ext:jar:1.7:compile
[DEBUG] org.apache.xmlgraphics:batik-gui-util:jar:1.7:compile
[DEBUG] org.apache.xmlgraphics:batik-gvt:jar:1.7:compile
[DEBUG] org.apache.xmlgraphics:batik-svg-dom:jar:1.7:compile
[DEBUG] org.apache.xmlgraphics:batik-util:jar:1.7:compile
[DEBUG] xml-apis:xml-apis:jar:1.3.04:compile
[DEBUG] xml-apis:xml-apis-ext:jar:1.3.04:compile
{noformat}.
As mentioned in the compat notes, {{maven-dependency-tree}} couldn't be briged onto Aether and this is one of those corner cases where the discrepancy gets visible.
> dependency:tree omits batik-js
> ------------------------------
>
> Key: MSHARED-167
> URL: http://jira.codehaus.org/browse/MSHARED-167
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-dependency-tree
> Affects Versions: maven-dependency-tree 1.2
> Environment: Maven 3.0, Ubuntu, JDK 6.
> Reporter: Jesse Glick
> Attachments: test_test-dependency-tree_jar_1.0-SNAPSHOT_101018-185145.zip
>
>
> (Not sure what the right place to file this is. {{maven-dependency-tree 1.2}} gives {{MNG}} as the JIRA component by inheritance.)
> {{mvn dependency:tree}} on the attached project lists {{batik-script}} by way of {{batik-bridge}} as expected, but then fails to show {{batik-js}} as a dependency of that. If you list {{batik-script}} as a direct dependency, {{batik-js}} is correctly shown.
> Possibly related is that Maven 2.2.1 also fails to find {{batik-js}} in {{MavenProject.getRuntimeArtifacts}}, so {{clean package}} fails, whereas this works fine under Maven 3.0. Yet just running the dependency plugin under M3 does not suffice to pick up this fix, wherever it was - MNG-4690?
> Although the Batik JARs are built from an odd source tree, the artifacts as present in the local repository look normal enough; all of the dependencies involved are simple compile scope without exclusions etc.
> Marking "major" since this seems to cause MNBMODULE-102 (producing build errors for certain projects); also I have noticed that the dependency graph feature in the NB IDE omits {{batik-js}}, and there may be other user-visible effects of this bug.
--
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
[jira] Commented: (MSHARED-167) dependency:tree omits batik-js
Posted by "Jesse Glick (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSHARED-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=241688#action_241688 ]
Jesse Glick commented on MSHARED-167:
-------------------------------------
The above tree seems to be printed by:
{noformat}
at org.apache.maven.project.DefaultProjectDependenciesResolver$GraphLogger.visitEnter(DefaultProjectDependenciesResolver.java:223)
at org.sonatype.aether.impl.internal.GraphEdge.accept(GraphEdge.java:173)
at org.sonatype.aether.impl.internal.GraphEdge.accept(GraphEdge.java:177)
at org.sonatype.aether.impl.internal.GraphEdge.accept(GraphEdge.java:177)
at org.sonatype.aether.impl.internal.GraphEdge.accept(GraphEdge.java:177)
at org.sonatype.aether.impl.internal.GraphEdge.accept(GraphEdge.java:177)
at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:145)
{noformat}
> dependency:tree omits batik-js
> ------------------------------
>
> Key: MSHARED-167
> URL: http://jira.codehaus.org/browse/MSHARED-167
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-dependency-tree
> Affects Versions: maven-dependency-tree 1.2
> Environment: Maven 3.0, Ubuntu, JDK 6.
> Reporter: Jesse Glick
> Attachments: test_test-dependency-tree_jar_1.0-SNAPSHOT_101018-185145.zip
>
>
> (Not sure what the right place to file this is. {{maven-dependency-tree 1.2}} gives {{MNG}} as the JIRA component by inheritance.)
> {{mvn dependency:tree}} on the attached project lists {{batik-script}} by way of {{batik-bridge}} as expected, but then fails to show {{batik-js}} as a dependency of that. If you list {{batik-script}} as a direct dependency, {{batik-js}} is correctly shown.
> Possibly related is that Maven 2.2.1 also fails to find {{batik-js}} in {{MavenProject.getRuntimeArtifacts}}, so {{clean package}} fails, whereas this works fine under Maven 3.0. Yet just running the dependency plugin under M3 does not suffice to pick up this fix, wherever it was - MNG-4690?
> Although the Batik JARs are built from an odd source tree, the artifacts as present in the local repository look normal enough; all of the dependencies involved are simple compile scope without exclusions etc.
> Marking "major" since this seems to cause MNBMODULE-102 (producing build errors for certain projects); also I have noticed that the dependency graph feature in the NB IDE omits {{batik-js}}, and there may be other user-visible effects of this bug.
--
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
[jira] Commented: (MSHARED-167) dependency:tree omits batik-js
Posted by "Jesse Glick (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MSHARED-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274422#comment-274422 ]
Jesse Glick commented on MSHARED-167:
-------------------------------------
Possibly related to MNG-4982?
> dependency:tree omits batik-js
> ------------------------------
>
> Key: MSHARED-167
> URL: https://jira.codehaus.org/browse/MSHARED-167
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-dependency-tree
> Affects Versions: maven-dependency-tree-1.2
> Environment: Maven 3.0, Ubuntu, JDK 6.
> Reporter: Jesse Glick
> Attachments: test_test-dependency-tree_jar_1.0-SNAPSHOT_101018-185145.zip
>
>
> (Not sure what the right place to file this is. {{maven-dependency-tree 1.2}} gives {{MNG}} as the JIRA component by inheritance.)
> {{mvn dependency:tree}} on the attached project lists {{batik-script}} by way of {{batik-bridge}} as expected, but then fails to show {{batik-js}} as a dependency of that. If you list {{batik-script}} as a direct dependency, {{batik-js}} is correctly shown.
> Possibly related is that Maven 2.2.1 also fails to find {{batik-js}} in {{MavenProject.getRuntimeArtifacts}}, so {{clean package}} fails, whereas this works fine under Maven 3.0. Yet just running the dependency plugin under M3 does not suffice to pick up this fix, wherever it was - MNG-4690?
> Although the Batik JARs are built from an odd source tree, the artifacts as present in the local repository look normal enough; all of the dependencies involved are simple compile scope without exclusions etc.
> Marking "major" since this seems to cause MNBMODULE-102 (producing build errors for certain projects); also I have noticed that the dependency graph feature in the NB IDE omits {{batik-js}}, and there may be other user-visible effects of this bug.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSHARED-167) dependency:tree omits batik-js
Posted by "Jesse Glick (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MSHARED-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=281317#comment-281317 ]
Jesse Glick commented on MSHARED-167:
-------------------------------------
I do not have commit privileges, so:
{code}
Index: src/main/java/org/apache/maven/plugin/dependency/TreeMojo.java
===================================================================
--- src/main/java/org/apache/maven/plugin/dependency/TreeMojo.java (revision 1183422)
+++ src/main/java/org/apache/maven/plugin/dependency/TreeMojo.java (working copy)
@@ -65,7 +65,7 @@
/**
* Displays the dependency tree for this project.
- *
+ * Beware that due to <a href="https://jira.codehaus.org/browse/MSHARED-167">MSHARED-167</a> the result may be incorrect in obscure cases.
* @author <a href="mailto:markhobson@gmail.com">Mark Hobson</a>
* @version $Id$
* @since 2.0-alpha-5
{code}
> dependency:tree omits batik-js
> ------------------------------
>
> Key: MSHARED-167
> URL: https://jira.codehaus.org/browse/MSHARED-167
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-dependency-tree
> Affects Versions: maven-dependency-tree-1.2
> Environment: Maven 3.0, Ubuntu, JDK 6.
> Reporter: Jesse Glick
> Attachments: test_test-dependency-tree_jar_1.0-SNAPSHOT_101018-185145.zip
>
>
> (Not sure what the right place to file this is. {{maven-dependency-tree 1.2}} gives {{MNG}} as the JIRA component by inheritance.)
> {{mvn dependency:tree}} on the attached project lists {{batik-script}} by way of {{batik-bridge}} as expected, but then fails to show {{batik-js}} as a dependency of that. If you list {{batik-script}} as a direct dependency, {{batik-js}} is correctly shown.
> Possibly related is that Maven 2.2.1 also fails to find {{batik-js}} in {{MavenProject.getRuntimeArtifacts}}, so {{clean package}} fails, whereas this works fine under Maven 3.0. Yet just running the dependency plugin under M3 does not suffice to pick up this fix, wherever it was - MNG-4690?
> Although the Batik JARs are built from an odd source tree, the artifacts as present in the local repository look normal enough; all of the dependencies involved are simple compile scope without exclusions etc.
> Marking "major" since this seems to cause MNBMODULE-102 (producing build errors for certain projects); also I have noticed that the dependency graph feature in the NB IDE omits {{batik-js}}, and there may be other user-visible effects of this bug.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSHARED-167) dependency:tree omits batik-js
Posted by "David Tombs (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MSHARED-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=278762#comment-278762 ]
David Tombs commented on MSHARED-167:
-------------------------------------
This issue just caused me some grief. Could this discrepancy between dependency:tree and the actual tree used possibly be documented in the dependency:tree docs?
> dependency:tree omits batik-js
> ------------------------------
>
> Key: MSHARED-167
> URL: https://jira.codehaus.org/browse/MSHARED-167
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-dependency-tree
> Affects Versions: maven-dependency-tree-1.2
> Environment: Maven 3.0, Ubuntu, JDK 6.
> Reporter: Jesse Glick
> Attachments: test_test-dependency-tree_jar_1.0-SNAPSHOT_101018-185145.zip
>
>
> (Not sure what the right place to file this is. {{maven-dependency-tree 1.2}} gives {{MNG}} as the JIRA component by inheritance.)
> {{mvn dependency:tree}} on the attached project lists {{batik-script}} by way of {{batik-bridge}} as expected, but then fails to show {{batik-js}} as a dependency of that. If you list {{batik-script}} as a direct dependency, {{batik-js}} is correctly shown.
> Possibly related is that Maven 2.2.1 also fails to find {{batik-js}} in {{MavenProject.getRuntimeArtifacts}}, so {{clean package}} fails, whereas this works fine under Maven 3.0. Yet just running the dependency plugin under M3 does not suffice to pick up this fix, wherever it was - MNG-4690?
> Although the Batik JARs are built from an odd source tree, the artifacts as present in the local repository look normal enough; all of the dependencies involved are simple compile scope without exclusions etc.
> Marking "major" since this seems to cause MNBMODULE-102 (producing build errors for certain projects); also I have noticed that the dependency graph feature in the NB IDE omits {{batik-js}}, and there may be other user-visible effects of this bug.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (MSHARED-167) dependency:tree omits batik-js
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSHARED-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann moved MNG-4870 to MSHARED-167:
------------------------------------------------
Complexity: (was: Intermediate)
Component/s: (was: Dependencies)
maven-dependency-tree
Affects Version/s: (was: 3.0)
maven-dependency-tree 1.2
Key: MSHARED-167 (was: MNG-4870)
Project: Maven Shared Components (was: Maven 2 & 3)
> dependency:tree omits batik-js
> ------------------------------
>
> Key: MSHARED-167
> URL: http://jira.codehaus.org/browse/MSHARED-167
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-dependency-tree
> Affects Versions: maven-dependency-tree 1.2
> Environment: Maven 3.0, Ubuntu, JDK 6.
> Reporter: Jesse Glick
> Attachments: test_test-dependency-tree_jar_1.0-SNAPSHOT_101018-185145.zip
>
>
> (Not sure what the right place to file this is. {{maven-dependency-tree 1.2}} gives {{MNG}} as the JIRA component by inheritance.)
> {{mvn dependency:tree}} on the attached project lists {{batik-script}} by way of {{batik-bridge}} as expected, but then fails to show {{batik-js}} as a dependency of that. If you list {{batik-script}} as a direct dependency, {{batik-js}} is correctly shown.
> Possibly related is that Maven 2.2.1 also fails to find {{batik-js}} in {{MavenProject.getRuntimeArtifacts}}, so {{clean package}} fails, whereas this works fine under Maven 3.0. Yet just running the dependency plugin under M3 does not suffice to pick up this fix, wherever it was - MNG-4690?
> Although the Batik JARs are built from an odd source tree, the artifacts as present in the local repository look normal enough; all of the dependencies involved are simple compile scope without exclusions etc.
> Marking "major" since this seems to cause MNBMODULE-102 (producing build errors for certain projects); also I have noticed that the dependency graph feature in the NB IDE omits {{batik-js}}, and there may be other user-visible effects of this bug.
--
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
[jira] Commented: (MSHARED-167) dependency:tree omits batik-js
Posted by "Jesse Glick (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSHARED-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=240144#action_240144 ]
Jesse Glick commented on MSHARED-167:
-------------------------------------
I see. Should maven-dependency-tree then be considered fully deprecated? If so, is there some plan to release a fixed maven-dependency-plugin; and is there some documentation on which API in Maven core (or Aether) should be used in place of the deprecated component?
> dependency:tree omits batik-js
> ------------------------------
>
> Key: MSHARED-167
> URL: http://jira.codehaus.org/browse/MSHARED-167
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-dependency-tree
> Affects Versions: maven-dependency-tree 1.2
> Environment: Maven 3.0, Ubuntu, JDK 6.
> Reporter: Jesse Glick
> Attachments: test_test-dependency-tree_jar_1.0-SNAPSHOT_101018-185145.zip
>
>
> (Not sure what the right place to file this is. {{maven-dependency-tree 1.2}} gives {{MNG}} as the JIRA component by inheritance.)
> {{mvn dependency:tree}} on the attached project lists {{batik-script}} by way of {{batik-bridge}} as expected, but then fails to show {{batik-js}} as a dependency of that. If you list {{batik-script}} as a direct dependency, {{batik-js}} is correctly shown.
> Possibly related is that Maven 2.2.1 also fails to find {{batik-js}} in {{MavenProject.getRuntimeArtifacts}}, so {{clean package}} fails, whereas this works fine under Maven 3.0. Yet just running the dependency plugin under M3 does not suffice to pick up this fix, wherever it was - MNG-4690?
> Although the Batik JARs are built from an odd source tree, the artifacts as present in the local repository look normal enough; all of the dependencies involved are simple compile scope without exclusions etc.
> Marking "major" since this seems to cause MNBMODULE-102 (producing build errors for certain projects); also I have noticed that the dependency graph feature in the NB IDE omits {{batik-js}}, and there may be other user-visible effects of this bug.
--
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