[jira] [Created] (SLING-5206) Create tests for all new features/handling

Carsten Ziegeler created SLING-5206: --- Summary: Create tests for all new features/handling Key: SLING-5206 URL: https://issues.apache.org/jira/browse/SLING-5206 Project: Sling Issue Type: Su

[jira] [Created] (SLING-5205) Check for potential memory leaks

Carsten Ziegeler created SLING-5205: --- Summary: Check for potential memory leaks Key: SLING-5205 URL: https://issues.apache.org/jira/browse/SLING-5205 Project: Sling Issue Type: Sub-task

[jira] [Updated] (SLING-5201) Improve resource provider resolving

[ https://issues.apache.org/jira/browse/SLING-5201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-5201: Issue Type: Sub-task (was: Improvement) Parent: SLING-4750 > Improve resource provi

[jira] [Created] (SLING-5204) Implement provider lifecycle methods

Carsten Ziegeler created SLING-5204: --- Summary: Implement provider lifecycle methods Key: SLING-5204 URL: https://issues.apache.org/jira/browse/SLING-5204 Project: Sling Issue Type: Sub-task

[jira] [Assigned] (SLING-5201) Improve resource provider resolving

[ https://issues.apache.org/jira/browse/SLING-5201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned SLING-5201: --- Assignee: Carsten Ziegeler > Improve resource provider resolving > --

[RESULT] [VOTE] Release Apache Sling Rewriter 1.1.2

Hi, The vote has passed with the following result : +1 (binding): Justin Edelson, Stefan Seifert, Setfan Egli, Robert Munteau, and Oliver Lietz I will copy this release to the Sling dist directory and promote the artifacts to the central Maven repository. On Mon, Oct 19, 2015 at 11:50 AM Justin

[jira] [Created] (SLING-5203) Move integration tests to Oak

Carsten Ziegeler created SLING-5203: --- Summary: Move integration tests to Oak Key: SLING-5203 URL: https://issues.apache.org/jira/browse/SLING-5203 Project: Sling Issue Type: Improvement

[jira] [Commented] (SLING-5201) Improve resource provider resolving

[ https://issues.apache.org/jira/browse/SLING-5201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14976413#comment-14976413 ] Carsten Ziegeler commented on SLING-5201: - Updated jcr resource in 1710815 and res

[jira] [Commented] (SLING-5201) Improve resource provider resolving

[ https://issues.apache.org/jira/browse/SLING-5201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14976381#comment-14976381 ] Carsten Ziegeler commented on SLING-5201: - Updated resource resolver implementatio

[jira] [Comment Edited] (SLING-5201) Improve resource provider resolving

[ https://issues.apache.org/jira/browse/SLING-5201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14976301#comment-14976301 ] Carsten Ziegeler edited comment on SLING-5201 at 10/27/15 1:35 PM: -

[jira] [Commented] (SLING-5201) Improve resource provider resolving

[ https://issues.apache.org/jira/browse/SLING-5201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14976301#comment-14976301 ] Carsten Ziegeler commented on SLING-5201: - I refactored the API in rev 1710797: -

Re: Trunk not building - Sightly Performance tests fail

Applied the change in https://svn.apache.org/viewvc?view=revision&revision=r1710785. On Tue, 27 Oct 2015 at 12:27 Radu Cotescu wrote: > Hi Carsten, > > We should probably _temporarily_ increase the threshold for the Sling > Models Sightly performance test, although the proper fix would be improv

Re: Trunk not building - Sightly Performance tests fail

Hi Carsten, We should probably _temporarily_ increase the threshold for the Sling Models Sightly performance test, although the proper fix would be improving how Sling Models are initialised. The reflection code we have now is not optimal. Cheers, Radu On Tue, 27 Oct 2015 at 09:58 Carsten Ziegel

[jira] [Commented] (SLING-5006) Allow to enable the usage of regular JCR users for service resolvers

[ https://issues.apache.org/jira/browse/SLING-5006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14976236#comment-14976236 ] Marius Petria commented on SLING-5006: -- yes > Allow to enable the usage of regular J

Re: [RT] Observation events

See GlobbingPathFilter [1] for how globbing on paths works. Note, that that there is no globbing on the elements of a path (yet). Michael [1] https://github.com/apache/jackrabbit-oak/blob/6a7c413ba69663bdf6b15e7aab211089f76da056/oak-core/src/main/java/org/apache/jackrabbit/oak/plugins/obser

Re: [RT] Observation events

Thanks Michael, so from that list, from a Sling perspective globbing seems to be the interesting part for me. Node types are not sufficient as we would need to filter on resource types, and that can become really tricky due to the type inheritance we have. So if no one complains I'll add globbing

Re: [RT] Observation events

See my reply to Bertrand on 19.10.15 for an overview. Regarding capabilities, Oak's filtering mechanism allows filtering by node type, by paths (including some globbing), by access control and by visibility (internal Oak nodes). It has additional support for filtering events of sub trees of a

[jira] [Comment Edited] (SLING-920) Sling Jenkins setup

[ https://issues.apache.org/jira/browse/SLING-920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14976207#comment-14976207 ] Robert Munteanu edited comment on SLING-920 at 10/27/15 10:42 AM: ---

[jira] [Commented] (SLING-920) Sling Jenkins setup

[ https://issues.apache.org/jira/browse/SLING-920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14976207#comment-14976207 ] Robert Munteanu commented on SLING-920: --- Removed 'Build periodically' from sling-tool

[jira] [Created] (SLING-5202) Use new resource API for querying and copy/move

Carsten Ziegeler created SLING-5202: --- Summary: Use new resource API for querying and copy/move Key: SLING-5202 URL: https://issues.apache.org/jira/browse/SLING-5202 Project: Sling Issue Typ

[jira] [Commented] (SLING-5201) Improve resource provider resolving

[ https://issues.apache.org/jira/browse/SLING-5201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14976193#comment-14976193 ] Carsten Ziegeler commented on SLING-5201: - ResolveContext is actually not that "st

[jira] [Resolved] (SLING-5188) Some WebConsole plugins are placed in the 'main' category

[ https://issues.apache.org/jira/browse/SLING-5188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-5188. Resolution: Fixed > Some WebConsole plugins are placed in the 'main' category >

[jira] [Commented] (SLING-5201) Improve resource provider resolving

[ https://issues.apache.org/jira/browse/SLING-5201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14976105#comment-14976105 ] Carsten Ziegeler commented on SLING-5201: - I'm not 100% sure but I think the list

[jira] [Updated] (SLING-5201) Improve resource provider resolving

[ https://issues.apache.org/jira/browse/SLING-5201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-5201: Fix Version/s: API 2.10.0 > Improve resource provider resolving > --

Re: [RT] Observation events

Am 27.10.15 um 10:23 schrieb Stefan Egli: > This is probably stating the obvious, but the resource-name-filter should > be compatible with oak's filter capabilities (OAK-1133) > Or a subset. It would be great, if someone can summarize those capabilities here. Thanks Carsten > Cheers, > Stefan >

[jira] [Created] (SLING-5201) Improve resource provider resolving

Carsten Ziegeler created SLING-5201: --- Summary: Improve resource provider resolving Key: SLING-5201 URL: https://issues.apache.org/jira/browse/SLING-5201 Project: Sling Issue Type: Improveme

Re: [RT] Observation events

This is probably stating the obvious, but the resource-name-filter should be compatible with oak's filter capabilities (OAK-1133) Cheers, Stefan On 27/10/15 10:11, "Carsten Ziegeler" wrote: >Continuing this discussion, right now the resource listeners can >subscribe to a path and a change type

[jira] [Commented] (SLING-5196) missing dependency when using maven-bundle-plugin 3.0.0 in discovery.base and discovery.impl

[ https://issues.apache.org/jira/browse/SLING-5196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14976064#comment-14976064 ] Stefan Egli commented on SLING-5196: thx! > missing dependency when using maven-bundl

[jira] [Created] (SLING-5200) introduce simulation of repository delays in discovery tests

Stefan Egli created SLING-5200: -- Summary: introduce simulation of repository delays in discovery tests Key: SLING-5200 URL: https://issues.apache.org/jira/browse/SLING-5200 Project: Sling Issue

Re: [RT] Observation events

Continuing this discussion, right now the resource listeners can subscribe to a path and a change type (added/changed/removed). I think a pretty common use case is to filter on the resource name, all script implementations that cache, filter on the script extension. Should we support this for reg

[jira] [Commented] (SLING-5188) Some WebConsole plugins are placed in the 'main' category

[ https://issues.apache.org/jira/browse/SLING-5188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14976054#comment-14976054 ] Carsten Ziegeler commented on SLING-5188: - Yes, thanks > Some WebConsole plugins

Trunk not building - Sightly Performance tests fail

Hi, when building trunk I repeatedly get a test failure in the sightly.testing module. Can this please be fixed? test5SlyJavaSlingModels(org.apache.sling.scripting.sightly.it.performance.PerformanceIT) Time elapsed: 9.086 sec <<< ERROR! java.lang.Exception: Threshold exceeded! Expected < 2,00,

[jira] [Commented] (SLING-5196) missing dependency when using maven-bundle-plugin 3.0.0 in discovery.base and discovery.impl

[ https://issues.apache.org/jira/browse/SLING-5196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14976043#comment-14976043 ] Robert Munteanu commented on SLING-5196: I think we can't use the maven-bundle-plu

[jira] [Commented] (SLING-5188) Some WebConsole plugins are placed in the 'main' category

[ https://issues.apache.org/jira/browse/SLING-5188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14976041#comment-14976041 ] Stefan Egli commented on SLING-5188: from my pov yes > Some WebConsole plugins are pl

[jira] [Created] (SLING-5199) Remove the maven-bundle-plugin override once version 3.0.2 is available

Robert Munteanu created SLING-5199: -- Summary: Remove the maven-bundle-plugin override once version 3.0.2 is available Key: SLING-5199 URL: https://issues.apache.org/jira/browse/SLING-5199 Project: Sl

[jira] [Commented] (SLING-5188) Some WebConsole plugins are placed in the 'main' category

[ https://issues.apache.org/jira/browse/SLING-5188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14976033#comment-14976033 ] Robert Munteanu commented on SLING-5188: Can this be resolved then? I don't think

[jira] [Reopened] (SLING-5006) Allow to enable the usage of regular JCR users for service resolvers

[ https://issues.apache.org/jira/browse/SLING-5006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reopened SLING-5006: - [~mpetria] Which means we should reopen this issue and reapply the sync improvements, right?

[jira] [Updated] (SLING-4895) Service registry should not be called from within synchronized block

[ https://issues.apache.org/jira/browse/SLING-4895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-4895: Assignee: Marius Petria > Service registry should not be called from within synchronized blo

Re: [VOTE] Release Apache Sling Discovery Commons 1.0.0, Discovery Base 1.0.0, Discovery Oak 1.0.0

On 26/10/15 23:06, "Stefan Seifert" wrote: >+1 > > >p.s. i updated the discovery version to next development snapshot until >the releases are available in maven central Thx Stefan, missed that one.. Cheers, Stefan > > >>-Original Message- >>From: Stefan Egli [mailto:stefane...@apache.

[jira] [Comment Edited] (SLING-5006) Allow to enable the usage of regular JCR users for service resolvers

[ https://issues.apache.org/jira/browse/SLING-5006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14975912#comment-14975912 ] Marius Petria edited comment on SLING-5006 at 10/27/15 7:59 AM:

[jira] [Commented] (SLING-5006) Allow to enable the usage of regular JCR users for service resolvers

[ https://issues.apache.org/jira/browse/SLING-5006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14975912#comment-14975912 ] Marius Petria commented on SLING-5006: -- [~kwin] [~cziegeler] I first apologize that I