[jira] [Assigned] (MASSEMBLY-843) finalName as readonly parameter makes common usecases very complicated

["Karl Heinz Marbaise (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MASSEMBLY-843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Karl Heinz Marbaise reassigned MASSEMBLY-843:
---------------------------------------------

    Assignee: Karl Heinz Marbaise

> finalName as readonly parameter makes common usecases very complicated
> ----------------------------------------------------------------------
>
>                 Key: MASSEMBLY-843
>                 URL: https://issues.apache.org/jira/browse/MASSEMBLY-843
>             Project: Maven Assembly Plugin
>          Issue Type: Bug
>    Affects Versions: 3.0.0
>            Reporter: Ulf Dreyer
>            Assignee: Karl Heinz Marbaise
>
> 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
(v6.4.14#64029)