[jira] [Reopened] (MRELEASE-282) Replace the current 'arguments' parameter with specialized version for each mojo (eg. 'argumentsRelease')

["Slawomir Jaranowski (Jira)" <ji...@apache.org>]

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

Slawomir Jaranowski reopened MRELEASE-282:
------------------------------------------

Existing {{arguments}} should be preserved and used as default.
We can add new specific options for each goal like {{argumentsPrepare}} and {{argumentsRelease}} - new parameter should override old one if are set.

> Replace the current 'arguments' parameter with specialized version for each mojo (eg. 'argumentsRelease')
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: MRELEASE-282
>                 URL: https://issues.apache.org/jira/browse/MRELEASE-282
>             Project: Maven Release Plugin
>          Issue Type: Improvement
>          Components: prepare
>    Affects Versions: 2.0-beta-6
>         Environment: mvn 2.0.7
> WinXP
>            Reporter: Marcel Schutte
>            Priority: Major
>
> There is currently no way to configure the release:prepare and release:perform mojos with different values for the 'arguments' parameter. Brett said the solution should be to use unique names for the parameters [1] [2].
> I am aware that it is possible to use profiles for this. However, I want to declare the default behavior in my pom, not leave it to the user to provide the correct profile.
> There is a workaround available [3], however, this means you have to duplicate the default values for <goals> and <preparationGoals) in your plugin configuration.
> Some context for this improvement request is [4]
> [1] http://jira.codehaus.org/browse/MNG-1446
> [2] http://jira.codehaus.org/browse/MCOMPILER-15
> [3] http://jira.codehaus.org/browse/MRELEASE-59
> [4] http://www.nabble.com/release-plugin-configuration-tf4377660s177.html



--
This message was sent by Atlassian Jira
(v8.20.7#820007)