You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Graham Leggett (JIRA)" <ji...@codehaus.org> on 2007/08/23 11:43:47 UTC
[jira] Created: (MRELEASE-278) release:clean doesn't clean up after
release:branch
release:clean doesn't clean up after release:branch
---------------------------------------------------
Key: MRELEASE-278
URL: http://jira.codehaus.org/browse/MRELEASE-278
Project: Maven 2.x Release Plugin
Issue Type: Bug
Affects Versions: 2.0-beta-6
Environment: java version "1.5.0_11"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03)
Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_11-b03, mixed mode)
Reporter: Graham Leggett
When using release:branch -DdryRun=true to test a branch, some extra files are left lying around like below. These cause release:branch to fail because of unchecked-in modifications.
release:clean needs to be taught how to clean up after these files.
bash-3.00$ svn status
? pom.xml.releaseBackup
? pom.xml.branch
? alchemy-cdo-client/pom.xml.releaseBackup
? alchemy-cdo-client/pom.xml.branch
? alchemy-transformer/pom.xml.releaseBackup
? alchemy-transformer/pom.xml.branch
? alchemy-native-assembly/pom.xml.releaseBackup
? alchemy-native-assembly/pom.xml.branch
? alchemy-cdo/pom.xml.releaseBackup
? alchemy-cdo/pom.xml.branch
--
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-278) release:clean doesn't clean up after
release:branch
Posted by "Paul Gier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Gier updated MRELEASE-278:
-------------------------------
Assignee: Paul Gier
Fix Version/s: 2.0-beta-10
> release:clean doesn't clean up after release:branch
> ---------------------------------------------------
>
> Key: MRELEASE-278
> URL: http://jira.codehaus.org/browse/MRELEASE-278
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: branch, clean
> Affects Versions: 2.0-beta-6
> Environment: java version "1.5.0_11"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03)
> Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_11-b03, mixed mode)
> Reporter: Graham Leggett
> Assignee: Paul Gier
> Fix For: 2.0-beta-10
>
> Attachments: MRELEASE-278.diff
>
>
> When using release:branch -DdryRun=true to test a branch, some extra files are left lying around like below. These cause release:branch to fail because of unchecked-in modifications.
> release:clean needs to be taught how to clean up after these files.
> bash-3.00$ svn status
> ? pom.xml.releaseBackup
> ? pom.xml.branch
> ? alchemy-cdo-client/pom.xml.releaseBackup
> ? alchemy-cdo-client/pom.xml.branch
> ? alchemy-transformer/pom.xml.releaseBackup
> ? alchemy-transformer/pom.xml.branch
> ? alchemy-native-assembly/pom.xml.releaseBackup
> ? alchemy-native-assembly/pom.xml.branch
> ? alchemy-cdo/pom.xml.releaseBackup
> ? alchemy-cdo/pom.xml.branch
--
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-278) release:clean doesn't clean up after
release:branch
Posted by "David Jencks (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Jencks updated MRELEASE-278:
----------------------------------
Attachment: MRELEASE-278.diff
Fixes the problem by including all the branch phases in the list of phase objects to run clean on. Note that this includes updates to the test config so there is a list of branch phases and also includes a test that checks that the branch phase clean is in fact called.
To repeat, this includes a test.
> release:clean doesn't clean up after release:branch
> ---------------------------------------------------
>
> Key: MRELEASE-278
> URL: http://jira.codehaus.org/browse/MRELEASE-278
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: branch, clean
> Affects Versions: 2.0-beta-6
> Environment: java version "1.5.0_11"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03)
> Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_11-b03, mixed mode)
> Reporter: Graham Leggett
> Attachments: MRELEASE-278.diff
>
>
> When using release:branch -DdryRun=true to test a branch, some extra files are left lying around like below. These cause release:branch to fail because of unchecked-in modifications.
> release:clean needs to be taught how to clean up after these files.
> bash-3.00$ svn status
> ? pom.xml.releaseBackup
> ? pom.xml.branch
> ? alchemy-cdo-client/pom.xml.releaseBackup
> ? alchemy-cdo-client/pom.xml.branch
> ? alchemy-transformer/pom.xml.releaseBackup
> ? alchemy-transformer/pom.xml.branch
> ? alchemy-native-assembly/pom.xml.releaseBackup
> ? alchemy-native-assembly/pom.xml.branch
> ? alchemy-cdo/pom.xml.releaseBackup
> ? alchemy-cdo/pom.xml.branch
--
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-278) release:clean doesn't clean up after
release:branch
Posted by "Arnaud Heritier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arnaud Heritier updated MRELEASE-278:
-------------------------------------
Component/s: clean
> release:clean doesn't clean up after release:branch
> ---------------------------------------------------
>
> Key: MRELEASE-278
> URL: http://jira.codehaus.org/browse/MRELEASE-278
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: branch, clean
> Affects Versions: 2.0-beta-6
> Environment: java version "1.5.0_11"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03)
> Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_11-b03, mixed mode)
> Reporter: Graham Leggett
>
> When using release:branch -DdryRun=true to test a branch, some extra files are left lying around like below. These cause release:branch to fail because of unchecked-in modifications.
> release:clean needs to be taught how to clean up after these files.
> bash-3.00$ svn status
> ? pom.xml.releaseBackup
> ? pom.xml.branch
> ? alchemy-cdo-client/pom.xml.releaseBackup
> ? alchemy-cdo-client/pom.xml.branch
> ? alchemy-transformer/pom.xml.releaseBackup
> ? alchemy-transformer/pom.xml.branch
> ? alchemy-native-assembly/pom.xml.releaseBackup
> ? alchemy-native-assembly/pom.xml.branch
> ? alchemy-cdo/pom.xml.releaseBackup
> ? alchemy-cdo/pom.xml.branch
--
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-278) release:clean doesn't clean up after
release:branch
Posted by "Arnaud Heritier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arnaud Heritier updated MRELEASE-278:
-------------------------------------
Component/s: branch
> release:clean doesn't clean up after release:branch
> ---------------------------------------------------
>
> Key: MRELEASE-278
> URL: http://jira.codehaus.org/browse/MRELEASE-278
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: branch
> Affects Versions: 2.0-beta-6
> Environment: java version "1.5.0_11"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03)
> Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_11-b03, mixed mode)
> Reporter: Graham Leggett
>
> When using release:branch -DdryRun=true to test a branch, some extra files are left lying around like below. These cause release:branch to fail because of unchecked-in modifications.
> release:clean needs to be taught how to clean up after these files.
> bash-3.00$ svn status
> ? pom.xml.releaseBackup
> ? pom.xml.branch
> ? alchemy-cdo-client/pom.xml.releaseBackup
> ? alchemy-cdo-client/pom.xml.branch
> ? alchemy-transformer/pom.xml.releaseBackup
> ? alchemy-transformer/pom.xml.branch
> ? alchemy-native-assembly/pom.xml.releaseBackup
> ? alchemy-native-assembly/pom.xml.branch
> ? alchemy-cdo/pom.xml.releaseBackup
> ? alchemy-cdo/pom.xml.branch
--
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] Closed: (MRELEASE-278) release:clean doesn't clean up after
release:branch
Posted by "Paul Gier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Gier closed MRELEASE-278.
------------------------------
Resolution: Fixed
Patch applied in [r805455|http://svn.apache.org/viewvc?view=rev&revision=805455]. Thanks!
> release:clean doesn't clean up after release:branch
> ---------------------------------------------------
>
> Key: MRELEASE-278
> URL: http://jira.codehaus.org/browse/MRELEASE-278
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: branch, clean
> Affects Versions: 2.0-beta-6
> Environment: java version "1.5.0_11"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03)
> Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_11-b03, mixed mode)
> Reporter: Graham Leggett
> Assignee: Paul Gier
> Fix For: 2.0-beta-10
>
> Attachments: MRELEASE-278.diff
>
>
> When using release:branch -DdryRun=true to test a branch, some extra files are left lying around like below. These cause release:branch to fail because of unchecked-in modifications.
> release:clean needs to be taught how to clean up after these files.
> bash-3.00$ svn status
> ? pom.xml.releaseBackup
> ? pom.xml.branch
> ? alchemy-cdo-client/pom.xml.releaseBackup
> ? alchemy-cdo-client/pom.xml.branch
> ? alchemy-transformer/pom.xml.releaseBackup
> ? alchemy-transformer/pom.xml.branch
> ? alchemy-native-assembly/pom.xml.releaseBackup
> ? alchemy-native-assembly/pom.xml.branch
> ? alchemy-cdo/pom.xml.releaseBackup
> ? alchemy-cdo/pom.xml.branch
--
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