You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brian Fox (JIRA)" <ji...@codehaus.org> on 2008/01/01 02:37:57 UTC
[jira] Closed: (MDEP-110) Cannot automatically resolve version for
transitive dependencies
[ http://jira.codehaus.org/browse/MDEP-110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Fox closed MDEP-110.
--------------------------
Resolution: Won't Fix
The unpack/copy goals aren't doing transitive dependency resolution; the version of the artifact you want must be defined in the pom hierarchy. If you want to get full transitive resolution, you can use the copy/unpack-dependencies goals along with the includes, excludes filters to get the ones you want.
> Cannot automatically resolve version for transitive dependencies
> ----------------------------------------------------------------
>
> Key: MDEP-110
> URL: http://jira.codehaus.org/browse/MDEP-110
> Project: Maven 2.x Dependency Plugin
> Issue Type: Bug
> Components: unpack
> Affects Versions: 2.0-alpha-4
> Reporter: Daniel Siegmann
> Assignee: Brian Fox
> Priority: Minor
> Attachments: unpack-test.zip
>
>
> When using dependency:unpack it is not normally necessary to specify the version for dependencies - the version is determined from settings in the POM. However, this does not work for transitive dependencies.
> For example, consider modules A and B with a dependency tree B -> A -> commons-lang. In module B we have dependency:unpack try to unpack commons-lang, without specifying a version. This will fail with the following error message, even though the version of this dependency is specified in A.
> [INFO] [dependency:unpack {execution: unpack}]
> [INFO] Configured Artifact: commons-lang:commons-lang:?:jar
> [INFO] ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] Unable to find artifact version of commons-lang:commons-lang in either dependency list or in project's dependency management.
> [INFO] ------------------------------------------------------------------------
> The attached example should demonstrate this problem (commons-lang chosen for no particular reason).
--
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