[
https://issues.apache.org/jira/browse/MASSEMBLY-817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15843063#comment-15843063
]
Stephen Colebourne edited comment on MASSEMBLY-817 at 1/27/17 5:35 PM:
-----------------------------------------------------------------------
This has just bitten me too. This is a very annoying and nasty change. Changing
the finalName of the whole project is very definitely not what is wanted, as it
does not allow a project to produce multiple distributions via the assembly
plugin, each with distinct names, or to produce jar files with a different zip
file name. Please reconsider this, as it was a widely used feature and will be
painful for many users that want to produce output zip files (ie. it will break
a lot of builds).
Could the name be settable when attach=false. That would be a step forward,
although restoring the full feature would be better.
was (Author: scolebourne):
This has just bitten me too. This is a very annoying and nasty change. Changing
the finalName of the whole project is very definitely not what is wanted, as it
does not allow a project to produce multiple distributions via the assembly
plugin, each with distinct names, or to produce jar files with a different zip
file name. Please reconsider this, as it was a widely used feature and will be
painful for many users that want to produce output zip files (ie. it will break
a lot of builds).
> 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)
