You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Stephen Connolly (JIRA)" <ji...@codehaus.org> on 2011/07/04 23:10:42 UTC

[jira] Commented: (MRELEASE-166) release:prepare should always check for local modifications

    [ https://jira.codehaus.org/browse/MRELEASE-166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=272289#comment-272289 ] 

Stephen Connolly commented on MRELEASE-166:
-------------------------------------------

Note that this should not always check for modifications, just check for modifications at points where it is not expecting them... such as just after committing the changes it has made

> release:prepare should always check for local modifications
> -----------------------------------------------------------
>
>                 Key: MRELEASE-166
>                 URL: https://jira.codehaus.org/browse/MRELEASE-166
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>          Components: prepare
>    Affects Versions: 2.0-beta-4
>            Reporter: Joerg Schaible
>            Priority: Critical
>             Fix For: 2.3
>
>
> If the first call to release:prepare fails, it does not check again for local modifications. This is quite likely though, since the release manager might have cleared the erroneous condition. If he forgets to check, the labe is set to the wrong version of the files and release:perform fails.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira