[jira] (MASSEMBLY-669) dependencySet does not resolve transient dependencies in reactor build
[
https://jira.codehaus.org/browse/MASSEMBLY-669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=342775#comment-342775
]
Christoph commented on MASSEMBLY-669:
-
In the first example each artifact has the same version. Only dependencies are
specified as ranges (never mind wrong syntax). I would say, this is a reactor.
At least maven tells me
[INFO] Reactor Build Order:
[INFO]
[INFO] reactor
[INFO] one
[INFO] two
[INFO] three
{{mvn compile}} works and resolves each dependency within the reactor. {{mvn
install}} from the root project will also work, because the reactor sorts the
order and runs, compile, package, install on each project in the correct order.
But any dependency resolution in the package phase happens against the
repository, not against the reactor.
This is also the case for {{mvn dependency:list}}. Ranges are resolved against
the repository not the reactor. So this might be a bug or feature of the
dependency resolution. See for example MDEP-410
> 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)
[jira] (MASSEMBLY-669) dependencySet does not resolve transient dependencies in reactor build
[
https://jira.codehaus.org/browse/MASSEMBLY-669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise closed MASSEMBLY-669.
-
Resolution: Not A Bug
Unfortunately i have to say that one very important thing about your
assumptions is incorrect:
The senctence:
{{using an assembly descriptor with a dependencySet will fail to resolve
transient dependencies that are build in the same reactor}}
These artifacts are not build in the same reactor. This is only an aggregator
and *not* an multi-module build.
Apart from that if you take a look at the error message:
{{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,]}}
This shows that the build is trying to solve the artifacts from the repository
as a result of not finding them within the current reactor.
An indicator for a multi-module build is the verison number which is identical
for all modules etc. within the same folder structure (parent, modules etc.)
which is *not* the case with your example. You have the same parent but the
versions are different. The conclusion of this is that you neither have an
aggregator nor an multi-module buld.
You can find it out via first doing:
{{mvn install -N} from the root of your project.
{{mvn install}} from module one.
{{mvn install}} from module two and finally:
{{mvn package}} from module threeor after installing module two going to
the root and do {{mvn clean package}} which will works.
So the result of this is: It's not bug, cause you are not building in the same
reactor.
> 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)
[jira] (MASSEMBLY-669) dependencySet does not resolve transient dependencies in reactor build
[ 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)
[jira] (MASSEMBLY-669) dependencySet does not resolve transient dependencies in reactor build
[ https://jira.codehaus.org/browse/MASSEMBLY-669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christoph updated MASSEMBLY-669: Attachment: assembly_bug_v2.tar.gz updated example with corrected version ranges and different artifact versions > 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)
[jira] (MASSEMBLY-669) dependencySet does not resolve transient dependencies in reactor build
[
https://jira.codehaus.org/browse/MASSEMBLY-669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise closed MASSEMBLY-669.
-
Resolution: Not A Bug
The first problem i see in your example is that your given [version ranges are
wrong|http://maven.apache.org/enforcer/enforcer-rules/versionRanges.html] cause
what you wrote in your dependencies is:
{{[0,]}} which means 0 <= x <= ?
So the question is what represent the "?"
So in other words i see the error message as a correct one cause an artifact
with the given version 0.. does not exist only artifacts with versio {{1.0.0}}
do exist.
Apart from that i would ask why are you using version ranges in that case this
can simply solved by using {{$\{project.version\}}} so no need for them.
So i will close the issue. If you have further details please don't hesitate to
reopen the issue.
> 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
>
>
> 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)
[jira] (MASSEMBLY-669) dependencySet does not resolve transient dependencies in reactor build
[ https://jira.codehaus.org/browse/MASSEMBLY-669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christoph updated MASSEMBLY-669: Description: 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. was: 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. Where artifact three depends on artifact two. And artifact two depends on artifact 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. > 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 > > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MASSEMBLY-669) dependencySet does not resolve transient dependencies in reactor build
Christoph created MASSEMBLY-669: --- Summary: 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.4, 2.2-beta-5 Environment: linux Reporter: Christoph Attachments: assembly_bug.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. Where artifact three depends on artifact two. And artifact two depends on artifact 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
