OK, I have modified my parent pom to be in the directory immediately above my parent pom.
I.E. pom.xml proj1/pom.xml proj2/pom.xml Now when I run release:prepare it updates all of my dependencies from 1.0.0-SNAPSHOT to 1.0.0. Then it returns an error that is cannot tag since the pom has uncommitted changes! Shouldn't the release 1.0.0 pom be committed on the parent and all child projects before the tag is executed? Todd On 4/5/06, dan tran <[EMAIL PROTECTED]> wrote: > > yes it is a bug > > http://jira.codehaus.org/browse/MRELEASE-6 > > -D > > > On 4/5/06, Todd Nine <[EMAIL PROTECTED]> wrote: > > > > I'm having some trouble with the prepare target of the release plug > in. I > > have a pom artifact type, and I have several child modules like the > > example > > below. I'm using the eclipse flat directory structure > > > > <modules> > > <module>../module1</module> > > <module>../module2</module> > > </modules> > > > > > > when I perform "mvn release:prepare" I'm prompted for the version of the > > parent pom as well as all child poms. However when maven should tag the > > source, it never tags the child poms and as a result, the > > release.propertiesall have HEAD as the tag to check out for a build. > > It does correctly update > > all the poms and check in the new development version, but doesn't tag > the > > source. Is this a bug? > > > > Todd > > > > > >
