On Tue, Dec 9, 2008 at 6:31 PM, sverhagen <[EMAIL PROTECTED]> wrote: > 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.
Thanks for pointing that out-- making a change to the pom instead of the code wasn't a good test. I re-did it after making a change to the code from a different checkout, and release:prepare succeeded. I still tend to favor communication and a quiet period when a release is going on, as well as keeping a close eye on the commits list to make sure nothing slips in (or slips _by_, as in this case.) Still it's a good one to be aware of and to put in JIRA, if it's not already there. -- Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
