> Would there be any harm in having the release plugin 
> perform an 'svn update' at the start of the release:prepare goal?

I think this would be no good idea. One of the prerequisites for a project to 
be released is that there is NO change between your current work and the branch 
your currently on ('trunk' also counts as a branch for this). The 
ScmCheckForModificationsPhase calls a scm:status and looks for changed files. 

Automatically updating first would mean that you may get changes from another 
checkin, which are merged into your own source silently! So you do a release 
and CANNOT BE SURE that it really has the contentyou thought of.

LieGrue,
strub


--- Ken Tanaka <[EMAIL PROTECTED]> schrieb am Mo, 25.8.2008:

> Von: Ken Tanaka <[EMAIL PROTECTED]>
> Betreff: Re: Having trouble with Maven release plugin using SubVersion
> An: "Maven Users List" <[email protected]>
> CC: [EMAIL PROTECTED]
> Datum: Montag, 25. August 2008, 19:14
> I think I found a solution:
> 
> Before issuing the 'mvn release:prepare' command,
> an 'svn update'  on 
> the parent directory of the directory renamed (or at the
> top level) will 
> update the SubVersion metadata. The update command
> doesn't print 
> anything so it appears like it doesn't do anything, but
> it's required 
> nonetheless.  Would there be any harm in having the release
> plugin 
> perform an 'svn update' at the start of the
> release:prepare goal?
> 
> Also found a few flaws with my earlier perl script.
> Should have issued a 'mvn clean' at line 87 so the
> target directory is 
> not added to version control.
> Forgot to add a tags directory: mkdir aProject/tags, after
> line 106
> Could have left out the creation of a sample configuration
> file 
> (myconf.xml) lines 88 to 100, it wasn't needed to
> reproduce the problem.
> The directory name could have been "foo" and
> renamed to "bar", so this 
> has nothing to do with the standard maven 2 naming
> convention of 
> src/main/config.
> If I created a FILE, not a directory, then there would be
> no error, even 
> without the 'svn update'.
> 
> -Ken
> 
> Dennis Lundberg wrote:
> > Did you use the 'svn move ...' command to
> rename the directory or did
> > you do it directly on the file system for your working
> copy?
> >
> > If you did the second your working copy will not have
> correct subversion
> > metadata.
> >
> > Ken Tanaka wrote:
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail:
> [EMAIL PROTECTED]

__________________________________________________
Do You Yahoo!?
Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen 
Massenmails. 
http://mail.yahoo.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to