[jira] [Closed] (MRELEASE-631) Use different file for non-interactive release configuration

["Michael Osipov (JIRA)" <ji...@apache.org>]

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

Michael Osipov closed MRELEASE-631.
-----------------------------------
    Resolution: Auto Closed

This issue has been auto closed because it has been inactive for a long period of time. If you think this issue still applies, retest your problem with the most recent version of Maven and the affected component, reopen and post your results.

> Use different file for non-interactive release configuration
> ------------------------------------------------------------
>
>                 Key: MRELEASE-631
>                 URL: https://issues.apache.org/jira/browse/MRELEASE-631
>             Project: Maven Release Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.1
>            Reporter: Arno Wolter
>            Priority: Minor
>
> It would be nice to use a configurable file for non-interactive release configuration instead of release.properties.
> One could commit that file with the sources in order to configure the upcoming release within his IDE. You cannot do that with the release.properties as is it modified by the release plugin and therefore prevents tagging. As a consequence you could just press a "release" button in your CI-server without touching any build plan configuration.
> Of course that makes only sense if release role and dev role are owned by the same person



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)