Maintaining versions in a multi-module project
I am working on a multi-module project where I see that some of the module POMs have versions different from the parent POM. Apparently, developers have made changes to some of the modules and updated the version of only those modules. I also see another project where irrespective of which modules have been modified, developers modify the versions of all modules using mvn versions command to keep all of them in-sync. I am new to maven and have started using it only since last six months. Seeing the above mentioned two projects, I am confused what is the right path to take - updating all module versions irrespective of where changes are, or updating only those module versions where something changed. Thanks, Anuj Agrawal
Re: Maintaining versions in a multi-module project
Use whatever works best for you. I have some projects where it is better for me to force them all in lock-step I have other projects where I let them run free. My general rule of thumb: if the modules are in the same GIT repo or the same Subversion trunk then they all will end up being released as one atomic group, so keep the version numbers in sync. If they are in different SCM instances then they will be released independently so let them run free On 11 September 2014 09:35, Anuj Agrawal anujagrawa...@gmail.com wrote: I am working on a multi-module project where I see that some of the module POMs have versions different from the parent POM. Apparently, developers have made changes to some of the modules and updated the version of only those modules. I also see another project where irrespective of which modules have been modified, developers modify the versions of all modules using mvn versions command to keep all of them in-sync. I am new to maven and have started using it only since last six months. Seeing the above mentioned two projects, I am confused what is the right path to take - updating all module versions irrespective of where changes are, or updating only those module versions where something changed. Thanks, Anuj Agrawal
Re: Maintaining versions in a multi-module project
I use the maven versions plugin for this… I just run: mvn versions:set -DnewVersion=0.0.3 mvn versions:commit and all my pom.s are updated. On Thu, Sep 11, 2014 at 6:02 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: Use whatever works best for you. I have some projects where it is better for me to force them all in lock-step I have other projects where I let them run free. My general rule of thumb: if the modules are in the same GIT repo or the same Subversion trunk then they all will end up being released as one atomic group, so keep the version numbers in sync. If they are in different SCM instances then they will be released independently so let them run free On 11 September 2014 09:35, Anuj Agrawal anujagrawa...@gmail.com wrote: I am working on a multi-module project where I see that some of the module POMs have versions different from the parent POM. Apparently, developers have made changes to some of the modules and updated the version of only those modules. I also see another project where irrespective of which modules have been modified, developers modify the versions of all modules using mvn versions command to keep all of them in-sync. I am new to maven and have started using it only since last six months. Seeing the above mentioned two projects, I am confused what is the right path to take - updating all module versions irrespective of where changes are, or updating only those module versions where something changed. Thanks, Anuj Agrawal -- Founder/CEO Spinn3r.com Location: *San Francisco, CA* blog: http://burtonator.wordpress.com … or check out my Google+ profile https://plus.google.com/102718274791889610666/posts http://spinn3r.com
