[
https://issues.apache.org/jira/browse/MASSEMBLY-817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15831448#comment-15831448
]
Robert Klaus commented on MASSEMBLY-817:
----------------------------------------
I see one problem with build/finalName. We often have one module that is
dedicated to packaging the build result and is using assembly plugin for this.
For this we often have multiple formats and multiple executions of the assembly
plugin.
One possibility is to append the assembly descriptor. But often we just simply
want to give the result the name we want it to have later on - that's what we
use the configuration in each execution to rename it to something readable.
So it is problematic when packaging multiple artifacts when just having one
configuration (build + finalName) for setting the name.
On a sidenote: We initially tried to create an issue for this. But this Jira
had some technical problems back then and reported an error instead. It seems
the issue was actually created: see MASSEMBLY-845
> Make finalName readonly parameter
> ---------------------------------
>
> Key: MASSEMBLY-817
> URL: https://issues.apache.org/jira/browse/MASSEMBLY-817
> Project: Maven Assembly Plugin
> Issue Type: Improvement
> Reporter: Anders Hammar
> Assignee: Robert Scholte
> Priority: Minor
> Fix For: 3.0.0
>
>
> The name of the created artifact (in the target folder) should always follow
> the convention. It shouldn't be configurable.
> As this is a breaking change it is appropriate for v3.0.0.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
