[
https://issues.apache.org/jira/browse/MASSEMBLY-817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15820479#comment-15820479
]
Ulf Dreyer commented on MASSEMBLY-817:
--------------------------------------
The "improvement" done in MASSEMBLY-817 makes some usecases very inconvenient:
We need to create an archive with one stable name (independent of e.g. version)
so we don't have to propagate these information to a bunch of scripts.
The general solution (i.e. Stack-overflow) refers exactly to the finalName:
[http://stackoverflow.com/questions/20697144/can-not-set-the-final-jar-name-with-maven-assembly-plugin]
*Please change finalName back to a settable property.*
It being settable does not hurt anyone satisfied with the default naming
convention but makes some usecases vastly simpler (otherwise you have to rename
the artifact using yet another plugin or propagate version info possibly
through a chain of scripts)
(I would have created an issue but jira gives me "Error creating issue:
Indexing completed with 2 errors" )
> 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)
