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 > ? > > On 1/16/07, alexsil <[EMAIL PROTECTED]> wrote: >> >> Ok, you are right, but I think to have exposed bad my problem. >> I don't want to release a historical version. >> >> I want to be sure that while I'm releasing a new version nobody can make >> a >> commit that invalid the version of code of the created TAG against the >> binary (in the maven repository) that will be deployed in server-farm. >> More deeply: >> the maven release process doesn't update the code, but get the latest >> version from tha Maven repository. >> The binary present in the MAVEN repository correspond to a SVN revision. >> If >> the TEST process gives the OK, the binary will be depoyed in server farm. >> But when I use Maven plugin to to this, the tag created from Trunk sure >> doesn't correspond to binary because in the time passed from release in >> TEST >> ed OK TEST several commits are done on Trunk from developers. >> Bye >> Alex. >> >> >> Tom Huybrechts wrote: >> > >> > you have to decide what you need: >> > - if you really are releasing a historical version, you probably don't >> > want the modified poms in trunk >> > - if you do want them, you should merge branch to trunk >> > >> > On 1/16/07, alexsil <[EMAIL PROTECTED]> wrote: >> >> >> >> Sorry Tom, >> >> but if I use a Branch instead of Trunk maven release plugin commit the >> >> "next >> >> version pom" on the Branch and not on the Trunk that is the right >> place >> >> ??? >> >> Is it true ???? >> >> >> >> Thanks >> >> Alex >> >> >> >> >> >> Tom Huybrechts wrote: >> >> > >> >> > during release:prepare the release plugin will need to change the >> >> > versions in the pom and make commits. You can't do that if you do >> not >> >> > have the latest versions of your poms, right ? >> >> > >> >> > An alternative would be to create a branch based on a revision, and >> >> > release from there. >> >> > >> >> > Tom >> >> > >> >> > On 1/16/07, alexsil <[EMAIL PROTECTED]> wrote: >> >> >> >> >> >> Thank you for the answer Marc, but tag is the name of the tag not >> the >> >> >> revision. >> >> >> Bye >> >> >> Alex >> >> >> >> >> >> >> >> >> marc gassmann wrote: >> >> >> > >> >> >> > alexsil said the following on 16.01.2007 11:20: >> >> >> >> Is possible force a revision to use during release:prepare o >> >> >> >> release:perform >> >> >> >> instead of use a default HEAD revision ??? >> >> >> >> Thanks in advance >> >> >> >> >> >> >> > >> >> >> > I didnt tried it ... but my guess is 'tag' >> >> >> > have a look here. it could be the same as in maven 1 >> >> >> > >> >> >> >> >> >> http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html#tag >> >> >> > >> >> >> > cheers >> >> >> > marc >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> --------------------------------------------------------------------- >> >> >> > To unsubscribe, e-mail: [EMAIL PROTECTED] >> >> >> > For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> > >> >> >> > >> >> >> > >> >> >> >> >> >> -- >> >> >> View this message in context: >> >> >> http://www.nabble.com/release%3Aprepare-tf3020091s177.html#a8391351 >> >> >> Sent from the Maven - Users mailing list archive at Nabble.com. >> >> >> >> >> >> >> >> >> >> --------------------------------------------------------------------- >> >> >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> >> >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> >> >> >> >> >> > >> >> > >> --------------------------------------------------------------------- >> >> > To unsubscribe, e-mail: [EMAIL PROTECTED] >> >> > For additional commands, e-mail: [EMAIL PROTECTED] >> >> > >> >> > >> >> > >> >> >> >> -- >> >> View this message in context: >> >> http://www.nabble.com/release%3Aprepare-tf3020091s177.html#a8393628 >> >> Sent from the Maven - Users mailing list archive at Nabble.com. >> >> >> >> >> >> --------------------------------------------------------------------- >> >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> >> >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: [EMAIL PROTECTED] >> > For additional commands, e-mail: [EMAIL PROTECTED] >> > >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/release%3Aprepare-tf3020091s177.html#a8394965 >> Sent from the Maven - Users mailing list archive at Nabble.com. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/release%3Aprepare-tf3020091s177.html#a8406197 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
