Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Blocker
-
Resolution: Not A Bug
-
Affects Version/s: 2.0-beta-8, 2.0-beta-9
-
Fix Version/s: None
-
Component/s: prepare
-
Labels:None
-
Environment:Gentoo Linux, Sun JDK 1.5, 32-bit
-
Number of attachments :
Description
The release plugin completely hangs when checking in "release:prepare" the dependencies and plugins for snapshot versions and I will have to kill it (^C after some minutes):
$ mvn release:prepare -Dtag=v_0.0.1
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Building Scalaris QMB Plugin
[INFO] task-segment: [release:prepare] (aggregator-style)
[INFO] ------------------------------------------------------------------------
[INFO] [release:prepare {execution: default-cli}]
[INFO] Verifying that there are no local modifications...
[INFO] Executing: /bin/sh -c cd /home/jos/work/research/qmb-plugin-webdev && svn --non-interactive status
[INFO] Working directory: /home/jos/work/research/qmb-plugin-webdev
[INFO] Checking dependencies and plugins for snapshots ...
^C
$ mvn release:rollback
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Building Scalaris QMB Plugin
[INFO] task-segment: [release:rollback] (aggregator-style)
[INFO] ------------------------------------------------------------------------
[INFO] [release:rollback {execution: default-cli}]
[INFO] Checking in modified POMs...
[INFO] Executing: /bin/sh -c cd /home/jos/work/research/qmb-plugin-webdev && svn --non-interactive commit --file /tmp/maven-scm-322645963.commit --targets /tmp/maven-scm-8571115898032334692-targets
[INFO] Working directory: /home/jos/work/research/qmb-plugin-webdev
[INFO] Cleaning up after release...
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 3 seconds
[INFO] Finished at: Tue Aug 04 12:57:00 CEST 2009
[INFO] Final Memory: 9M/56M
[INFO] ------------------------------------------------------------------------
I tried this with M221-rc2, M221-rc1, M220, M210, M2010 and M209. To simplify things I've replaced the original POM with a stripped-down effective-pom (without parent), so everything is contained in the attached single POM file that still behaves so weird. All you have to do is to adjust the SCM URLs to some valid location.
Note, that this project has been released before without problems (it's a plugin), just the dependencies have been updated from M209 to M210 artifacts.
Stupid me! I forgot that I colorized my Maven output last week (piping the output of Maven through sed and add some ANSI color escape codes)! While this is normally really helpful for large builds, it does not work at all for interactive plugin communication. Sorry for the noise.