FWIW, I don't use the release plugin. Gary
On Mon, Nov 6, 2017 at 12:22 PM, Romain Manni-Bucau <rmannibu...@gmail.com> wrote: > Hmm, > > there are probably a lot of manual workarounds - like not using the > release plugin at all to start easy, but I was more looking for a > standard normalized procedure like mvn release:prepare && mvn > release:perform-rc && mvn release:promote-rc or something like that. > > Ideally 2 commands matching the release flow (create the RC - merging > prepare and perform probably - then close it once the vote passed) > > So read this thread more as making the releases more straight forward > than a blame on the plugin itself. > > Romain Manni-Bucau > @rmannibucau | Blog | Old Blog | Github | LinkedIn > > > 2017-11-06 20:19 GMT+01:00 Sergio Fernández <wik...@apache.org>: > > Just be sure you have pushChanges=false, so you can manually push the > work > > to your RC branch, but you don't push the tag. > > > > Anyways, the commit id is binding for a vote, not the tag (because can be > > changed). > > > > On Mon, Nov 6, 2017 at 11:14 AM, Romain Manni-Bucau < > rmannibu...@gmail.com> > > wrote: > > > >> Will not recopy what i said in jcs vote thread but git solves it > >> creating the tag locally so you can immediately copy it *locally* and > >> only push the rc tag for the vote duration. That said most of > >> communities push the tag on a fork and avoid any issue with the asf > >> repo. This is how git can solve that issue. > >> > >> 2017-11-06 19:16 GMT+01:00 Thomas Vandahl <t...@apache.org>: > >> > On 06.11.17 09:01, Romain Manni-Bucau wrote: > >> >> 2017-11-06 8:59 GMT+01:00 Jochen Wiedmann <jochen.wiedm...@gmail.com > >: > >> >>> On Mon, Nov 6, 2017 at 7:27 AM, Romain Manni-Bucau > >> >>> <rmannibu...@gmail.com> wrote: > >> >>> > >> >>>> due to the RCx procedure we cant use the maven release plugin, any > >> >>>> plan to make it working with commons release procedure or do we > just > >> >>>> wait to move all to git? > >> >>> > >> >>> What problem is there when using the plugin? > >> >> > >> >> the plugin doesn't support the RCx branch creation without corrupting > >> >> the final release - due to nexus. It would be fancy to be able to > >> >> *automatically* create the right tag if flagged as such in the pom. > >> > > >> > There is nothing wrong with the plugin. If you read the commons > release > >> > docs, the chapter about the maven-release-plugin says nothing about > RCs, > >> > let alone tags. Moving to git would not help as long as the POM > >> > scm-section still points to the original tag. (And I'm not suggesting > to > >> > change that!) > >> > > >> > 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 > >
