I see it:
> On Oct 25, 2015, at 10:44 PM, Cameron McKenzie <[email protected]> wrote: > > I'm having some issues with getting Nexus to work. I can see that the > orgapachecurator-1019 > repo is present and has the right artefacts but I can't see it via the > https://repository.apache.org/content/repositories/ link. Any ideas? > > On Mon, Oct 26, 2015 at 12:54 PM, Cameron McKenzie <[email protected]> > wrote: > >> Thanks Jordan, will give that a spin. >> >> On Mon, Oct 26, 2015 at 12:48 PM, Jordan Zimmerman < >> [email protected]> wrote: >> >>> Use the versions plugin to set back to whatever version you need: >>> >>> mvn versions:set -DnewVersion=2.9.1-SNAPSHOT >>> >>> It does some work and then you commit it via: >>> >>> mvn versions:commit >>> >>> Believe it or not, this doesn’t go a git commit :) So, commit that: >>> >>> git commit -a -m “Back to 2.9.1-SNAPSHOT” >>> >>> >>> >>>> On Oct 25, 2015, at 8:40 PM, Cameron McKenzie <[email protected]> >>> wrote: >>>> >>>> The master branch is currently in a bit of a bogus state due to the >>> backed >>>> out release last week. Do I need to manually go and change the versions >>> in >>>> the pom.xml in each sub project to fix things up? I was expecting the >>>> release target to just overwrite things, but it generated artefacts >>> with a >>>> 2.9.2 tag even though I explicitly asked for a 2.9.1 version. >>>> cheers >>>> >>>> On Thu, Oct 22, 2015 at 9:55 AM, Jordan Zimmerman < >>>> [email protected]> wrote: >>>> >>>>> Yeah - let me look into that one. >>>>> >>>>>> On Oct 21, 2015, at 1:16 AM, Cameron McKenzie <[email protected] >>>> >>>>> wrote: >>>>>> >>>>>> Should we be holding off on this build until CURATOR-274 is >>> investigated? >>>>>> Looks like it could be a bit of a show stopper? >>>>>> >>>>>> On Wed, Oct 21, 2015 at 3:27 PM, Cameron McKenzie < >>>>> [email protected]> >>>>>> wrote: >>>>>> >>>>>>> Ok thanks, will give it a spin when I get a minute. >>>>>>> cheers >>>>>>> >>>>>>> On Wed, Oct 21, 2015 at 2:35 PM, Jordan Zimmerman < >>>>>>> [email protected]> wrote: >>>>>>> >>>>>>>> It may be because the <scm> tag is messed up. I noticed it in the >>> 3.0.0 >>>>>>>> branch and fixed it there. Change the <scm> tag to HEAD. >>>>>>>> >>>>>>>> -Jordan >>>>>>>> >>>>>>>> >>>>>>>>> On Oct 20, 2015, at 9:13 PM, Cameron McKenzie < >>> [email protected] >>>>>> >>>>>>>> wrote: >>>>>>>>> >>>>>>>>> The current release process seems to be creating a >>>>>>>> CURATOR-2.9.1-SNAPSHOT >>>>>>>>> tag. Is that expected? I notice that there are both 3.0.0-SNAPSHOT >>> and >>>>>>>> just >>>>>>>>> 3.0.0 tags, but for all the prior releases, there is no SNAPSHOT >>> tag. >>>>>>>>> >>>>>>>>> Have I stuff something up? I just used the standard release process >>>>> from >>>>>>>>> the wiki: >>>>>>>>> mvn -P apache-release release:prepare >>>>>>>>> mvn -P apache-release release:perform >>>>>>>>> >>>>>>>>> So, the tag doesn't match what the wiki steps involve for doing the >>>>>>>>> checkout in git to do the actual release. Should I just manually >>>>> create >>>>>>>> a >>>>>>>>> tag without the -SNAPSHOT suffix? Or should I be redoing the >>> release >>>>> in >>>>>>>>> some other manner? >>>>>>>>> >>>>>>>>> cheers >>>>>>>>> >>>>>>>>> >>>>>>>>> On Wed, Oct 21, 2015 at 7:37 AM, Cameron McKenzie < >>>>>>>> [email protected]> >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> I will start looking at a 2.9.1 release. >>>>>>>>>> >>>>>>>>>> On Wed, Oct 21, 2015 at 1:53 AM, Jordan Zimmerman < >>>>>>>>>> [email protected]> wrote: >>>>>>>>>> >>>>>>>>>>> I moved the 1 remaining issue out to the next release. Can one of >>>>> the >>>>>>>>>>> other committers start on 2.9.1? >>>>>>>>>>> >>>>>>>>>>> -Jordan >>>>>>>>>>> >>>>>>>>>>>> On Oct 20, 2015, at 1:54 AM, Flaath, Jaran < >>>>>>>>>>> [email protected]> wrote: >>>>>>>>>>>> >>>>>>>>>>>> Hi, >>>>>>>>>>>> >>>>>>>>>>>> Just wondering if there is any ETA on version 2.9.1 of Curator? >>>>>>>>>>>> >>>>>>>>>>>> Best, >>>>>>>>>>>> Jaran Flaath >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>> >>>>> >>> >>> >>
