Thanks for your quick response.
Wendy Smoak-3 wrote: > > [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 > Yours fails on inconsistent pom.xml. In my scenario I can tell you that the POM did not change due to the work of either one of the developers; the sources changed. Also, yours fails on commiting something to the trunk, rather than making the tag. I ended up with an issue being fixed in a revision before a release, the release being on the production system, and the fix missing from the production system. I am *very* concerned about this opportunity for errors. Except for the release tag, my whole scenario plays on trunk. Wendy Smoak-3 wrote: > > 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. > Their work was sequential in time, not parallel. If the release plugin would've been bullet proof in this regard, as I always expected it to be (until now), communication would not have been necessary. (I agree that it would have been, when they'd been working on the same thing at the same time. No argument.) -- View this message in context: http://www.nabble.com/Up-to-date-release-tp20925759p20926113.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
