Overridden artifact finalName with classifier is ignored by the assembly plugin.
--------------------------------------------------------------------------------
Key: MASSEMBLY-339
URL: http://jira.codehaus.org/browse/MASSEMBLY-339
Project: Maven 2.x Assembly Plugin
Issue Type: Bug
Affects Versions: 2.2-beta-1
Environment: Maven 2.0.9, JDK 6, WinXP SP2
Reporter: Michael Osipov
Attachments: assemblyClassifierMapping.png
I have a multimodule project.
groupId: net.fckeditor
Parent ArtifactId: fckeditor-java
1. module ArtifactId: java-core; finalName "fckeditor-${artifactId}-${version}"
though => e.g. fckeditor-java-core-2.4-SNAPSHOT
2. module ArtifactId: java-demo; finalName "fckeditor-${artifactId}-${version}"
though
I did create a bin assembly. The assembly contains the javadoc jars but their
names do not correspond to the overridden finalNames.
The javadoc:jar genereation is bound to the package phase.
An example picture is attached and the project can be checked out at our
[trac|http://dev.fckeditor.net/browser/FCKeditor.Java/trunk] and the
[SVN|http://svn.fckeditor.net/FCKeditor.Java/trunk/] directly.
Checkout the
[bin.xml|http://dev.fckeditor.net/browser/FCKeditor.Java/trunk/src/main/assembly/bin.xml]
and comment out the second outputFileNameMapping and run "mvn clean site
package assembly:assembly".
You should be able to reproduce the problem.
I did find a workaround for the problem by defining the outputFileNameMapping
as same as in the modules poms. This works just because all modules have the
same finalName remapping.
--
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
