[
https://jira.codehaus.org/browse/MASSEMBLY-558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg updated MASSEMBLY-558:
--------------------------------------
Component/s: dependencySet
Description:
In my project there's an artifact, which can be resolved by 2 different paths
(scopes in brackets)
{noformat}
a) Project->projA(compile)->projB(compile)->myArtifact(runtime)
b) Project->projB(test)->myArtifact(runtime)
{noformat}
The relevant part of the distribution descriptor is the following
{code:xml}
<formats>
<format>zip</format>
</formats>
<dependencySets>
<dependencySet>
<outputDirectory>/lib</outputDirectory>
<useProjectArtifact>true</useProjectArtifact>
<unpack>false</unpack>
<scope>runtime</scope>
</dependencySet>
</dependencySets>
{code}
So when I run assembly:assembly I wonder, why myArtifact isn't included in my
zip. I now think, that assembly favours the shorter path b) despite the
test-scope over the longer but correct path a).
Since test-scope dependencies should have nothing to do with distribution (if
not included explicitly) myArtifact should have be included in my zip.
was:
In my project there's an artifact, which can be resolved by 2 different paths
(scopes in brackets)
a) Project->projA(compile)->projB(compile)->myArtifact(runtime)
b) Project->projB(test)->myArtifact(runtime)
The relevant part of the distribution descriptor is thhe following
<formats>
<format>zip</format>
</formats>
<dependencySets>
<dependencySet>
<outputDirectory>/lib</outputDirectory>
<useProjectArtifact>true</useProjectArtifact>
<unpack>false</unpack>
<scope>runtime</scope>
</dependencySet>
</dependencySets>
So when I run assembly:assembly I wonder, why myArtifact isn't included in my
zip. I now think, that assembly favours the shorter path b) despite the
test-scope over the longer but correct path a).
Since test-scope dependencies should have nothing to do with distribution (if
not included explicitly) myArtifact should have be included in my zip.
> Assembly does not include runtime-dependency if test-dependency with shorter
> path exists
> ----------------------------------------------------------------------------------------
>
> Key: MASSEMBLY-558
> URL: https://jira.codehaus.org/browse/MASSEMBLY-558
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Components: dependencySet
> Affects Versions: 2.2
> Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100)
> Java version: 1.5.0_12, vendor: Sun Microsystems Inc.
> Default locale: de_DE, platform encoding: Cp1252
> OS name: "windows xp", version: "5.1", arch: "x86", family: "windows"
> Reporter: Frank Jakop
>
> In my project there's an artifact, which can be resolved by 2 different paths
> (scopes in brackets)
> {noformat}
> a) Project->projA(compile)->projB(compile)->myArtifact(runtime)
> b) Project->projB(test)->myArtifact(runtime)
> {noformat}
> The relevant part of the distribution descriptor is the following
> {code:xml}
> <formats>
> <format>zip</format>
> </formats>
> <dependencySets>
> <dependencySet>
> <outputDirectory>/lib</outputDirectory>
> <useProjectArtifact>true</useProjectArtifact>
> <unpack>false</unpack>
> <scope>runtime</scope>
> </dependencySet>
> </dependencySets>
> {code}
> So when I run assembly:assembly I wonder, why myArtifact isn't included in my
> zip. I now think, that assembly favours the shorter path b) despite the
> test-scope over the longer but correct path a).
> Since test-scope dependencies should have nothing to do with distribution (if
> not included explicitly) myArtifact should have be included in my zip.
--
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
