If you did a revision copy, you would have to do commit to capture the changes to the POM. You couldn't do a straight revision copy. So the situation now become more complicated.
If you checkout revision x, someone may commit before you release incrementing the revision to x+1. You then run your prepare, incrementing the revision to x+2 to change the version of your pom to a released version. So you now have to copy revision x+2 of your pom to your tags folder but use revision x for everything else. The best solution I see is to not commit the changes to the POM which changes the version to a released version and continue to do a working copy as the plugin does now. Thoughts? --- Todd Thiessen > -----Original Message----- > From: Nick Stolwijk [mailto:[EMAIL PROTECTED] > Sent: Thursday, December 04, 2008 9:22 AM > To: Maven Users List > Subject: Re: Limitation of the release plugin? > > > Doing a copy from your working directory, however, is important. If > > you did a copy from an SVN revision you could potentially release > > something you didn't intend if someone commits to that > revision after > > the you checked out your working copy from that revion, but > before you > > performed the release. > > If the release plugin did a copy of the revision there would > be no problem. The problem is that you cannot make a copy of > the HEAD revision. You cannot commit anymore to any revision > (It would make a new revision) > > Hth, > > Nick Stolwijk > ~Java Developer~ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
