You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2017/08/13 20:01:00 UTC

[jira] [Commented] (MEAR-232) Remove param properties that doesn't make sense for CLI usage

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

Hudson commented on MEAR-232:
-----------------------------

SUCCESS: Integrated in Jenkins build maven-plugins #9067 (See [https://builds.apache.org/job/maven-plugins/9067/])
[MEAR-232] Remove param properties that doesn't make sense for CLI usage
 o Removed maven.ear.escapedBackslashesInFilePath,
   maven.ear.escapeString, maven.ear.skinnyWars, maven.ear.useJvmChmod.
 o Removed alias earName. (khmarbaise: [http://svn.apache.org/viewvc/?view=rev&rev=1804942])
* (edit) maven-ear-plugin/src/main/java/org/apache/maven/plugins/ear/EarMojo.java


> Remove param properties that doesn't make sense for CLI usage
> -------------------------------------------------------------
>
>                 Key: MEAR-232
>                 URL: https://issues.apache.org/jira/browse/MEAR-232
>             Project: Maven Ear Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.10.1
>         Environment: n/a
>            Reporter: Anders Hammar
>            Assignee: Karl Heinz Marbaise
>             Fix For: 3.0.0
>
>
> 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 message was sent by Atlassian JIRA
(v6.4.14#64029)