[MWAR-376] Remove param properties that doesn't make sense for CLI usage

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.6
• Fix Version/s: 3.0.0
• Environment: n/a
• Assignee: Karl Heinz Marbaise
• Reporter: Anders Hammar
• Created: 24/Apr/16 14:15
• Updated: 16/May/16 18:16
• Resolved: 16/May/16 17:57

Description

Currently the plugin supports configuring several of the parameters via CLI properties. This doesn't make sense in many cases and encourages bad Maven usage (builds should be reproducible). Remove the properties for those parameters. The v3.0.0 release is a good time to do this.

First of all we need to identify candidates for removal.

This is the list of parameters/properties maven-war-plugin contains at the moment:

@Parameter( property = "archiveClasses", defaultValue = "false" )
 @Parameter( property = "resourceEncoding", defaultValue = "${project.build.sourceEncoding}" )
 @Parameter( property = "maven.war.webxml" )
 @Parameter( property = "maven.war.containerConfigXML" )
 @Parameter( property = "useCache", defaultValue = "false" )
 @Parameter( property = "maven.war.filteringDeploymentDescriptors", defaultValue = "false" )
 @Parameter( property = "maven.war.escapedBackslashesInFilePath", defaultValue = "false" )
 @Parameter( property = "maven.war.escapeString" )
 @Parameter( property = "maven.war.supportMultiLineFiltering", defaultValue = "false" )
 @Parameter( property = "maven.war.useJvmChmod", defaultValue = "true" )
 @Parameter( property = "primaryArtifact", defaultValue = "true" )
 @Parameter( property = "failOnMissingWebXml", defaultValue = "true" )
 @Parameter( property = "maven.war.skip", defaultValue = "false" )

Issue Links

• is duplicated by: MWAR-377 Remove param properties that doesn't make sense for CLI usage