mvn release:prepare will not tag in subversion repository
---------------------------------------------------------
Key: MPRELEASE-22
URL: http://jira.codehaus.org/browse/MPRELEASE-22
Project: maven-release-plugin
Issue Type: Bug
Environment: linux ubuntu
Reporter: Andrew
Priority: Minor
The release plugin won't tag a version in subversion after performing
release:prepare -DdryRun=true.
We are currently using a Subversion 1.4 client and repository server.
Steps to reproduce :-
mvn release:prepare -DdryRun=true
mvn release:prepare (I assume should tag at this point)
No tag is created in repository.
If however the following :- mvn release:prepare -Dresume=false is run after
the release:prepare the tag will be created as expected.
The output from the mvn release:prepare was interesting, it appears that the
release:prepare -DdryRun=true has already performed the release preparation
even though its a dry run.
[EMAIL PROTECTED]:~/development/persistence-r1$ mvn release:prepare
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'release'.
[INFO]
----------------------------------------------------------------------------
[INFO] Building Persistence library
[INFO] task-segment: [release:prepare] (aggregator-style)
[INFO]
----------------------------------------------------------------------------
[INFO] [release:prepare]
[INFO] Release preparation already completed. You can now continue with
release:perform, or start again using the -Dresume=false flag
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 4 seconds
[INFO] Finished at: Thu Nov 09 09:08:23 EST 2006
[INFO] Final Memory: 5M/10M
[INFO] ------------------------------------------------------------------------
My guess is that the release:prepare -DdryRun=true
shouldn't write completedPhase=end-release to release.properties ?
--
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
