[
https://jira.codehaus.org/browse/MASSEMBLY-669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christoph reopened MASSEMBLY-669:
---------------------------------
The example has been corrected but the problem persists.
Now each project in the reactor uses it's own version. As it's only an example
we have independent versioning on submodules.
> dependencySet does not resolve transient dependencies in reactor build
> ----------------------------------------------------------------------
>
> Key: MASSEMBLY-669
> URL: https://jira.codehaus.org/browse/MASSEMBLY-669
> Project: Maven Assembly Plugin
> Issue Type: Bug
> Components: dependencySet
> Affects Versions: 2.2-beta-5, 2.4
> Environment: linux
> Reporter: Christoph
> Attachments: assembly_bug.tar.gz, assembly_bug_v2.tar.gz
>
>
> using an assembly descriptor with a dependencySet will fail to resolve
> transient dependencies that are build in the same reactor.
> having artifacts one, two, three. With a dependeny chain: three -> two -> one
> Artifact three runs an assembly during package phase. It succeeds in finding
> the artifact two in the reactor. But the transient dependency pointing to
> artifact one can't be resolved.
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-assembly-plugin:2.4:single (make-assembly) on
> project three: Failed to create assembly: Unable to resolve dependencies for
> assembly 'foo': Failed to resolve dependencies for assembly: No versions are
> present in the repository for the artifact with a range [0,]
> [ERROR] de.gsi.cs.co.maven.assembly_bug:one:jar:null
> A sample project structure is attached.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
