Hi
release.properties and pom.xml.releaseBackup should not be under version
control. They are only temporary files.
Cheers, michael
Alexandre Gomes wrote:
Hi everybody. Is that a must to run release:prepare twice to have a
release prepared under CVS? Look the sequence below. With CVS, the
problem in step 5 always happens but not in SVN. Well, I think
release:prepare always changes the release.properties file. So, why
isn't the plugin smart enough to know it and just commit by itself,
without the error?
1) First, I commit everything: "cvs commit"
2) Then, I run "mvn release:clean"
3) Run "mvn release:prepare"
4) Inform release version, release tag and next development version:
(...)
[INFO] Checking dependencies and plugins for snapshots ...
What is the release version for "SEAUP"? (br.com.seatecnologia:seaup) 2.0.18: :
What is SCM release tag or label for "SEAUP"?
(br.com.seatecnologia:seaup) seaup-2_0_18: :
What is the new development version for "SEAUP"?
(br.com.seatecnologia:seaup) 2.0.19-SNAPSHOT: :
[INFO] Transforming 'SEAUP'...
(...)
5) Then, I get an error:
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Unable to tag SCM
Provider message:
The cvs tag command failed.
Command output:
cvs tag: release.properties is locally modified
cvs [tag aborted]: correct the above errors first!
6) I re-commit everything "cvs commit" (release.properties is commited)
7) I re-run "mvn release:prepare"
8) Now, the release is prepared.
thanks,
Alexandre
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Michael Meyer | [EMAIL PROTECTED]
phone +41-44-247 79 12 | fax +41-44-247 70 75
Netcetera AG | 8040 Zürich | Switzerland | http://netcetera.ch
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
