[jira] [Commented] (SLING-5777) Stop embedding oak-jcr in the o.a.s.jcr.oak.server bundle

[ https://issues.apache.org/jira/browse/SLING-5777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15325293#comment-15325293 ] Oliver Lietz commented on SLING-5777: - Bootstrap ITs are successful on Jenkins also. > Stop embedding

[jira] [Commented] (SLING-5520) Update Oak to 1.4

[ https://issues.apache.org/jira/browse/SLING-5520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15325283#comment-15325283 ] Oliver Lietz commented on SLING-5520: - That doesn't look nice, but as long the repository shuts down

[jira] [Comment Edited] (SLING-5511) Adjust Oak package imports

[ https://issues.apache.org/jira/browse/SLING-5511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15325234#comment-15325234 ] Oliver Lietz edited comment on SLING-5511 at 6/10/16 8:30 PM: -- [~rombert], I

[jira] [Resolved] (SLING-5511) Adjust Oak package imports

[ https://issues.apache.org/jira/browse/SLING-5511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz resolved SLING-5511. - Resolution: Done > Adjust Oak package imports > -- > >

[jira] [Commented] (SLING-5511) Adjust Oak package imports

[ https://issues.apache.org/jira/browse/SLING-5511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15325234#comment-15325234 ] Oliver Lietz commented on SLING-5511: - [~rombert], I didn't encounter any issues related to package

[jira] [Assigned] (SLING-5511) Adjust Oak package imports

[ https://issues.apache.org/jira/browse/SLING-5511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz reassigned SLING-5511: --- Assignee: Oliver Lietz > Adjust Oak package imports > -- > >

[jira] [Commented] (SLING-5777) Stop embedding oak-jcr in the o.a.s.jcr.oak.server bundle

[ https://issues.apache.org/jira/browse/SLING-5777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15325198#comment-15325198 ] Oliver Lietz commented on SLING-5777: - [~rombert], Bootstrap ITs are successful here: {noformat}

[jira] [Closed] (SLING-5780) Remove org.apache.sling.auth.openid from build

[ https://issues.apache.org/jira/browse/SLING-5780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz closed SLING-5780. --- > Remove org.apache.sling.auth.openid from build > -- > >

[jira] [Resolved] (SLING-5780) Remove org.apache.sling.auth.openid from build

[ https://issues.apache.org/jira/browse/SLING-5780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz resolved SLING-5780. - Resolution: Done [r1747788|https://svn.apache.org/r1747788] > Remove

[jira] [Created] (SLING-5780) Remove org.apache.sling.auth.openid from build

Oliver Lietz created SLING-5780: --- Summary: Remove org.apache.sling.auth.openid from build Key: SLING-5780 URL: https://issues.apache.org/jira/browse/SLING-5780 Project: Sling Issue Type: Task

[jira] [Updated] (SLING-5776) Update to Oak 1.5.3

[ https://issues.apache.org/jira/browse/SLING-5776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz updated SLING-5776: Issue Type: Improvement (was: Bug) > Update to Oak 1.5.3 > --- > >

[jira] [Commented] (SLING-5776) Update to Oak 1.5.3

[ https://issues.apache.org/jira/browse/SLING-5776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15325108#comment-15325108 ] Oliver Lietz commented on SLING-5776: - Looks good, [~rombert]. Thanks. Test added for bundle

[jira] [Updated] (SLING-5776) Update to Oak 1.5.3

[ https://issues.apache.org/jira/browse/SLING-5776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz updated SLING-5776: Fix Version/s: Launchpad Builder 9 Launchpad Karaf Integration Tests 0.2.0

Re: Scripts, docs and locations

On Friday 10 June 2016 14:51:43 Robert Munteanu wrote: > Hi, Hi Robert, > We have a couple of scripts in the root folder: > > - modules.py > - update_dependencies.sh - check_release_matches_tag.sh - check_staged_release.sh > > As they are not frequently used, I suggest we move them to >

[jira] [Updated] (SLING-5779) LuceneIndexProviderService is sometimes not configured

[ https://issues.apache.org/jira/browse/SLING-5779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-5779: --- Summary: LuceneIndexProviderService is sometimes not configured (was:

[jira] [Created] (SLING-5779) LuceneIndexProviderService sometimes is not configured

Robert Munteanu created SLING-5779: -- Summary: LuceneIndexProviderService sometimes is not configured Key: SLING-5779 URL: https://issues.apache.org/jira/browse/SLING-5779 Project: Sling

[jira] [Updated] (SLING-5779) LuceneIndexProviderService is sometimes not configured

[ https://issues.apache.org/jira/browse/SLING-5779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-5779: --- Attachment: stdout.log.gz error.log.gz > LuceneIndexProviderService is

[jira] [Resolved] (SLING-5778) o.a.s.repoinit.oak-jcr does not start due to missing org.apache.sling.provisioning.model package

[ https://issues.apache.org/jira/browse/SLING-5778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-5778. Resolution: Fixed Fixed in [r1747733|https://svn.apache.org/r1747733] >

Re: Resource.getParent() on NonExistingResource

I am talking about https://github.com/apache/sling/blob/c9e59667d8f9cd698bc33a51f3e6a22e85d4a952/bundles/scripting/sightly/engine/src/main/java/org/apache/sling/scripting/sightly/impl/engine/extension/ResourceRuntimeExtension.java#L254

[jira] [Created] (SLING-5778) o.a.s.repoinit.oak-jcr does not start due to missing org.apache.sling.provisioning.model package

Robert Munteanu created SLING-5778: -- Summary: o.a.s.repoinit.oak-jcr does not start due to missing org.apache.sling.provisioning.model package Key: SLING-5778 URL:

Re: Resource.getParent() on NonExistingResource

I only propose to change getParent() on NonExistingResource. Right now we have the situation that getParent() would just return the wrong NonExistingResource! So what we could do is to rely on resolve() as a fallback in case the regular way does not succeed. That would not make things any worse

Re: Resource.getParent() on NonExistingResource

Regardless of what other problem may exist; involving resolve() in getParent() isn't a solution. Resolve() operates on _URI_ paths. Not on resource paths. So proposing to involve resolve() in an implementation of getParent() doesn't make sense. Resolve() makes special considerations of some

[jira] [Commented] (SLING-5520) Update Oak to 1.4

[ https://issues.apache.org/jira/browse/SLING-5520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15324499#comment-15324499 ] Robert Munteanu commented on SLING-5520: [~olli] - the Repository is still reconfigured/restarted

RE: [VOTE] Release Apache Sling Testing JCR Mock 1.1.14, OSGi Mock 2.0.4, ResourceResolver Mock 1.1.14

+1

[jira] [Resolved] (SLING-5777) Stop embedding oak-jcr in the o.a.s.jcr.oak.server bundle

[ https://issues.apache.org/jira/browse/SLING-5777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-5777. Resolution: Fixed Fixed in [r1747710|https://svn.apache.org/r1747710] [~olli] - I updated

[jira] [Comment Edited] (SLING-5770) Allow to configure resource resolver mapping

[ https://issues.apache.org/jira/browse/SLING-5770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15324330#comment-15324330 ] Konrad Windszus edited comment on SLING-5770 at 6/10/16 1:46 PM: - For that

[jira] [Comment Edited] (SLING-5520) Update Oak to 1.4

[ https://issues.apache.org/jira/browse/SLING-5520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15324375#comment-15324375 ] Robert Munteanu edited comment on SLING-5520 at 6/10/16 1:44 PM: -

[jira] [Commented] (SLING-5520) Update Oak to 1.4

[ https://issues.apache.org/jira/browse/SLING-5520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15324466#comment-15324466 ] Robert Munteanu commented on SLING-5520: I am not sure about that, but I can try later :-) and

Re: [VOTE] Release Apache Sling Testing JCR Mock 1.1.14, OSGi Mock 2.0.4, ResourceResolver Mock 1.1.14

+1 -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org

Re: [VOTE] Release Apache Sling Testing JCR Mock 1.1.14, OSGi Mock 2.0.4, ResourceResolver Mock 1.1.14

On Fri, 2016-06-10 at 12:24 +, Stefan Seifert wrote: > Please vote to approve this release: +1 Robert signature.asc Description: This is a digitally signed message part

[jira] [Commented] (SLING-5520) Update Oak to 1.4

[ https://issues.apache.org/jira/browse/SLING-5520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15324375#comment-15324375 ] Robert Munteanu commented on SLING-5520: {quote}There is still use of deprecated Oak API in

[jira] [Commented] (SLING-5520) Update Oak to 1.4

[ https://issues.apache.org/jira/browse/SLING-5520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15324373#comment-15324373 ] Oliver Lietz commented on SLING-5520: - Do we still need start levels for setting up Oak properly

[jira] [Commented] (SLING-5520) Update Oak to 1.4

[ https://issues.apache.org/jira/browse/SLING-5520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15324371#comment-15324371 ] Oliver Lietz commented on SLING-5520: - There is still use of deprecated Oak API in

[VOTE] Release Apache Sling Testing JCR Mock 1.1.14, OSGi Mock 2.0.4, ResourceResolver Mock 1.1.14

Hi, We solved issues in this releases: Apache Sling Testing JCR Mock 1.1.14 (2 issues) https://issues.apache.org/jira/browse/SLING/fixforversion/12334801 Apache Sling Testing OSGi Mock 2.0.4 (2 issues) https://issues.apache.org/jira/browse/SLING/fixforversion/12334799 Apache Sling Testing

Merging oak-server and it-jackrabbit-oak

Hi, Right now we have the oak glue code located in bundles/jcr/jackrabbit- oak and the ITs for the oak integration located in bundles/jcr/it- jackrabbit-oak. This makes updating Oak a bit harder since: - you have to update the oak version in both the bundles and the ITs - you have to build and

[jira] [Created] (SLING-5777) Stop embedding oak-jcr in the o.a.s.jcr.oak.server bundle

Robert Munteanu created SLING-5777: -- Summary: Stop embedding oak-jcr in the o.a.s.jcr.oak.server bundle Key: SLING-5777 URL: https://issues.apache.org/jira/browse/SLING-5777 Project: Sling

[jira] [Commented] (SLING-5511) Adjust Oak package imports

[ https://issues.apache.org/jira/browse/SLING-5511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15324350#comment-15324350 ] Robert Munteanu commented on SLING-5511: [~olli] - is there anything left to be done here? >

[jira] [Resolved] (SLING-5776) Update to Oak 1.5.3

[ https://issues.apache.org/jira/browse/SLING-5776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-5776. Resolution: Fixed Fixed in [r1747690|https://svn.apache.org/r1747690]: -

[jira] [Created] (SLING-5776) Update to Oak 1.5.3

Robert Munteanu created SLING-5776: -- Summary: Update to Oak 1.5.3 Key: SLING-5776 URL: https://issues.apache.org/jira/browse/SLING-5776 Project: Sling Issue Type: Bug Components:

Re: Release of Testing ResourceResolverMock

Perfect, thanks. Konrad > On 10 Jun 2016, at 13:48, Stefan Seifert wrote: > > i will do the release as i want to release some of the other mock libs as > well today. > > stefan > > >> -Original Message- >> From: Konrad Windszus [mailto:konra...@gmx.de] >>

[jira] [Updated] (SLING-5478) Implement MockNode methods regarding mixin, reordering and move

[ https://issues.apache.org/jira/browse/SLING-5478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert updated SLING-5478: -- Assignee: (was: Stefan Seifert) Fix Version/s: (was: Testing JCR Mock 1.1.14)

Scripts, docs and locations

Hi, We have a couple of scripts in the root folder: - modules.py - update_dependencies.sh As they are not frequently used, I suggest we move them to 'tooling/release' or maybe 'tooling/scm' if appropriate. Also, I'm not sure how to use update_dependencies.sh, there are no docs for it and

[jira] [Commented] (SLING-5770) Allow to configure resource resolver mapping

[ https://issues.apache.org/jira/browse/SLING-5770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15324330#comment-15324330 ] Konrad Windszus commented on SLING-5770: For that I need to implement my own custom context, I

[jira] [Commented] (SLING-5520) Update Oak to 1.4

[ https://issues.apache.org/jira/browse/SLING-5520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15324329#comment-15324329 ] Robert Munteanu commented on SLING-5520: [~olli] - any more changes to be done here? I'd like to

RE: Release of Testing ResourceResolverMock

i will do the release as i want to release some of the other mock libs as well today. stefan >-Original Message- >From: Konrad Windszus [mailto:konra...@gmx.de] >Sent: Thursday, June 09, 2016 10:18 AM >To: dev@sling.apache.org >Subject: Release of Testing ResourceResolverMock > >I

[jira] [Commented] (SLING-5770) Allow to configure resource resolver mapping

[ https://issues.apache.org/jira/browse/SLING-5770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15324319#comment-15324319 ] Stefan Seifert commented on SLING-5770: --- if you do the same as in AemContextImpl and overwrite the

[jira] [Resolved] (SLING-5775) jcr-mock: Support PropertyDefinition flags

[ https://issues.apache.org/jira/browse/SLING-5775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert resolved SLING-5775. --- Resolution: Fixed Completed: At revision: 1747678 > jcr-mock: Support PropertyDefinition

[jira] [Created] (SLING-5775) jcr-mock: Support PropertyDefinition flags

Stefan Seifert created SLING-5775: - Summary: jcr-mock: Support PropertyDefinition flags Key: SLING-5775 URL: https://issues.apache.org/jira/browse/SLING-5775 Project: Sling Issue Type:

[jira] [Resolved] (SLING-5774) jcr-mock: Support Node.getMixinNodeTypes

[ https://issues.apache.org/jira/browse/SLING-5774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert resolved SLING-5774. --- Resolution: Fixed Completed: At revision: 1747677 > jcr-mock: Support

[jira] [Created] (SLING-5774) jcr-mock: Support Node.getMixinNodeTypes

Stefan Seifert created SLING-5774: - Summary: jcr-mock: Support Node.getMixinNodeTypes Key: SLING-5774 URL: https://issues.apache.org/jira/browse/SLING-5774 Project: Sling Issue Type:

[jira] [Commented] (SLING-5629) redirectAfterLogout prepends servlet context to the target, when it's already there

[ https://issues.apache.org/jira/browse/SLING-5629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15324173#comment-15324173 ] ASF GitHub Bot commented on SLING-5629: --- Github user glucazeau closed the pull request at:

[GitHub] sling pull request #132: SLING-5629: do not prepend servlet context path on ...

Github user glucazeau closed the pull request at: https://github.com/apache/sling/pull/132 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Commented] (SLING-5461) Sightly quotes all markup attributes' values with double quotes

[ https://issues.apache.org/jira/browse/SLING-5461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15324161#comment-15324161 ] Radu Cotescu commented on SLING-5461: - Please open a separate issue (as this one is closed) and try to

[jira] [Closed] (SLING-5738) Add support for configuring a pattern for the model files to be read

[ https://issues.apache.org/jira/browse/SLING-5738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-5738. --- > Add support for configuring a pattern for the model files to be read >

[jira] [Closed] (SLING-5765) No way to remove an artifact from a special runmode

[ https://issues.apache.org/jira/browse/SLING-5765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-5765. --- > No way to remove an artifact from a special runmode >

[VOTE RESULT] Release Apache Sling Provisioning Model 1.4.4 and Apache Sling Slingstart Maven Plugin 1.4.4

The vote passes with three binding +1 votes Thanks Carsten -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org

Re: Resource.getParent() on NonExistingResource

Konrad Windszus wrote > My use case is AEM: > I have an existing page containing some components (each one encapsulated in > dedicated child resources). > Now the underlying template in AEM is extended (i.e. new fixed components > have been added). For each of those a child resource is

Re: svn commit: r1747400 - /sling/trunk/testing/http/clients/src/test/java/org/apache/sling/testing/DelayRequestInterceptorTest.java

Hi Robert, That's a unit test for the sling http testing clients themselves and I only made that change to test my svn rights :) But thanks for pointing that out, I'll make sure to use the timeoutsprovider wherever there's a sleep in the tooling. Thanks. On Thu, Jun 9, 2016 at 2:53 PM Robert

Re: Resource.getParent() on NonExistingResource

My use case is AEM: I have an existing page containing some components (each one encapsulated in dedicated child resources). Now the underlying template in AEM is extended (i.e. new fixed components have been added). For each of those a child resource is necessary, which does not exist yet on

Re: Resource.getParent() on NonExistingResource

On 10.6.16 9:26 , Carsten Ziegeler wrote: I think calling resolve() for traversal is totally unexpected. Now looking at this, I'm really wondering if it was a good idea to implement getParent on NonExistingResource. Let the client deal with it instead of adding complex special cases. FWIW:

Re: Resource.getParent() on NonExistingResource

Konrad Windszus wrote > This is complex to solve for the client (and kind of unexpected that this is > not working). > So what speaks against supporting this use case properly in Sling. > Maybe you can elaborate a bit on >> I think calling resolve() for traversal is totally unexpected. > > IMHO

Re: Resource.getParent() on NonExistingResource

This is complex to solve for the client (and kind of unexpected that this is not working). So what speaks against supporting this use case properly in Sling. Maybe you can elaborate a bit on > I think calling resolve() for traversal is totally unexpected. IMHO the complex cases should be nicely

Re: Resource.getParent() on NonExistingResource

I think calling resolve() for traversal is totally unexpected. Now looking at this, I'm really wondering if it was a good idea to implement getParent on NonExistingResource. Let the client deal with it instead of adding complex special cases. Carsten Konrad Windszus wrote > There is one related

[jira] [Created] (SLING-5773) NonExistingResource.getParent() must consider the resource resolver mapping

Konrad Windszus created SLING-5773: -- Summary: NonExistingResource.getParent() must consider the resource resolver mapping Key: SLING-5773 URL: https://issues.apache.org/jira/browse/SLING-5773

Re: Resource.getParent() on NonExistingResource

There is one related problem with mapping: Consider the case you have a resource resolver mapping from "/content/" to "/". In the underlying repository you have a resource in "/content/existingParent". Now it might happen that a NonExistingResource is resolved for path