The release plugin does an awful lot more than deploy. The usual case is that during development, your version is set to a snapshot - the plugin changes it to a release version, commits the change to CM and tags it, among other things. Deploy won’t do any of that.
That said, your point about the versions is a good one. It makes no sense to set the snapshot back to match the version just released. Regards, Russ On Nov 19, 2013, at 10:36 AM, Ron Wheeler <rwhee...@artifact-software.com> wrote: > I never us the release plug-in so you can take my comments with a grain of > salt. > > From reading the docs I am not sure that these are right. > > -DdevelopmentVersion=52.0.0-SNAPSHOT -DreleaseVersion=52.0.0 > > > My interpretation is that you are trying to get maven to go backwards. > You are saying to release 52.0.0 and make a new snapshot of 52.0.0-SNAPSHOT > which is not right. > > -DdevelopmentVersion=52.0.1-SNAPSHOT -DreleaseVersion=52.0.0 > > seems to be the right arguments. > > I am not sure why you are even using the release plug-in at all. If you just > want to deploy a release of one module just use the deploy command. > Release wants to do a some magic to your project to get it setup for the next > development cycle and I am not sure that you really want to do all this at > this time. > > If you just want to deploy the current release and start working on > 52.0.1-SNAPSHOT for one module, you can just deploy and change the pom to > point the 52.0.1-SNAPSHOT parent and you are ready for the next development > cycle. - Not worth wrestling with the release plug-in. > > Ron > > > On 19/11/2013 10:09 AM, laredotornado-3 wrote: >> I hadn't specified a Maven release version anywhere, so I assume you meant >> like this >> >> mvn -B -DdevelopmentVersion=52.0.0-SNAPSHOT -DreleaseVersion=52.0.0 >> -Dusername=***** -Dtag=myprojectt-52.0.0 -DskipTests -P prod -Dresume=false >> -DdryRun=true org.apache.maven.plugins:maven-release-plugin:2.4.2:prepare >> >> However, I get the same errors, whether I specify the project version like >> this: >> >> <parent> >> <artifactId>subco</artifactId> >> <groupId>org.mainco.subco</groupId> >> <version>52.0.0</version> >> </parent> >> >> or like this >> >> <parent> >> <artifactId>subco</artifactId> >> <groupId>org.mainco.subco</groupId> >> <version>52.0.0-SNAPSHOT</version> >> </parent> >> >> Was there something more I needed to do? - >> >> >> >> -- >> View this message in context: >> http://maven.40175.n5.nabble.com/Is-it-possible-to-release-a-child-module-that-isn-t-listed-in-the-parent-s-list-of-modules-tp5775784p5775848.html >> Sent from the Maven - Users mailing list archive at Nabble.com. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> >> > > > -- > Ron Wheeler > President > Artifact Software Inc > email: rwhee...@artifact-software.com > skype: ronaldmwheeler > phone: 866-970-2435, ext 102 > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
