[MASSEMBLY-845] MASSEMBLY-817 makes some usecases very inconvenient

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 3.0.0
• Assignee: Unassigned
• Reporter: Ulf Dreyer
• Created: 12/Jan/17 08:29
• Updated: 25/Apr/23 16:25
• Resolved: 25/Apr/23 16:25

Description

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)

Issue Links

• duplicates: MASSEMBLY-843 finalName as readonly parameter makes common usecases very complicated
• is related to: MASSEMBLY-817 Make finalName readonly parameter
• relates to: MJAR-233 What happened to finalName?!