Re: Support for ACE Restrictions with jackrabbit.accessmanager REST

2018-12-11 Thread Robert Munteanu
On Thu, 2018-12-06 at 20:56 -0800, Eric Norman wrote:
> Hi Robert,
> 
> Ok, I will give it a try.  Please advise if I mess something up.
> 
> Regards,
> Eric

Everything turned up fine from the first try, that's nice!

Robert

> 
> On Mon, Dec 3, 2018 at 1:39 AM Robert Munteanu 
> wrote:
> 
> > Hi Eric,
> > 
> > On Tue, 2018-11-27 at 17:10 -0800, Eric Norman wrote:
> > > Would someone be able to review the changes done for those issues
> > > and
> > > if
> > > there are no objections to the code changes assist with releasing
> > > those two
> > > bundles?  I've never done that before and I not sure I even have
> > > sufficient
> > > rights to do it.
> > 
> > As a committer you are able to start a release vote, you only need
> > a
> > PMC member at the end to promote the artifacts to dist.apache.org ,
> > see
> > [1] for more details.
> > 
> > In case you would like someone else to run the release feel free to
> > ask
> > when ready, but I would suggest to try it yourself since you have
> > sufficient rights.
> > 
> > Thanks,
> > 
> > Robert
> > 
> > [1]:
> > http://sling.apache.org/documentation/development/release-management.html
> > 
> > 




Re: Support for ACE Restrictions with jackrabbit.accessmanager REST

2018-12-06 Thread Eric Norman
Hi Robert,

Ok, I will give it a try.  Please advise if I mess something up.

Regards,
Eric

On Mon, Dec 3, 2018 at 1:39 AM Robert Munteanu  wrote:

> Hi Eric,
>
> On Tue, 2018-11-27 at 17:10 -0800, Eric Norman wrote:
> > Would someone be able to review the changes done for those issues and
> > if
> > there are no objections to the code changes assist with releasing
> > those two
> > bundles?  I've never done that before and I not sure I even have
> > sufficient
> > rights to do it.
>
> As a committer you are able to start a release vote, you only need a
> PMC member at the end to promote the artifacts to dist.apache.org , see
> [1] for more details.
>
> In case you would like someone else to run the release feel free to ask
> when ready, but I would suggest to try it yourself since you have
> sufficient rights.
>
> Thanks,
>
> Robert
>
> [1]:
> http://sling.apache.org/documentation/development/release-management.html
>
>


Re: Support for ACE Restrictions with jackrabbit.accessmanager REST

2018-12-03 Thread Robert Munteanu
Hi Eric,

On Tue, 2018-11-27 at 17:10 -0800, Eric Norman wrote:
> Would someone be able to review the changes done for those issues and
> if
> there are no objections to the code changes assist with releasing
> those two
> bundles?  I've never done that before and I not sure I even have
> sufficient
> rights to do it.

As a committer you are able to start a release vote, you only need a
PMC member at the end to promote the artifacts to dist.apache.org , see
[1] for more details.

In case you would like someone else to run the release feel free to ask
when ready, but I would suggest to try it yourself since you have
sufficient rights.

Thanks,

Robert

[1]: http://sling.apache.org/documentation/development/release-management.html



Support for ACE Restrictions with jackrabbit.accessmanager REST

2018-11-27 Thread Eric Norman
Hey all,

I've been doing some work to try to solve the issue reported in the thread
at [1] and tracked as SLING-8117


   1.
   
https://lists.apache.org/thread.html/bb7c9bede0274969f4e7c2363a40ebd6d7ee783536ae02ca5642590d@%3Cusers.sling.apache.org%3E


I have a solution working locally and some new unit tests to verify it
works.

I've committed the changes for the first of two steps with these issues:
SLING-8138  for JCR Base
3.0.6

SLING-8139  for Testing
Sling Mock Oak 2.1.2


Would someone be able to review the changes done for those issues and if
there are no objections to the code changes assist with releasing those two
bundles?  I've never done that before and I not sure I even have sufficient
rights to do it.

Once there are released versions of those two bundles, I can commit the
second part of the solution to resolve the remaining two issues:
- SLING-8117  forJCR
Jackrabbit Access Manager 3.0.4


   1. SLING-8118  forJCR
   ContentLoader 2.3.0
   



And if I understand correctly, I will have to wait for released versions of
all 4 of the above bundles before the new integration tests can be
committed to org.apache.sling.launchpad.integration-tests since the
org.apache.sling.starter project isn't allowed to have SNAPSHOT
dependencies?

I'd be happy to answer any questions if you have them.

Regards,
Eric