Here we are: http://repo1.maven.org/maven2/org/apache/ranger/
Colm. On Tue, Jul 19, 2016 at 3:40 PM, Selvamohan Neethiraj <[email protected]> wrote: > +1 for promotion of the staged version to release. > > Thanks a lot Colm …. > > Selva- > > From: Colm O hEigeartaigh <[email protected]> > Reply-To: "[email protected]" < > [email protected]>, "[email protected]" < > [email protected]> > Date: Tuesday, July 19, 2016 at 7:21 AM > To: "[email protected]" <[email protected]> > Cc: Selvamohan Neethiraj <[email protected]>, "[email protected]" < > [email protected]> > > Subject: Re: [MENTORS] - Need help in binary release of Apache Ranger > 0.6.0 (incubating) > > Ok here it is: > https://repository.apache.org/content/repositories/orgapacheranger-1003/ > > Please give me a "+1" and I will promote it to maven central. > > I think the reason you were getting an authorization error is that you need > a Server entry in your settings.xml with a matching Id to > "apache.staging.https". Incidentally, doing a "deploy" fails when you try > to "close" the repo in r.a.o, as we don't have the gpg plugin configured. I > just added it locally - I will also add it to the master pom so that it's > fixed for the next release. > > Colm. > > On Tue, Jul 19, 2016 at 10:05 AM, Selvamohan Neethiraj < > [email protected]> wrote: > > Thanks Colm, If you can, please publish the binaries build from the > release source for 0.6.0 ranger. > > I am still trying to find out as why I can not publish ... > > Thanks, > Selva- > > Get Outlook for iOS<https://aka.ms/o0ukef> > > _____________________________ > From: Colm O hEigeartaigh <[email protected]<mailto:[email protected] > <[email protected]> > >> > Sent: Tuesday, July 19, 2016 4:59 AM > Subject: Re: [MENTORS] - Need help in binary release of Apache Ranger > 0.6.0 (incubating) > To: <[email protected]<mailto: > [email protected]>> > Cc: Selvamohan Neethiraj <[email protected]<mailto:[email protected]> > <[email protected]%3E>>, > <[email protected]<mailto:[email protected]> > <[email protected]%3E>> > > > Hi Selva, > > If you want help with deploying the artifacts to r.a.o let me know...I > definitely have access. > > Colm. > > On Mon, Jul 18, 2016 at 6:16 PM, Josh Elser <[email protected]<mailto: > [email protected]>> wrote: > > > Regarding the binary release after-the-fact, it seems like I am concerned > > about nothing. > > > > > > > > https://lists.apache.org/thread.html/7b70e963f9496937ead0bfc8c1df9c14eca737678b663e93bc470e40@1422484930@%3Cgeneral.incubator.apache.org%3E > > > > The suggestion was made "Don't ever look at the binary files". I don't > > understand this from a licensing perspective or a "these binaries end up > on > > ASF hardware", but the Ranger podling is not the place I need post to try > > to understand this better. Sorry for the derailing. > > > > LMK if you can log into repository.apache.org< > http://repository.apache.org> but still not deploy > > successfully. Using a `mvn -X` might help get you some more debug -- it > > could be something like a SSL library mismatch (e.g. if you have a very > old > > JVM). > > > > Josh Elser wrote: > > > >> I'm talking with some others on the subject right now -- it's not clear > >> to me whether or not what you're presently trying to do is OK. My gut > >> reaction was that you're releasing non-vetted artifacts which is a > >> no-no. I'm going to do some digging to see what I can find. If anyone > >> can send me something to read on the matter, I'd be extremely happy. > >> > >> I've been pointed to > >> > >> > > https://lists.apache.org/thread.html/b88d3886a1dfb0156e005214657474e0fc6cb7d81eabfc1ac9fa562a@1422535390@%3Cdev.nifi.apache.org%3E > >> already. I have a lot of respect for Benson, so perhaps I am wrong. > >> > >> Re the authentication: can you successfully log into > >> https://repository.apache.org/? These should be the credentials you > >> need. I'm not sure if your mentors need to grant you some karma (it's > >> been a very long time since I first got set up). > >> > >> Selvamohan Neethiraj wrote: > >> > >>> Josh: > >>> > >>> Thanks for your quick response …. > >>> > >>> Is there a separate VOTE needed for binary release? If so, can someone > >>> provide me the proper process to get the binary release VOTE done asap. > >>> > >>> Here is my ~/.m2/settings.xml > >>> > >>> > > =============================================================================== > >>> > >>> <settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"; > >>> > >>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > >>> > >>> xsi:schemaLocation="<http:>http://maven.apache.org/SETTINGS/1.0.0 > >>> http://maven.apache.org/xsd/settings-1.0.0.xsd";> > >>> > >>> <servers> > >>> > >>> <!-- To publish a snapshot of some part of Maven --> > >>> > >>> <server> > >>> > >>> <id>apache.snapshots.https</id> > >>> > >>> <username>sneethir</username> > >>> > >>> <password>***********</password> > >>> > >>> </server> > >>> > >>> <!-- To stage a release of some part of Maven --> > >>> > >>> <server> > >>> > >>> <id>apache.releases.https</id> > >>> > >>> <username>sneethir</username> > >>> > >>> <password>****************</password> > >>> > >>> </server> > >>> > >>> <server> > >>> > >>> <id>apache.staging.https</id> > >>> > >>> <username>sneethir</username> > >>> > >>> <password>****************</password> > >>> > >>> </server> > >>> > >>> </servers> > >>> > >>> </settings> > >>> > >>> > >>> > > =============================================================================== > >>> > >>> > >>> The error seems to be unauthorized instead of Authentication failure. > >>> Also, I have confirmed that the BASIC AUTH header is going along with > >>> the HTTP request to POST these artifacts to staging area (via TCPDUMP > >>> and using HTTP protocol – just to validate the AUTH http headers are > >>> going as part of the request). > >>> > >>> Is there any special permission needed to publish these POM and JAR > >>> files ? If so, who can grant these access ? > >>> > >>> Thanks, > >>> Selva- > >>> > >>> > >>> From: Josh Elser <[email protected]<mailto:[email protected] > <[email protected]>> <mailto: > [email protected]>> > >>> Reply-To: "[email protected]<mailto: > [email protected]> > >>> <mailto:[email protected]> > <[email protected]%3E>" > >>> <[email protected]<mailto: > [email protected]> > >>> <mailto:[email protected]> > <[email protected]%3E>> > >>> Date: Monday, July 18, 2016 at 12:19 PM > >>> To: "[email protected]<mailto:[email protected] > <[email protected]>> <mailto: > [email protected]>" > >>> <[email protected]<mailto:[email protected] > <[email protected]>> <mailto: > [email protected]>> > >>> Subject: Re: [MENTORS] - Need help in binary release of Apache Ranger > >>> 0.6.0 (incubating) > >>> > >>> Hi Selva, > >>> > >>> You didn't vote on any jars to deploy in 0.6.0-rc1. Why are you trying > >>> to deploy artifacts that were not voted upon? Am I missing something? > >>> > >>> That aside, your authorization issue is probably coming from a lack of > >>> credentials in your ~/.m2/settings.xml > >>> > >>> <servers> > >>> <server> > >>> <id>apache.snapshots.https</id> > >>> <username>elserj</username> > >>> <password>redacted</password> > >>> </server> > >>> <server> > >>> <id>apache.releases.https</id> > >>> <username>elserj</username> > >>> <password>redacted</password> > >>> </server> > >>> <server> > >>> <id>apache.staging.https</id> > >>> <username>elserj</username> > >>> <password>redacted</password> > >>> </server> > >>> </servers> > >>> > >>> Often, with a corresponding setup of your ~/.m2/settings-security.xml > to > >>> avoid a plaintext password in this file. > >>> > >>> https://maven.apache.org/guides/mini/guide-encryption.html > >>> > >>> On 2016-07-18 11:28 (-0400), Selvamohan Neethiraj <[email protected] > <mailto:[email protected] <[email protected]>> > >>> <mailto:[email protected]> <[email protected]%3E>> > >>> wrote: > >>> > >>> Thank you all rangers for their enormous contribution to the Apache > >>> Ranger 0.6.0 (incubating) release which has lot of new features and > >>> improvements over the previous major release %u2026. > >>> > >>> Now, I am trying to deploy the release JAR files in the > >>> > https://repository.apache.org/content/repositories/releases/org/apache/ > >>> using "maven deploy%u201D command from the source code associated > >>> with the release. I am getting %u201CAccess denied" error from the > >>> process: > >>> > >>> # > >>> # List of commands executed for the Maven deploy %u2026. > >>> # > >>> > >>> # Checked out the repo from > >>> https://github.com/apache/incubator-ranger.git > >>> git clone https://github.com/apache/incubator-ranger.git > >>> cd incubator-ranger > >>> # Switched to tags/ranger-0.6.0-rc1 > >>> git checkout tags/ranger-0.6.0-rc1 > >>> > >>> # Run command to stage/deploy the binary to Apache Release folder > >>> > >>> mvn clean package deploy > >>> > >>> > >>> > >>> %u2026. > >>> > >>> > >>> > >>> [ERROR] Failed to execute goal > >>> org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy > >>> (default-deploy) on project ranger: Failed to deploy artifacts: > >>> Could not transfer artifact org.apache.ranger:ranger:pom:0.6.0 > >>> from/to apache.staging.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/ranger/ranger/0.6.0/ranger-0.6.0.pom > >>> . > >>> > >>> Return code is: 401, ReasonPhrase: Unauthorized. -> [Help 1] > >>> > >>> > >>> Can someone help me to fix this issue asap ? Also, I would like to > >>> understand the process and permission required to do the binary > >>> release ? > >>> > >>> Thanks, > >>> Selva- > >>> > >>> > >>> > >>> > >>> > >>> > > > -- > Colm O hEigeartaigh > > Talend Community Coder > http://coders.talend.com > > > > > > -- > Colm O hEigeartaigh > > Talend Community Coder > http://coders.talend.com > > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
