[ 
https://issues.apache.org/jira/browse/MASSEMBLY-845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16052801#comment-16052801
 ] 

Karl Heinz Marbaise commented on MASSEMBLY-845:
-----------------------------------------------

It is not prevented to use:
{code:xml}
<build>
  <finalName>ToWhatEverYouLike</finalName>
 ...
</build>
{code}
This only changes the name of the resulting artifact in the target folder 
nothing more...
To be honest I don't see a real issue here? 


> 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
>
> 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)

Reply via email to