[
https://issues.apache.org/jira/browse/MJAR-210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15224801#comment-15224801
]
Anders Hammar commented on MJAR-210:
------------------------------------
Just an idea, should we keep params that we want to remove but mark them as
deprecated and have them issue an exception with a good error message? To
simplify for people upgrading and catch these breaking changes.
> Remove useDefaultManifestFile parameter
> ---------------------------------------
>
> Key: MJAR-210
> URL: https://issues.apache.org/jira/browse/MJAR-210
> Project: Maven JAR Plugin
> Issue Type: Improvement
> Affects Versions: 3.0.0
> Reporter: Karl Heinz Marbaise
> Assignee: Karl Heinz Marbaise
> Fix For: 3.0.0
>
>
> The following:
> {code}
> @Parameter( property = "maven.jar.useDefaultManifestFile", defaultValue =
> "false" )
> private boolean useDefaultManifestFile;
> {code}
> does not make sense in general, cause it can be handled via
> [MavenArchiver|http://maven.apache.org/shared/maven-archiver/index.html]
> configuration. So this should be completely removed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)