[jira] Updated: (CONTINUUM-1030) Build for official release leaves a dirty working copy if it fails

2007-01-09 Thread Edwin Punzalan (JIRA)
 [ http://jira.codehaus.org/browse/CONTINUUM-1030?page=all ]

Edwin Punzalan updated CONTINUUM-1030:
--

Attachment: CONTINUUM-1030-continuum.patch

Attached a patch to allow a rollback after a release.

> Build for official release leaves a dirty working copy if it fails
> --
>
> Key: CONTINUUM-1030
> URL: http://jira.codehaus.org/browse/CONTINUUM-1030
> Project: Continuum
>  Issue Type: Bug
>  Components: Core system
>Affects Versions: 1.1
>Reporter: Carlos Sanchez
> Assigned To: Edwin Punzalan
>Priority: Critical
> Fix For: 1.1
>
> Attachments: CONTINUUM-1030-continuum.patch
>
>
> if release breaks after modyfing the pom the working copy is left dirty, with 
> a modified pom and you can't release again, it complains with "pom is not 
> snapshot"

-- 
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




[jira] Updated: (CONTINUUM-1030) Build for official release leaves a dirty working copy if it fails

2006-12-13 Thread Carlos Sanchez (JIRA)
 [ http://jira.codehaus.org/browse/CONTINUUM-1030?page=all ]

Carlos Sanchez updated CONTINUUM-1030:
--

Description: if release breaks after modyfing the pom the working copy is 
left dirty, with a modified pom and you can't release again, it complains with 
"pom is not snapshot"  (was: if release breaks after modyfing the pom the 
working copy is left dirty, with a modified pom and you can't release again, it 
complains with "pom is not snapshot"

Anyway although it succeeds it's gonna leave the pom modifed in the working 
copy, so if I check the build history I will have a working copy that doesn't 
match whatever was built)
Summary: Build for official release leaves a dirty working copy if it 
fails  (was: Build for official release leaves a dirty working copy)

> Build for official release leaves a dirty working copy if it fails
> --
>
> Key: CONTINUUM-1030
> URL: http://jira.codehaus.org/browse/CONTINUUM-1030
> Project: Continuum
>  Issue Type: Bug
>  Components: Core system
>Affects Versions: 1.1
>Reporter: Carlos Sanchez
>Priority: Critical
> Fix For: 1.1
>
>
> if release breaks after modyfing the pom the working copy is left dirty, with 
> a modified pom and you can't release again, it complains with "pom is not 
> snapshot"

-- 
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