Did you try -DautoVersionSubmodules=true? Not sure if that would make a difference in this case but worth a shot.
--- Todd Thiessen > -----Original Message----- > From: David C. Hicks [mailto:[email protected]] > Sent: Wednesday, August 26, 2009 7:06 PM > To: maven Users > Subject: Help with batch-mode release? > > I'm trying to set up a script to handle an automated release process. > I'm using the "releaseVersion" and "developmentVersion" > properties to give me some flexibility with respect to the > assigned versions. > However, they don't seem to be sticking. > > For instance, my current version is 0.9.27-SNAPSHOT. I do a > release:prepare using the command: > > mvn --batch-mode release:prepare -DreleaseVersion=1.0.0.26 > -DdevelopmentVersion=1.0.0.27-SNAPSHOT > > The prepare builds a tag of 0.9.27 and sets the development > version to 0.9.28-SNAPSHOT. > > This is a multi-module project. Is that what's causing this? > Do I really have to specify the versions for each module? > Thanks, > Dave > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
