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

Hudson commented on MJAR-210:
-----------------------------

UNSTABLE: Integrated in maven-plugins #5587 (See 
[https://builds.apache.org/job/maven-plugins/5587/])
[MJAR-210] Remove useDefaultManifestFile parameter
 o Removed the parameter useDefaultManifestFile, 
   defaultManifestFile and removed the docs about that.
   Everything can be handled by MavenArchiveConfiguration. (khmarbaise: 
[http://svn.apache.org/viewvc/?view=rev&rev=1737724])
* maven-jar-plugin/src/it/mjar-71-01/pom.xml
* 
maven-jar-plugin/src/main/java/org/apache/maven/plugins/jar/AbstractJarMojo.java
* maven-jar-plugin/src/site/apt/examples/default-manifest-file.apt.vm
* maven-jar-plugin/src/site/apt/examples/manifest-customization.apt.vm
* maven-jar-plugin/src/site/apt/index.apt.vm
* maven-jar-plugin/src/site/site.xml


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

Reply via email to