You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Arnaud Heritier (JIRA)" <ji...@codehaus.org> on 2012/12/04 23:08:15 UTC
[jira] (MDEP-392) dependency:tree is erroneous with Maven 3 (3.0.4
or 3.1-SNAPSHOT)
Arnaud Heritier created MDEP-392:
------------------------------------
Summary: dependency:tree is erroneous with Maven 3 (3.0.4 or 3.1-SNAPSHOT)
Key: MDEP-392
URL: https://jira.codehaus.org/browse/MDEP-392
Project: Maven 2.x Dependency Plugin
Issue Type: Bug
Components: tree
Affects Versions: 2.6
Environment: Java 6
Reporter: Arnaud Heritier
Priority: Critical
Attachments: dependency-tree-mvn-2.2.1.txt, dependency-tree-mvn-3.1-SNAPSHOT.txt
I have a complex project with many deps, many depsMgt import ...
https://github.com/exoplatform/platform-tomcat-standalone
I discovered the issue on rev fb36980
I was trying to blacklist all servlet/jsp dependencies coming projects dependencies (searching them with dependency:tree -Dverbose -Dincludes=*:*servlet*:*).
The plugin reported that there was no such dep in my graph after all my exclusions and cleanup in low level projects.
But it was false because the assembly plugin continued to find such deps and copied them in my distribution.
Downgrading to Maven 2.2.1 allowed me to find some of these dependencies that I didn't found with 3.1 (see commit https://github.com/exoplatform/platform-tomcat-standalone/commit/67eb23a8b6e033cecbd1d1726ff75afebdd0fdfd)
Note : this bug is probably something low level because the enforcer plugin has it too. It didn't discover/reported the dependency I wanted to blacklist
--
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-392) dependency:tree -Dincludes is erroneous with
Maven 3 (3.0.4 or 3.1-SNAPSHOT)
Posted by "Herve Boutemy (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MDEP-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Herve Boutemy updated MDEP-392:
-------------------------------
Summary: dependency:tree -Dincludes is erroneous with Maven 3 (3.0.4 or 3.1-SNAPSHOT) (was: dependency:tree is erroneous with Maven 3 (3.0.4 or 3.1-SNAPSHOT))
> dependency:tree -Dincludes is erroneous with Maven 3 (3.0.4 or 3.1-SNAPSHOT)
> ----------------------------------------------------------------------------
>
> Key: MDEP-392
> URL: https://jira.codehaus.org/browse/MDEP-392
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Components: tree
> Affects Versions: 2.6
> Environment: Java 6
> Reporter: Arnaud Heritier
> Priority: Critical
> Attachments: dependency-tree-mvn-2.2.1.txt, dependency-tree-mvn-3.1-SNAPSHOT.txt
>
>
> I have a complex project with many deps, many depsMgt import ...
> https://github.com/exoplatform/platform-tomcat-standalone
> I discovered the issue on rev fb36980
> I was trying to blacklist all servlet/jsp dependencies coming projects dependencies (searching them with dependency:tree -Dverbose -Dincludes=*:*servlet*:*).
> The plugin reported that there was no such dep in my graph after all my exclusions and cleanup in low level projects.
> But it was false because the assembly plugin continued to find such deps and copied them in my distribution.
> Downgrading to Maven 2.2.1 allowed me to find some of these dependencies that I didn't found with 3.1 (see commit https://github.com/exoplatform/platform-tomcat-standalone/commit/67eb23a8b6e033cecbd1d1726ff75afebdd0fdfd)
> Note : this bug is probably something low level because the enforcer plugin has it too. It didn't discover/reported the dependency I wanted to blacklist
--
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-392) dependency:tree is erroneous with Maven 3 (3.0.4
or 3.1-SNAPSHOT)
Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MDEP-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=315011#comment-315011 ]
Olivier Lamy commented on MDEP-392:
-----------------------------------
need this repository: http://repository.exoplatform.org/public/
> dependency:tree is erroneous with Maven 3 (3.0.4 or 3.1-SNAPSHOT)
> -----------------------------------------------------------------
>
> Key: MDEP-392
> URL: https://jira.codehaus.org/browse/MDEP-392
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Components: tree
> Affects Versions: 2.6
> Environment: Java 6
> Reporter: Arnaud Heritier
> Priority: Critical
> Attachments: dependency-tree-mvn-2.2.1.txt, dependency-tree-mvn-3.1-SNAPSHOT.txt
>
>
> I have a complex project with many deps, many depsMgt import ...
> https://github.com/exoplatform/platform-tomcat-standalone
> I discovered the issue on rev fb36980
> I was trying to blacklist all servlet/jsp dependencies coming projects dependencies (searching them with dependency:tree -Dverbose -Dincludes=*:*servlet*:*).
> The plugin reported that there was no such dep in my graph after all my exclusions and cleanup in low level projects.
> But it was false because the assembly plugin continued to find such deps and copied them in my distribution.
> Downgrading to Maven 2.2.1 allowed me to find some of these dependencies that I didn't found with 3.1 (see commit https://github.com/exoplatform/platform-tomcat-standalone/commit/67eb23a8b6e033cecbd1d1726ff75afebdd0fdfd)
> Note : this bug is probably something low level because the enforcer plugin has it too. It didn't discover/reported the dependency I wanted to blacklist
--
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-392) dependency:tree is erroneous with Maven 3 (3.0.4
or 3.1-SNAPSHOT)
Posted by "Arnaud Heritier (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MDEP-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=315012#comment-315012 ]
Arnaud Heritier commented on MDEP-392:
--------------------------------------
Ipushed a branch MDEP-392 in this project to help to reproduce it : https://github.com/exoplatform/platform-tomcat-standalone/tree/MDEP-392
You may need this repository http://repository.exoplatform.org/public/
Then with Maven 3.x:
{code}
mvn dependency:tree -Dverbose -Dincludes=javax.servlet:servlet-api:*
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building eXo Platform Tomcat Standalone Package 4.0.0.Alpha1-kill-exobuild-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-dependency-plugin:2.6:tree (default-cli) @ platform-tomcat-standalone ---
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 24.901s
[INFO] Finished at: Tue Dec 04 23:25:22 CET 2012
[INFO] Final Memory: 34M/125M
[INFO] ------------------------------------------------------------------------
{code}
With Maven 2.2.1:
{code}
mvn dependency:tree -Dverbose -Dincludes=javax.servlet:servlet-api:*
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'dependency'.
[INFO] ------------------------------------------------------------------------
[INFO] Building eXo Platform Tomcat Standalone Package
[INFO] task-segment: [dependency:tree]
[INFO] ------------------------------------------------------------------------
[INFO] [dependency:tree {execution: default-cli}]
[INFO] org.exoplatform.platform.pkg:platform-tomcat-standalone:pom:4.0.0.Alpha1-kill-exobuild-SNAPSHOT
[INFO] \- org.exoplatform.portal:exo.portal.component.management:jar:3.4.0.Final:compile
[INFO] \- org.exoplatform.ws:exo.ws.rest.core:jar:2.2.10-GA-SNAPSHOT:compile
[INFO] \- javax.servlet:servlet-api:jar:2.5:compile
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 15 seconds
[INFO] Finished at: Tue Dec 04 23:28:17 CET 2012
[INFO] Final Memory: 127M/239M
[INFO] ------------------------------------------------------------------------
{code}
I hope that SNAPSHOTs deps will be always available to allow you to reproduce it
For now I didn't find how to easily debug this problem
> dependency:tree is erroneous with Maven 3 (3.0.4 or 3.1-SNAPSHOT)
> -----------------------------------------------------------------
>
> Key: MDEP-392
> URL: https://jira.codehaus.org/browse/MDEP-392
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Components: tree
> Affects Versions: 2.6
> Environment: Java 6
> Reporter: Arnaud Heritier
> Priority: Critical
> Attachments: dependency-tree-mvn-2.2.1.txt, dependency-tree-mvn-3.1-SNAPSHOT.txt
>
>
> I have a complex project with many deps, many depsMgt import ...
> https://github.com/exoplatform/platform-tomcat-standalone
> I discovered the issue on rev fb36980
> I was trying to blacklist all servlet/jsp dependencies coming projects dependencies (searching them with dependency:tree -Dverbose -Dincludes=*:*servlet*:*).
> The plugin reported that there was no such dep in my graph after all my exclusions and cleanup in low level projects.
> But it was false because the assembly plugin continued to find such deps and copied them in my distribution.
> Downgrading to Maven 2.2.1 allowed me to find some of these dependencies that I didn't found with 3.1 (see commit https://github.com/exoplatform/platform-tomcat-standalone/commit/67eb23a8b6e033cecbd1d1726ff75afebdd0fdfd)
> Note : this bug is probably something low level because the enforcer plugin has it too. It didn't discover/reported the dependency I wanted to blacklist
--
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