You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Anders Hammar (JIRA)" <ji...@apache.org> on 2016/04/18 10:50:25 UTC

[jira] [Comment Edited] (MJAR-209) Remove param properties that doesn't make sense for CLI usage

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

Anders Hammar edited comment on MJAR-209 at 4/18/16 8:49 AM:
-------------------------------------------------------------

The only params I think make sense to be able to configure from CLI are forceCreation and skip (only found in test-jar). The rest shouldn't have user property.



was (Author: afloom):
The only params I think make sense to be able to configure from CLI are forceCreation and skip. The rest shouldn't have user property.
(Please note that I looked at the on-line docs for v2.6, so if there is any param added after that I haven't taken that into account.)


> Remove param properties that doesn't make sense for CLI usage
> -------------------------------------------------------------
>
>                 Key: MJAR-209
>                 URL: https://issues.apache.org/jira/browse/MJAR-209
>             Project: Maven JAR Plugin
>          Issue Type: Improvement
>         Environment: n/a
>            Reporter: Anders Hammar
>
> 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 reproducable). 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.3.4#6332)