You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Richard Kerr (JIRA)" <ji...@codehaus.org> on 2011/09/09 18:15:32 UTC
[jira] Reopened: (MASSEMBLY-572) outputFileNameMapping does not
account for custom build.finalName value
[ https://jira.codehaus.org/browse/MASSEMBLY-572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Richard Kerr reopened MASSEMBLY-572:
------------------------------------
Accidently opened, will close it properly this time =/
> outputFileNameMapping does not account for custom build.finalName value
> -----------------------------------------------------------------------
>
> Key: MASSEMBLY-572
> URL: https://jira.codehaus.org/browse/MASSEMBLY-572
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
> Affects Versions: 2.2.1
> Environment: Running under Windows Vista
> Reporter: Richard Kerr
> Priority: Minor
>
> I have a project where one of the artifacts (a WAR) has a custom build.finalName value.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira