You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Alexandre Gomes <al...@gmail.com> on 2007/08/21 13:53:46 UTC
release:prepare must be runned twice?
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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: release:prepare must be runned twice?
Posted by houzecl <ch...@etat.ge.ch>.
I take advantage of your post to ask a question about the release prompts:
(...)
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: :
(...)
the plugin batch mode will avoid the prompts but will use default values
In your case the tag would be: seaup-2.0.18
which is not acceptable for cvs (tha's why you specify seaup-2_0_18)
Is there any way to specify the default values somewhere in plugin
configuration ?
Thanks,
Christian-Luc
(cf also my thread: Maven Release Plugin - parameters: release version,
release tag, new development version)
--
View this message in context: http://www.nabble.com/release%3Aprepare-must-be-runned-twice--tf4304706s177.html#a12253817
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: release:prepare must be runned twice?
Posted by Michael Meyer <mi...@netcetera.ch>.
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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
--
Michael Meyer | michael.meyer@netcetera.ch
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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: release:prepare must be runned twice?
Posted by Alexandre Gomes <al...@gmail.com>.
Ok. Thanks everybody. Now, I have two mor infos:
1) The guy responsible for release:prepare is not the same for
release:perform. That's why I use to add those temp files to SCM.
2) The problem I mentioned before happens in my Mac OS X, but not in
Ubuntu. A bug, maybe?
thanks.
On 8/21/07, nick_stolwijk@planet.nl <ni...@planet.nl> wrote:
> Why would you check in release.properties? AFAIK, it is a more common use case to let your SCM ignore the release.properties. I guess your release:prepare would run smooth.
>
> Hth,
>
> Nick Stolwijk
>
>
> -----Original Message-----
> From: Alexandre Gomes [mailto:alegomes@gmail.com]
> Sent: Tue 8/21/2007 1:53 PM
> To: users@maven.apache.org
> Subject: release:prepare must be runned twice?
>
> 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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: release:prepare must be runned twice?
Posted by ni...@planet.nl.
Why would you check in release.properties? AFAIK, it is a more common use case to let your SCM ignore the release.properties. I guess your release:prepare would run smooth.
Hth,
Nick Stolwijk
-----Original Message-----
From: Alexandre Gomes [mailto:alegomes@gmail.com]
Sent: Tue 8/21/2007 1:53 PM
To: users@maven.apache.org
Subject: release:prepare must be runned twice?
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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org