maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Heinz Marbaise (JIRA)" <j...@apache.org>
Subject [jira] [Issue Comment Deleted] (MJAR-209) Remove param properties that doesn't make sense for CLI usage
Date Wed, 30 Mar 2016 15:40:25 GMT

     [ https://issues.apache.org/jira/browse/MJAR-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Karl Heinz Marbaise updated MJAR-209:
-------------------------------------
    Comment: was deleted

(was: 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 MavehArchiver configuration. So
this should be completely removed.)

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

Mime
View raw message