Alex,
When you do a release:prepare you always end up with a
tag in SVN. You use that for testing, then if QA
validates it, you can use the same tag to build it
again for production. The command is:
mvn release:perform
-DconnectionUrl=scm:svn:${your_svn_tag_url}
This will always build it from the same code you made
the QA build and you can run it as many times you
want, as long the ${your_svn_tag_url} is a valid url.
Now, if QA found issues and you need to do a build out
of it, it will be your responsability to make sure the
trunk is in sync with your tagged version.
You can do that by always using a branch for
development and merging code to trunk before releases.
Attila
> Date: Wed, 17 Jan 2007 00:18:30 -0800 (PST)
> From: alexsil <[EMAIL PROTECTED]>
> To: [email protected]
> Subject: Re: release:prepare
>
>
> Hi tom,
> unfortunalty svn doesn't support LockMod, infact i
> get the following message
> "[WARNING] Provider svn does not support edit
> operation."
>
> In any case lock mode doesn't resolve my problem. In
> fact this flag lock
> files only during release phase. My problem instead
> is to TAG the revision
> that correspond to last deploy in TEST before that
> binaries are deployed
> in server-farm.
>
> Thanks however
> Alex
>
>
> Tom Huybrechts wrote:
> >
> > would this help:
> >
>
http://maven.apache.org/plugins/maven-release-plugin/examples/lock-files.html
> > ?
> >
____________________________________________________________________________________
Finding fabulous fares is fun.
Let Yahoo! FareChase search your favorite travel sites to find flight and hotel
bargains.
http://farechase.yahoo.com/promo-generic-14795097
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
