On Tue, Dec 9, 2008 at 6:07 PM, sverhagen <[EMAIL PROTECTED]> wrote:
>
> Hi. We heavily use the Maven release plugin.
> Following scenario:
> * Developers update from SVN
> * Developer 1 commits a change
> * Developer 2 commits a change and releases ("mvn release:prepare")
>
> Because developer 2 does not explicitly update from SVN, the change from
> developer 1 will not be in the release. Hard to track down, hard to detect.
Have you actually had this happen? I'm pretty sure it's going to
complain that the working copy isn't up to date when it tries to
tag...
Yep, it does:
$ mvn release:prepare
...
[INFO] Checking in modified POMs...
[INFO] Executing: svn --non-interactive commit --file
/tmp/maven-scm-1832181566.commit --targets
/tmp/maven-scm-10681-targets
[INFO] Working directory: /private/tmp/hello1
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Unable to commit files
Provider message:
The svn command failed.
Command output:
svn: Commit failed (details follow):
svn: Your file or directory 'pom.xml' is probably out-of-date
svn: resource out of date; try updating
This is with Subversion 1.4.4 on OS X.
Still, I'd suggest:
Developer A communicates that a release is in progress/code freeze.
Developer B holds commits, or one of them works on a branch.
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
