problem in maven release plugin

2 messages Options
Embed this post
Permalink
Mr Debasis

problem in maven release plugin

Reply Threaded More More options
Print post
Permalink

1.while executing the goal release:prepare it is committing the pom file
twice.
   one is -preparerelease versionno . second is-preparation for next
development iteration
2.suppose my releaseversion no is 3.0 .previous was 2.9.
 In first commit i,e prepare release my pom file version is getting changed
to 3.0 including the submodules.
 but again in the second commit i,e preparation for next development
iteration the pom version is getting modified to 2.9 including
submodules.which i don't want.

is there any way to prevent this second committ for next development
iteration.i want only one committ i,e prepare release.i don't want my
version no should go back to the previous version.

mvn -B -Dtag=3.0.0.0.RC17
-Dproject.dev.com.arisglobal.aglite:aglite-platform=3.0.0.0.RC17
-Dproject.dev.com.arisglobal.aglite:aglite-demo=3.0.0.0.RC17
-Dproject.dev.com.arisglobal.aglite:aglite-admin=3.0.0.0.RC17
-Dproject.dev.com.arisglobal.aglite:aglite-parent=3.0.0.0.RC17
-Dproject.rel.com.arisglobal.aglite:aglite-parent=3.0.0.0.RC17
-Dproject.dev.com.arisglobal.aglite:aglite-core=3.0.0.0.RC17
-Dproject.dev.co.arisglobal.aglite:aglite-web=3.0.0.0.RC17
-Dproject.rel.com.arisglobal.aglite:aglite-demo=3.0.0.0.RC17
-Dproject.rel.co.arisglobal.aglite:aglite-platform=3.0.0.0.RC17
-Dproject.rel.com.arisglobal.aglite:aglite-admin=3.0.0.0.RC17
-Dproject.rel.co.arisglobal.aglite:aglite-web=3.0.0.0.RC17
-Dproject.rel.com.arisglobal.aglite:aglite-maven-plugin=3.0.0.0.RC17
-Dproject.dev.co.arisglobal.aglite:aglite-maven-plugin=3.0.0.0.RC17
-Dproject.rel.com.arisglobal.aglite:aglite-core=3.0.0.0.RC17 release:prepare

here i want my pom version no for rel as well as dev should be
3.0.0.0.RC17.In the first committ it is 3.0.0.0.RC17 and in the second
commit it is becoming 3.0.0.0.RC16.

i tried to run by giving all the rel and dev version manually.then also in
the next development iteration commit the version no is going back to the
previous versio.



3.release:perform runs two goal one is site-deploy and other is deploy goal.
i want only one goal should be fired that is deploy during
release:perform.is it possible??

Thanks,
Debasis
--
View this message in context: http://old.nabble.com/problem-in-maven-release-plugin-tp26230046p26230046.html
Sent from the Maven - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Anders Hammar

Re: problem in maven release plugin

Reply Threaded More More options
Print post
Permalink
>
> 3.release:perform runs two goal one is site-deploy and other is deploy
> goal.
> i want only one goal should be fired that is deploy during
> release:perform.is it possible??
>
>
You can change that through the goals param:
http://maven.apache.org/plugins/maven-release-plugin/perform-mojo.html#goals

/Anders