You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "David Barri (JIRA)" <ji...@codehaus.org> on 2008/08/01 07:37:26 UTC
[jira] Created: (MRELEASE-368) release:prepare doesn't recognise
deleted files
release:prepare doesn't recognise deleted files
-----------------------------------------------
Key: MRELEASE-368
URL: http://jira.codehaus.org/browse/MRELEASE-368
Project: Maven 2.x Release Plugin
Issue Type: Bug
Components: scm
Affects Versions: 2.0-beta-7
Environment: Windows XP, CVSNT 2.5.03 (build 2382), Maven 2.0.9
Reporter: David Barri
Priority: Critical
If I check a project out, delete a file and then run mvn release:prepare (using native cvs impl) then the following happens:
* In the first phase I see Unknown file status: 'R'.
* It then changes the version in the pom to the release version and commits it.
* However before tagging it checks again, see’s that a file is missing and aborts.
It should stop in the verify phase at the beginning.
--
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: (MRELEASE-368) release:prepare doesn't recognise
deleted files
Posted by "David Barri (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Barri updated MRELEASE-368:
---------------------------------
Attachment: MRELEASE-368 output.txt
mvn output
> release:prepare doesn't recognise deleted files
> -----------------------------------------------
>
> Key: MRELEASE-368
> URL: http://jira.codehaus.org/browse/MRELEASE-368
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: scm
> Affects Versions: 2.0-beta-7
> Environment: Windows XP, CVSNT 2.5.03 (build 2382), Maven 2.0.9
> Reporter: David Barri
> Priority: Critical
> Attachments: MRELEASE-368 output.txt
>
>
> If I check a project out, delete a file and then run mvn release:prepare (using native cvs impl) then the following happens:
> * In the first phase I see Unknown file status: 'R'.
> * It then changes the version in the pom to the release version and commits it.
> * However before tagging it checks again, see’s that a file is missing and aborts.
> It should stop in the verify phase at the beginning.
--
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] Commented: (MRELEASE-368) release:prepare doesn't recognise
deleted files
Posted by "Mark Struberg (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=271521#comment-271521 ]
Mark Struberg commented on MRELEASE-368:
----------------------------------------
this looks like a bug in maven-scm-provider-cvs. It uses cvs update instead of cvs status....
Could be a side effect of SCM-625
> release:prepare doesn't recognise deleted files
> -----------------------------------------------
>
> Key: MRELEASE-368
> URL: https://jira.codehaus.org/browse/MRELEASE-368
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: scm
> Affects Versions: 2.0-beta-7
> Environment: Windows XP, CVSNT 2.5.03 (build 2382), Maven 2.0.9
> Reporter: David Barri
> Priority: Critical
> Attachments: MRELEASE-368 output.txt
>
>
> If I check a project out, delete a file and then run mvn release:prepare (using native cvs impl) then the following happens:
> * In the first phase I see Unknown file status: 'R'.
> * It then changes the version in the pom to the release version and commits it.
> * However before tagging it checks again, see’s that a file is missing and aborts.
> It should stop in the verify phase at the beginning.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira