[
https://issues.apache.org/jira/browse/MJAR-233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15412520#comment-15412520
]
Matthew commented on MJAR-233:
------------------------------
Hmm. If you remove a feature it would be good to explain why! I spent a long
time trying to work out if it was broken!
In our use case we require jar files without version tags in the name for
continuous integration since version tags are nearly meaningless in this
context. I can envisage many other use cases.
How should we be solving this?
> What happened to finalName?!
> ----------------------------
>
> Key: MJAR-233
> URL: https://issues.apache.org/jira/browse/MJAR-233
> Project: Maven JAR Plugin
> Issue Type: Bug
> Affects Versions: 3.0.2
> Reporter: Matthew
> Assignee: Robert Scholte
>
> I've updated my maven-jar-plugin from 2.6 to 3.0.2 and it no longer supports
> the jar.finalName property. There's no mention of it in the documents either.
> There's some clue in the code that it's been renamed "maven.jar.finalName"
> but this doesn't seem to work for me (nor is it documented on the webpage).
> Am I missing something?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
