try maven-scm-plugin 1.5.1-SNAPSHOT still in svn.
svn co https://svn.apache.org/repos/asf/maven/maven-1/plugins/trunk
then goto trunk/scm and do maven install
-D
On 8/18/05, Sanjay Choudhary [EMAIL PROTECTED] wrote:
Hi Dan,
This makes perfect sense. Thanks for your help.
In one of your
Sanjay,
You might want to look at continuous integration engines like CruiseControl,
Anthill or Luntbuild, which take care of the tagging and are ideal for
nightly builds. Maven would then just be used for build and packaging. CVS
operations are handled by the build server. However, for
Hi Tom,
Is your plug-in public or private? If its public, whats the name of your
plug-in?
On 8/18/05, Thomas Van de Velde [EMAIL PROTECTED] wrote:
Sanjay,
You might want to look at continuous integration engines like
CruiseControl,
Anthill or Luntbuild, which take care of the tagging
Sanjay, beside from CI as Thomas suggested.
If your have a night build fail. You should increment the build
number and tag it again for the next build.
However even with simple cron job to do scm:update and build every
hour would reduce your chance of failed nightly build big time. It
works
Hi Dan,
thanks for your comments and I tried it but it fails
First Build
1. Bootstrap code for release 1.0.1
2. multiproject:prepare-release will Tag in CVS and project.xml gets updated
with version 1.0.1
3. maven goal-name
Second build
1. Bootstrap code.
2. mulitproject:prepare-release will
Sanjay, you and I have the same build requirements ( tag daily build)
but I dont use
multiproejct:prepare-release. This is the different.
In my case, I have a single version property defined at the root pom, and all
subproject's version and dependency's version, except the thirdpary
ones, reuse
Hi Dan,
This makes perfect sense. Thanks for your help.
In one of your steps you said tag the entire source source. How do you
tag it? Do you use ant rtag or someother mechanism?
Thanks,
Sanjay
On 8/18/05, dan tran [EMAIL PROTECTED] wrote:
Sanjay, you and I have the same build
