[
https://issues.apache.org/jira/browse/MASSEMBLY-845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16426841#comment-16426841
]
Robin Björklin commented on MASSEMBLY-845:
------------------------------------------
We have this problem as well. One of our projects is creating three artifacts
and not being able to set a name for each one of these has kept us on 2.6 for
years now. In 2.6 we just use the execution <id> as a name but since 3.0.0 also
the files now get named like this: <id>-<classifier>.jar and we have no control
over this. A fix would be much appreciated.
> MASSEMBLY-817 makes some usecases very inconvenient
> ---------------------------------------------------
>
> Key: MASSEMBLY-845
> URL: https://issues.apache.org/jira/browse/MASSEMBLY-845
> Project: Maven Assembly Plugin
> Issue Type: Bug
> Affects Versions: 3.0.0
> Reporter: Ulf Dreyer
> Priority: Major
>
> 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)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
