You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Carlos Sanchez (JIRA)" <ji...@codehaus.org> on 2006/12/06 05:18:41 UTC
[jira] Updated: (CONTINUUM-1030) Build for official release leaves
a dirty working copy
[ http://jira.codehaus.org/browse/CONTINUUM-1030?page=all ]
Carlos Sanchez updated CONTINUUM-1030:
--------------------------------------
Priority: Critical (was: Major)
Fix Version/s: 1.1
> Build for official release leaves a dirty working copy
> ------------------------------------------------------
>
> 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"
> 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
--
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