You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Lars Corneliussen (JIRA)" <ji...@codehaus.org> on 2010/05/05 17:00:12 UTC
[jira] Updated: (MRELEASE-425) When running release:branch in
-DdryRun mode, the resulting pom.xml.branch is seen as an unknown file the
next time a release is run
[ http://jira.codehaus.org/browse/MRELEASE-425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Corneliussen updated MRELEASE-425:
---------------------------------------
Attachment: MRELEASE-425.patch
Also ignores pom.xml.branch when checking for local modifications
> When running release:branch in -DdryRun mode, the resulting pom.xml.branch is seen as an unknown file the next time a release is run
> ------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MRELEASE-425
> URL: http://jira.codehaus.org/browse/MRELEASE-425
> Project: Maven 2.x Release Plugin
> Issue Type: Wish
> Components: branch
> Affects Versions: 2.0-beta-8
> Reporter: Eric
> Assignee: Olivier Lamy
> Priority: Minor
> Attachments: MRELEASE-425.patch
>
>
> If you try to run the release:branch goal with -DdryRun, it runs fine. However, the next time you try to run release:clean or any other goal, the plugin fails that pom.xml.branch is unknown.
> I would have expected the plugin to ignore this file's CVS status, similarly to the pom.xml.releaseBackup or pom.xml.tag or release.properties files when a release:prepare is run with -DdryRun
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira