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 everything else to 1.6... Then the subsequent "fixing" of their mistake... Which was only discovered with everything else on 1.11 while that module was on 1.5.6 and we'd gained a 1.8.3 and a 1.10.1 module thanks to copycat developers... Well that was "fun") Don't do it is my recommendation. If they need different version numbers then they most likely need separate release lifecycles and thus should be separate release roots On Tuesday, September 1, 2015, Dan Tran <dant...@gmail.com> wrote: > Thanks Robert, > > if anyone has done this scenario, please share your experience :-) > > -Dan > > On Tue, Sep 1, 2015 at 8:51 AM, Robert Scholte <rfscho...@apache.org > <javascript:;>> wrote: > > > 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 <dant...@gmail.com > <javascript:;>>: > > > > > > 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 > >> > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > <javascript:;> > > For additional commands, e-mail: users-h...@maven.apache.org > <javascript:;> > > > > > -- Sent from my phone
