[jira] Commented: (MASSEMBLY-338) Overridden artifact finalName is ignored by the assembly plugin.

["Geert Schuring (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MASSEMBLY-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=150495#action_150495 ] 

Geert Schuring commented on MASSEMBLY-338:
------------------------------------------

I have the same problem. According to the assembly plugin documentation, one should be able to set the finalName in the configuration of the plugin.

See [http://maven.apache.org/plugins/maven-assembly-plugin/assembly-mojo.html]

However, the assembly plugin ignores this. I need the jar file the have a certain name, which is currently impossible.



> Overridden artifact finalName is ignored by the assembly plugin.
> ----------------------------------------------------------------
>
>                 Key: MASSEMBLY-338
>                 URL: http://jira.codehaus.org/browse/MASSEMBLY-338
>             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: assemblyMapping.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 jars but their names do not correspond to the overridden finalNames.
> 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 first 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