[jira] [Updated] (SLING-6939) sling distribution leaks jcr sessions

[ https://issues.apache.org/jira/browse/SLING-6939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Will McGauley updated SLING-6939: - Attachment: SLING_6939.patch > sling distribution leaks jcr sessions >

[jira] [Created] (SLING-6940) JSPC plugin violates Maven naming convention

Tobias Bocanegra created SLING-6940: --- Summary: JSPC plugin violates Maven naming convention Key: SLING-6940 URL: https://issues.apache.org/jira/browse/SLING-6940 Project: Sling Issue Type:

Release: maven-jspc-plugin-2.0.9 ?

Hi, With the fix of [0] the jspc plugin uses the latest sling jsp scripting backend and supports java 1.8. Would it be possible to release it? thanks. regards, toby ps: the plugin violates the maven plugin convention, as it starts with "maven-": --- [INFO] --- maven-plugin-plugin:3.4:helpmojo

[jira] [Commented] (SLING-5763) ClassFormatException when using java 8 lambda expressions

[ https://issues.apache.org/jira/browse/SLING-5763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16040050#comment-16040050 ] Tobias Bocanegra commented on SLING-5763: - [~bobi] I fixed SLING-6923. can you test again if it

[jira] [Commented] (SLING-848) Support getting versioned resources by using uri path parameters

[ https://issues.apache.org/jira/browse/SLING-848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16038277#comment-16038277 ] Julian Reschke commented on SLING-848: -- Out of curiosity: will percent-escaping the semicolon disable

[jira] [Updated] (SLING-6937) Referrer Filter: Allow Path Exclusions

[ https://issues.apache.org/jira/browse/SLING-6937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dominique Jäggi updated SLING-6937: --- Attachment: SLING_6937___Referrer_Filter__Allow_Path_Exclusions.patch > Referrer Filter:

[jira] [Created] (SLING-6937) Referrer Filter: Allow Path Exclusions

Dominique Jäggi created SLING-6937: -- Summary: Referrer Filter: Allow Path Exclusions Key: SLING-6937 URL: https://issues.apache.org/jira/browse/SLING-6937 Project: Sling Issue Type:

[jira] [Commented] (SLING-848) Support getting versioned resources by using uri path parameters

[ https://issues.apache.org/jira/browse/SLING-848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16038406#comment-16038406 ] Tomek Rękawek commented on SLING-848: - [~alexander.klimetschek], according to the discussion in this

Re: [VOTE] Apache Sling JUnit Core 1.0.26, Testing Clients 1.1.0, JUnit Remote Test Runners 1.0.12, Tooling Support Install 1.0.4, Tooling Support Source 1.0.4

+1 (non-binding) On Mon, Jun 5, 2017 at 4:24 PM Carsten Ziegeler wrote: > +1 > > > > -- > Carsten Ziegeler > Adobe Research Switzerland > cziege...@apache.org >

[jira] [Commented] (SLING-6885) Tooling support bundles no longer work due to dependency on org.apache.sling.commons.json

[ https://issues.apache.org/jira/browse/SLING-6885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16038362#comment-16038362 ] Robert Munteanu commented on SLING-6885: No issue from me :-), thanks for the fix [~karlpauls] >

Re: [VOTE] Apache Sling Resource Inventory 1.0.8, Content Distribution Core 0.2.8, Testing Sling Mock 2.2.12, Log Tracer 1.0.4, Commons Metrics 1.2.2

+1 Tommaso Il giorno lun 5 giu 2017 alle ore 16:24 Carsten Ziegeler < cziege...@apache.org> ha scritto: > +1 > > > > -- > Carsten Ziegeler > Adobe Research Switzerland > cziege...@apache.org >

[jira] [Commented] (SLING-848) Support getting versioned resources by using uri path parameters

[ https://issues.apache.org/jira/browse/SLING-848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16038448#comment-16038448 ] Carsten Ziegeler commented on SLING-848: I don't think a configuration would work as this means its

[jira] [Comment Edited] (SLING-848) Support getting versioned resources by using uri path parameters

[ https://issues.apache.org/jira/browse/SLING-848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16038448#comment-16038448 ] Carsten Ziegeler edited comment on SLING-848 at 6/6/17 9:31 AM: I don't

[jira] [Commented] (SLING-848) Support getting versioned resources by using uri path parameters

[ https://issues.apache.org/jira/browse/SLING-848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16038477#comment-16038477 ] Tomek Rękawek commented on SLING-848: - -I like the equals sign idea.- Actually, it works like this

[jira] [Commented] (SLING-848) Support getting versioned resources by using uri path parameters

[ https://issues.apache.org/jira/browse/SLING-848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16038489#comment-16038489 ] Julian Reschke commented on SLING-848: -- Making the semantics of ";" depend on whether it is followed

Re: [RESULT] [VOTE] Apache Sling Resource Inventory 1.0.8, Content Distribution Core 0.2.8, Testing Sling Mock 2.2.12, Log Tracer 1.0.4, Commons Metrics 1.2.2

Time to call the vote on the Apache Sling Resource Inventory 1.0.8, Content Distribution Core 0.2.8, Testing Sling Mock 2.2.12, Log Tracer 1.0.4, and Commons Metrics 1.2.2 releases. * +1 votes from Stefan Seifert, Carsten Ziegeler, Tommaso Teofili, and Karl Pauls. * No other votes. The vote is

Re: [VOTE] Apache Sling JUnit Core 1.0.26, Testing Clients 1.1.0, JUnit Remote Test Runners 1.0.12, Tooling Support Install 1.0.4, Tooling Support Source 1.0.4

+1 regards, Karl On Tue, Jun 6, 2017 at 10:53 AM, Andrei Dulvac wrote: > +1 (non-binding) > > On Mon, Jun 5, 2017 at 4:24 PM Carsten Ziegeler > wrote: >> >> +1 >> >> >> >> -- >> Carsten Ziegeler >> Adobe Research Switzerland >>

[jira] [Updated] (SLING-6866) HTL doesn't allow to overwrite the context for data-sly-text

[ https://issues.apache.org/jira/browse/SLING-6866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu updated SLING-6866: Affects Version/s: Scripting Sightly Engine 1.0.18 > HTL doesn't allow to overwrite the context for

[jira] [Updated] (SLING-6866) HTL doesn't allow to overwrite the context for data-sly-text

[ https://issues.apache.org/jira/browse/SLING-6866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu updated SLING-6866: Description: When using the following expression {code:html} {code} the output is escaped using

[jira] [Resolved] (SLING-6866) HTL doesn't allow to overwrite the context for data-sly-text

[ https://issues.apache.org/jira/browse/SLING-6866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu resolved SLING-6866. - Resolution: Fixed Fixed in [r1797789|https://svn.apache.org/r1797789]. > HTL doesn't allow to

ResultRegistry for Health Checks -> StickyResults instead?

Hi, I 've had a look at SLING-6855 that Clint contributed, and I have a slightly different proposal. The goal is to declare health check results that remain valid for a specified time or forever. For example, a quota has been tripped - warn for 30 minutes. Or an events queue overflowed and the

[jira] [Commented] (SLING-6855) Create ResultRegistry to provide health check behavior for executing code that does not want a HealthCheck

[ https://issues.apache.org/jira/browse/SLING-6855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16038996#comment-16038996 ] Bertrand Delacretaz commented on SLING-6855: Thanks Clint for your pull request! I've had a

Re: [DISCUSS] Remove retired artifacts from the Downloads section and the dist dir

Hi Bertrand, > If people want to de-emphasize them, how about marking them as > on the downloads page, with a note that points to [1] and [2] ? So we would remove them from dist (they still would be in the archive) and move them into a special section on the download page. That would make sense

Re: [DISCUSS] Can we Retire org.apache.sling.jcr.js.nodetypes to the Sling attic?

On Tue, Jun 6, 2017 at 2:39 PM, Bertrand Delacretaz wrote: > On Tue, Jun 6, 2017 at 2:30 PM, Karl Pauls wrote: >> ...it looks like the only consumer of the >> org.apache.sling.jcr.js.nodetypes artifact is the >> org.apache.sling.resource-editor in

[jira] [Resolved] (SLING-6867) Repoinit ACL handler should take aggregate privilege into account

[ https://issues.apache.org/jira/browse/SLING-6867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz resolved SLING-6867. Resolution: Fixed Assignee: Bertrand Delacretaz Thanks for your contribution!

[jira] [Updated] (SLING-6867) Repoinit ACL handler should take aggregate privilege into account

[ https://issues.apache.org/jira/browse/SLING-6867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz updated SLING-6867: --- Fix Version/s: Repoinit JCR 1.1.6 > Repoinit ACL handler should take aggregate

Re: Wiki access

Continuing on the thread, how can i submit articles on https://cwiki.apache.org/confluence/display/SLING/Index My confluence username is "suren" Thanks Suren On Mon, Apr 10, 2017 at 5:37 AM, Konrad Windszus wrote: > Thanks, Carsten. I will extend the documentation and point

Re: ResultRegistry for Health Checks -> StickyResults instead?

Hi, The goal is to declare health check results that remain valid for a specified time or forever. So I agree metrics as proposed in comment [1] cannot achieve this (limited to 1, 5 and 15 minutes time windows). However I still think a purely declarative approach is cleaner and will lead to

[jira] [Created] (SLING-6939) sling distribution leaks jcr sessions

Will McGauley created SLING-6939: Summary: sling distribution leaks jcr sessions Key: SLING-6939 URL: https://issues.apache.org/jira/browse/SLING-6939 Project: Sling Issue Type: Bug

Re: [DISCUSS] Can we Retire org.apache.sling.jcr.js.nodetypes to the Sling attic?

As a little follow-up, it looks like the only consumer of the org.apache.sling.jcr.js.nodetypes artifact is the org.apache.sling.resource-editor in contrib/explorers/resourceeditor. It almost looks like if we retire the nodetypes we might have to retire the resource-editor as well. Again, if

Re: [DISCUSS] Remove retired artifacts from the Downloads section and the dist dir

Hi Karl, On Tue, Jun 6, 2017 at 2:25 PM, Karl Pauls wrote: > ...currently, we are still listing retired artifacts (that have been > moved to the attic) in the downloads section and consequently, they > are still in the dist dir I think we still want the modules moved to

[DISCUSS] Remove retired artifacts from the Downloads section and the dist dir

Hi, currently, we are still listing retired artifacts (that have been moved to the attic) in the downloads section and consequently, they are still in the dist dir. I was wondering, should we remove them from both? regards, Karl -- Karl Pauls karlpa...@gmail.com

[jira] [Commented] (SLING-848) Support getting versioned resources by using uri path parameters

[ https://issues.apache.org/jira/browse/SLING-848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16038505#comment-16038505 ] Tomek Rękawek commented on SLING-848: - bq. Making the semantics of ";" depend on whether it is followed

Re: [VOTE] Apache Sling Resource Inventory 1.0.8, Content Distribution Core 0.2.8, Testing Sling Mock 2.2.12, Log Tracer 1.0.4, Commons Metrics 1.2.2

+1 regards, Karl 2017-06-06 11:15 GMT+02:00 Tommaso Teofili : > +1 > > Tommaso > > Il giorno lun 5 giu 2017 alle ore 16:24 Carsten Ziegeler > ha scritto: >> >> +1 >> >> >> >> -- >> Carsten Ziegeler >> Adobe Research Switzerland >>

[jira] [Commented] (SLING-848) Support getting versioned resources by using uri path parameters

[ https://issues.apache.org/jira/browse/SLING-848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16038545#comment-16038545 ] Julian Reschke commented on SLING-848: -- bq. The URI parameter format is defined by the RFC. Source,

Re: [RESULT] [VOTE] Apache Sling JUnit Core 1.0.26, Testing Clients 1.1.0, JUnit Remote Test Runners 1.0.12, Tooling Support Install 1.0.4, Tooling Support Source 1.0.4

Time to call the vote on the Apache Sling JUnit Core 1.0.26, Testing Clients 1.1.0, JUnit Remote Test Runners 1.0.12, Tooling Support Install 1.0.4, Tooling Support Source 1.0.4 releases. * +1 votes from Stefan Seifert, Carsten Ziegeler, Andrei Dulvac, and Karl Pauls. * No other votes. The vote

[jira] [Commented] (SLING-848) Support getting versioned resources by using uri path parameters

[ https://issues.apache.org/jira/browse/SLING-848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16038557#comment-16038557 ] Carsten Ziegeler commented on SLING-848: [~reschke] While I agree that the proposal is not the

[jira] [Commented] (SLING-848) Support getting versioned resources by using uri path parameters

[ https://issues.apache.org/jira/browse/SLING-848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16038582#comment-16038582 ] Tomek Rękawek commented on SLING-848: - [~reschke] bq. Source, please. All I can see in RFC 3986 is that

[jira] [Created] (SLING-6938) Create a multi-module maven archetype

Suren Konathala created SLING-6938: -- Summary: Create a multi-module maven archetype Key: SLING-6938 URL: https://issues.apache.org/jira/browse/SLING-6938 Project: Sling Issue Type:

[jira] [Commented] (SLING-848) Support getting versioned resources by using uri path parameters

[ https://issues.apache.org/jira/browse/SLING-848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16039472#comment-16039472 ] Alexander Klimetschek commented on SLING-848: - The original filename that triggered this issue

[jira] [Comment Edited] (SLING-848) Support getting versioned resources by using uri path parameters

[ https://issues.apache.org/jira/browse/SLING-848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16039472#comment-16039472 ] Alexander Klimetschek edited comment on SLING-848 at 6/6/17 8:53 PM: -

[jira] [Comment Edited] (SLING-848) Support getting versioned resources by using uri path parameters

[ https://issues.apache.org/jira/browse/SLING-848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16039472#comment-16039472 ] Alexander Klimetschek edited comment on SLING-848 at 6/6/17 8:52 PM: -

[jira] [Comment Edited] (SLING-848) Support getting versioned resources by using uri path parameters

[ https://issues.apache.org/jira/browse/SLING-848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16039472#comment-16039472 ] Alexander Klimetschek edited comment on SLING-848 at 6/6/17 8:52 PM: -