--Original Message-
> From: Alexandre Gomes [mailto:[EMAIL PROTECTED]
> 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 C
repare must be runned twice?
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
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 "SEA
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
pro
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
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
