Hi! I am using maven-2.0.4 (on WindowsXP, CVS on Solaris) and have exactly the same problem during release:prepare of a multiproject build. The child poms were updated and checked in, the master pom is updated (and so locally changed), but not checked in before tagging the source tree. This leads during tagging to the failure with the message ... pom.xml is locally modified .... Seems to be a bug ...
As a workaround, i manually checked the master pom into CVS, performs again the release:prepare(which successfully uses the before created release.properties) and the tagging is successfull, (At the end the master pom with the new snapshot version number is again not checked into CVS, just the child poms with the new snapshot version numbers are checked into CVS, i do not know if this is a feature or a bug) Greetings, Gelkand -- View this message in context: http://www.nabble.com/Question-about-release-plugin-on-pom-archtype-t1403232.html#a3867837 Sent from the Maven - Users forum at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
