Re: New release branch 2.0.0

I think it should be "apache.releases.https" based on the error message below. I have both in my local settings.xml, so you could try adding both in! Colm. On Tue, Nov 28, 2017 at 4:41 PM, Sergio Pena wrote: > I have the same issue. > > Colm, the wiki mentioned

Re: New release branch 2.0.0

Hmm I'm not sure if that's correct, it should look more like: apache.releases.https coheigea ... apache.staging.https coheigea ... On Tue, Nov 28, 2017 at 5:02 PM, Kalyan Kumar Kalvagadda < kkal...@cloudera.com>

Re: New release branch 2.0.0

Colm, that is the issue. I will update the wiki accordingly. -Kalyan On Tue, Nov 28, 2017 at 11:11 AM, Colm O hEigeartaigh wrote: > Hmm I'm not sure if that's correct, it should look more like: > > > > > >apache.releases.https >coheigea >

Re: New release branch 2.0.0

I have the same issue. Colm, the wiki mentioned "apache.staging.https". is that the correct one? On Tue, Nov 28, 2017 at 10:14 AM, Colm O hEigeartaigh wrote: > Have you got a "apache.releases.https" server defined in your maven > settings.xml, with a corresponding username

Re: New release branch 2.0.0

Colm, This the the complete content of my settings.xml. > > > > apache.staging.https > > kalyan > > * > >apache.releases.https > > kalyan > > * > > > > I'm running below command. > mvn -s ~/.m2/settings.xml clean deploy -Psign-artifacts I still observe the

Re: New release branch 2.0.0

Have you got a "apache.releases.https" server defined in your maven settings.xml, with a corresponding username + password? Colm. On Tue, Nov 28, 2017 at 4:11 PM, Kalyan Kumar Kalvagadda < kkal...@cloudera.com> wrote: > I'm observing error while deploying the artifacts in maven repository. >

Re: New release branch 2.0.0

I'm observing error while deploying the artifacts in maven repository. Looks like I don't have permission to do it. [ERROR] Failed to execute goal org.apache.maven.plugins: > maven-deploy-plugin:2.8.2:deploy (default-deploy) on project sentry: > Failed to deploy artifacts: Could not transfer

2.0 release and SENTRY-1812

Colm, do you plan to include SENTRY-1812 in 2.0 release?

Re: 2.0 release and SENTRY-1812

Yes, it's already merged and the Jira is resolved. Colm. On 28 Nov 2017 7:04 p.m., "Alexander Kolbasov" wrote: Colm, do you plan to include SENTRY-1812 in 2.0 release?

Re: Review Request 63596: SENTRY-1951 - Old SentryStore.retrieveFullPathsImage() should be removed

> On Nov. 28, 2017, 10:16 p.m., Vadim Spector wrote: > > sentry-provider/sentry-provider-db/src/test/java/org/apache/sentry/provider/db/service/persistent/TestSentryStore.java > > Line 2514 (original), 2513 (patched) > >

Re: Review Request 63596: SENTRY-1951 - Old SentryStore.retrieveFullPathsImage() should be removed

> On Nov. 28, 2017, 10:16 p.m., Vadim Spector wrote: > > sentry-provider/sentry-provider-db/src/test/java/org/apache/sentry/provider/db/service/persistent/TestSentryStore.java > > Line 2514 (original), 2513 (patched) > >

Re: Review Request 63596: SENTRY-1951 - Old SentryStore.retrieveFullPathsImage() should be removed

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/63596/#review192068 ---

Re: Review Request 63596: SENTRY-1951 - Old SentryStore.retrieveFullPathsImage() should be removed

> On Nov. 28, 2017, 10:16 p.m., Vadim Spector wrote: > > sentry-provider/sentry-provider-db/src/test/java/org/apache/sentry/provider/db/service/persistent/TestSentryStore.java > > Line 2514 (original), 2513 (patched) > >

[VOTE] Release Sentry version 2.0.0

This is the release of Apache Sentry, version 2.0.0. It fixes the following issues: *https://issues.apache.org/jira/projects/SENTRY/versions/12341081 * Source and bin files :