Can you check with infra on this? I can’t think of anything else. I just double checked the listing on people.apache.org and you’re in there:
randgalt@minotaur:~$ list_unix_group.pl curator cammckenzie cheddar dragonsinth enis iocanel lresende mahadev mdrob phunt randgalt zarfide -JZ On September 2, 2015 at 8:11:11 AM, Mike Drob ([email protected]) wrote: Yes, like I said, I've double-checked my maven settings and verified that I can log in to Nexus using those same credentials. On Tue, Sep 1, 2015 at 11:53 PM, Jordan Zimmerman <[email protected]> wrote: Do you have your Maven settings.xml set up per: https://cwiki.apache.org/confluence/display/CURATOR/For+Curator+Committers#ForCuratorCommitters-maven-settings Also, check if you can log into https://repository.apache.org/ -Jordan On September 1, 2015 at 2:42:55 PM, Mike Drob ([email protected]) wrote: Hey all, I was trying to build and put up a release candidate following the instructions on the wiki, but ran into [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project apache-curator: Failed to deploy artifacts: Could not transfer artifact org.apache.curator:apache-curator:pom:2.9.0 from/to apache.releases.https (https://repository.apache.org/service/local/staging/deploy/maven2): Failed to transfer file: https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/curator/apache-curator/2.9.0/apache-curator-2.9.0.pom. Return code is: 401, ReasonPhrase: Unauthorized. -> [Help 1] I verified that I can log in to Nexus, and that my password is correct in my settings.xml - is there a group I need to be added to or permissions granted or anything like that? Thanks, Mike On Sun, Aug 30, 2015 at 10:26 PM, Cameron McKenzie <[email protected]> wrote: Ok, I think that's ready to be merged then. Mike's had a look at the PR. On Mon, Aug 31, 2015 at 1:25 PM, Jordan Zimmerman < [email protected]> wrote: > Yes - I think simple logging is the best thing for CURATOR-228. > > > On August 30, 2015 at 4:05:52 PM, Cameron McKenzie ([email protected]) > wrote: > > You are indeed correct! I was referring to CURATOR-228. > > On Mon, Aug 31, 2015 at 8:48 AM, Jordan Zimmerman < > [email protected]> wrote: > >> CURATOR-233? Do you mean something else? >> >> >> >> On August 30, 2015 at 3:02:18 PM, Cameron McKenzie ( >> [email protected]) wrote: >> >> What are people's thoughts on CURATOR-233? I think that it may be worth >> merging in the fix that I have done for CURATOR-233 (just logging a >> warning) as this will stop the hard loop occurring in this situation. >> >> It's not a perfect fix by any means, but it's better than the current >> state >> of affairs. Maybe we could use this to close CURATOR-233 and open another >> for a more reliable fix that respects the persistent ephemeral contract? >> >> On Mon, Aug 31, 2015 at 3:07 AM, Jordan Zimmerman < >> [email protected]> wrote: >> >> > The only outstanding issue on 2.9.0 is CURATOR-233. I’d like to push >> that >> > to 2.9.1 and get a release started. Thoughts? >> > >> > -Jordan >> > >> > >> > >> >> >
