On 28 August 2018 at 19:36, Matt Sicker <boa...@gmail.com> wrote: > On Tue, 28 Aug 2018 at 05:03, sebb <seb...@gmail.com> wrote: > >> 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) >> > > Would it work if you made a release branch first? Then you wouldn't merge > the release branch to master until the voted upon release candidate is > accepted.
Unless it relies on updating trunk rather than the current workspace, I guess that should work. But it's extra work, so why does the plugin not do it for you? > >> It also assumes that the current workspace does not contain anything >> it should not. >> > > It doesn't check out the tag into a separate directory to build the release > artifacts? Last time I checked it did not. > > -- > Matt Sicker <boa...@gmail.com> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
