[ 
http://jira.codehaus.org/browse/MRELEASE-469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=249769#action_249769
 ] 

Arno Wolter commented on MRELEASE-469:
--------------------------------------

I just wanted to comment on this, because I ran into similar "problem". Simply 
put, I forgot to add the "-B" switch to enable non-interactive mode when 
running release:prepare in Bamboo. The build will hang then at the same spot 
with just the line "Checking dependencies and plugins for snapshots ..."

> Plugin hangs in preparation while checking deps and plugins for snapshots
> -------------------------------------------------------------------------
>
>                 Key: MRELEASE-469
>                 URL: http://jira.codehaus.org/browse/MRELEASE-469
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>          Components: prepare
>    Affects Versions: 2.0-beta-8, 2.0-beta-9
>         Environment: Gentoo Linux, Sun JDK 1.5, 32-bit
>            Reporter: Joerg Schaible
>            Priority: Blocker
>         Attachments: pom.xml
>
>
> 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):
> {noformat}
> $ 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] 
> ------------------------------------------------------------------------
> {noformat}
> 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.

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

        

Reply via email to