On 28 August 2018 at 09:25, Mark Struberg <strub...@yahoo.de.invalid> wrote: >> This is unlikely to happen as long as it does not cover multi-module builds > > The maven-release-plugin covers multi-module releases since many years. > > In the projects I'm working on there is no 'release manager'. > _Everybody_ can do releases without having to know anything special. > This is where the maven-release-plugin really shines. > Just use mvn release:prepare + mvn release:perform and be done.
If it works first time. The problem is that the Maven release plugin design assumes that the first release attempt will succeed. As such, it updates trunk to the new snapshot version. (This causes issues with CI builds) It also assumes that the current workspace does not contain anything it should not. Neither of these assumptions is valid in general. The Apache POM also makes assumptions about the content of the dist/ folder. > Of course it's fine if projects use ant, etc. > But ideally there should be a single way to kick of a release (fully > automated, same target name across projects, etc) > > LieGrue, > strub > > >> Am 26.08.2018 um 10:43 schrieb Thomas Vandahl <t...@apache.org>: >> >> On 25.08.18 16:14, Gilles wrote: >>>>> Probably for those who don't want to use the release plugin :-) >>>> >>>> I was mainly following up on the thread about updating CP to AP 21 [1] >>>> >>>> But yes, it could be used as an alternative hashing method. >>> >>> I thought that the release plugin was intended for all >>> components to converge on the same release "recipe"... >> >> This is unlikely to happen as long as it does not cover multi-module builds. >> >> Bye, Thomas. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
