maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrick Schneider (JIRA)" <j...@codehaus.org>
Subject [jira] Updated: (MRELEASE-227) release:rollback fails when using Perforce
Date Fri, 18 May 2007 22:09:59 GMT

     [ http://jira.codehaus.org/browse/MRELEASE-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Patrick Schneider updated MRELEASE-227:
---------------------------------------

    Description: 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.  (was: The Perforce
provider requires edit mode when changing files that are under source control.  After a successful
release:prepare, the release:perform 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.)
        Summary: release:rollback fails when using Perforce  (was: release:perform fails when
using Perforce)

Corrected the title and description.

> 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

        

Mime
View raw message