You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Patrick Schneider (JIRA)" <ji...@codehaus.org> on 2007/05/19 00:43:59 UTC
[jira] Commented: (MRELEASE-227) release:rollback fails when using
Perforce
[ http://jira.codehaus.org/browse/MRELEASE-227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_96327 ]
Patrick Schneider commented on MRELEASE-227:
--------------------------------------------
Works great Emmanuel -- thanks!
> release:rollback fails when using Perforce
> ------------------------------------------
>
> Key: MRELEASE-227
> URL: http://jira.codehaus.org/browse/MRELEASE-227
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.0-beta-5
> Environment: Maven 2.0.6
> Reporter: Patrick Schneider
> Assignee: Emmanuel Venisse
> Priority: Minor
> Fix For: 2.0-beta-6
>
>
> The Perforce provider requires edit mode when changing files that are under source control. After a successful release:prepare, the release:rollback goal fails. It looks like RestoreBackupPomsPhase tries a FileUtils.copyFile, disregarding whether the SCM requires this or not -- it then fails b/c the POM is readonly at this point.
--
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