You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "John Casey (JIRA)" <ji...@codehaus.org> on 2008/03/25 00:19:58 UTC
[jira] Closed: (MASSEMBLY-270) Assembly does not resolved managed
dependencies correctly
[ http://jira.codehaus.org/browse/MASSEMBLY-270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Casey closed MASSEMBLY-270.
--------------------------------
Assignee: John Casey
Resolution: Fixed
Fix Version/s: 2.2-beta-3
Just verified that this has been fixed in 2.2-beta-2.
> Assembly does not resolved managed dependencies correctly
> ---------------------------------------------------------
>
> Key: MASSEMBLY-270
> URL: http://jira.codehaus.org/browse/MASSEMBLY-270
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2-beta-1
> Reporter: Brian Jackson
> Assignee: John Casey
> Fix For: 2.2-beta-3
>
> Attachments: dependency-bug.zip
>
>
> The assembly plugin does not resolve the version number correctly for a managed transitive dependency. The result is the jar-with-dependencies assembly will include a different version of the transitive dependency than the version that is reported dependency and project-info-reports plugins report.
> Steps to reproduce bug
> --------------
> 1) Extract the dependencybug.zip
> 2) cd dependencybug-c
> 3) mvn install
> 4) open the pom.xml and change the version to 2.0
> 5) mvn install
> 6) cd ../dependencybug-b
> 7) mvn install
> 8) cd ../dependencybug-a
> Now within the dependencybug-a project compare the results of:
> ==============================================
> mvn dependency:resolve
> ------------------------------------------
> Resolves dependencybug-c to version 2.0
> ------------------------------------------
> [INFO] [dependency:resolve]
> [INFO]
> [INFO] The following files have been resolved:
> ...
> [INFO] com.espn.test.dependencybug:dependencybug-c:jar:2.0 (scope = compile)
> ...
> ==============================================
> mvn org.apache.maven.plugins:maven-dependency-plugin:2.0-alpha-5-SNAPSHOT:tree
> ------------------------------------------
> Resolves dependencybug-c to version 2.0
> ------------------------------------------
> [INFO] [dependency:tree]
> [INFO] com.espn.test.dependencybug:dependencybug-a:jar:1.0-SNAPSHOT
> [INFO] +- com.espn.test.dependencybug:dependencybug-b:jar:1.0-SNAPSHOT:compile
> [INFO] | \- com.espn.test.dependencybug:dependencybug-c:jar:2.0:compile (version managed from 1.0)
> ...
> ==============================================
> mvn project-info-reports:dependencies
> ------------------------------------------
> Resolves dependencybug-c to version 2.0
> ------------------------------------------
> target/site/dependencies.html:
> ...
> GroupId ArtifactId Version Classifier Type Optional
> com.espn.test.dependencybug dependencybug-c 2.0 - jar
> ....
> ==============================================
> mvn assembly:assembly
> ------------------------------------------
> Resolves dependencybug-c to version 1.0 !!!!
> ------------------------------------------
> [INFO] [jar:jar]
> [INFO] Building jar: C:\Documents and Settings\jacksbrr\My Documents\Projects\dependency-bug\dependencybug-a\target\dependencybug-a-1.0-SNAPSHOT.jar
> [INFO] [assembly:assembly]
> [INFO] Processing DependencySet (output=)
> [INFO] Expanding: C:\Documents and Settings\jacksbrr\.m2\repository\com\espn\test\dependencybug\dependencybug-b\1.0-SNAPSHOT\dependencybug-b-1.0-SNAPSHOT.jar into C:\DOCUME~1\jacksbrr\LOCALS~1\Temp\archived-file-set.1539373911.tmp
> [INFO] Expanding: C:\Documents and Settings\jacksbrr\.m2\repository\com\espn\test\dependencybug\dependencybug-c\1.0\dependencybug-c-1.0.jar into C:\DOCUME~1\jacksbrr\LOCALS~1\Temp\archived-file-set.148071824.tmp
> [INFO] Building jar: C:\Documents and Settings\jacksbrr\My Documents\Projects\dependency-bug\dependencybug-a\target\dependencybug-a-1.0-SNAPSHOT-jar-with-dependencies.jar
> ==============================================
--
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