In searching the net I know this has come up before, but the explanations
I've found so far don't seem to match my stituation exactly (e.g. older
version of the plugin).
I'm using a simple test project to learn how the release plugin works. It's
checked into CVS, and we use private-public key pairs to access CVS. When I
run:
mvn -X release:prepare -DdryRun=true
the last few lines of the output are roughly:
[INFO] [release:prepare {execution: default-cli}]
[DEBUG] release.properties not found - using empty properties
[INFO] Verifying that there are no local modifications...
[INFO] Executing: /bin/sh -c cd /work/mdb/lib/m2test && cvs -z3 -f -d
:ext:jfre...@server:/cvs -n -q update -d
[INFO] Working directory: /work/mdb/lib/m2test
[DEBUG] Executing CVS command: update -d
where it just hangs.
I can run 'cvs update -d' from the command line. My <scm> section looks
like:
<scm>
<connection>
scm:cvs:ext:jfre...@server:/cvs:mdb/lib/m2test
</connection>
<developerConnection>
scm:cvs:ext:jfre...@server:/cvs:mdb/lib/m2test
</developerConnection>
<tag>HEAD</tag>
</scm>
I've tried both versions 2.0-beta-8 and 2.0-beta-9 of the release plugin.
Any ideas what I might be doing wrong? Thanks for any help.
Jeff
--
View this message in context:
http://old.nabble.com/Hanging-on-release%3Aprepare-tp26660984p26660984.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
