DpendencySet doesn't work anymore when taken from executedProject
-----------------------------------------------------------------
Key: MASSEMBLY-124
URL: http://jira.codehaus.org/browse/MASSEMBLY-124
Project: Maven 2.x Assembly Plugin
Type: Bug
Versions: 2.2
Environment: maven 2.0.4
Reporter: Jerome Lacoste
Priority: Blocker
Attachments: patch.diff
One of my project build just broke after an upgrade to the latest plugins.
assembly contains:
<dependencySets>
<dependencySet>
<outputDirectory>lib</outputDirectory>
<unpack>false</unpack>
<scope>runtime</scope>
</dependencySet>
If I add a logging to the DirectoryMojo class I can see that no dependencies
are seen for the project.
+ getLog().debug( "DependencySet[" + output + "]" + "
allDependencies: " + allDependencyArtifacts.size()
+ + " filtered: " + dependencyArtifacts.size() );
+
[INFO] [assembly:directory]
[...]
[DEBUG] DependencySet[ubd-1.0.1-SNAPSHOT/lib/] dir perms: 40755 file perms:
100644
[DEBUG] DependencySet[ubd-1.0.1-SNAPSHOT/lib/] allDependencies: 0 filtered: 0
[...]
If I force the plugin to use the original project (not the executedProject),
assembly works again (see patch).
As such, this issue very similar to the MCLIRR-2 one encountered by Vincent.
--
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