Re: Maven release with sub modules have miss match version??

Thanks Stephen, it is very helpful -Dan On Wed, Sep 2, 2015 at 12:50 PM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > I have done it (by accident). It works but is super annoying... Especially > when you end up with and off-by-one version number in a couple of the > modules...

Re: Maven release with sub modules have miss match version??

I have done it (by accident). It works but is super annoying... Especially when you end up with and off-by-one version number in a couple of the modules... (Happened when some developer wanted to do a point release of one module and kicked off the über-release so that one went to 1.5.1 and

Re: Maven release with sub modules have miss match version??

Thanks Robert, if anyone has done this scenario, please share your experience :-) -Dan On Tue, Sep 1, 2015 at 8:51 AM, Robert Scholte wrote: > it should support separate versions, although it is not the best practice. > try running it with -DdryRun first to confirm. > >

Maven release with sub modules have miss match version??

Hi, is it possible that release plugin can handle this situation? Or the entire release tree must use the same release version. Period Thanks -Dan

Re: Maven release with sub modules have miss match version??

it should support separate versions, although it is not the best practice. try running it with -DdryRun first to confirm. Robert Op Tue, 01 Sep 2015 17:04:16 +0200 schreef Dan Tran : Hi, is it possible that release plugin can handle this situation? Or the entire release