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]
