[jira] [Resolved] (SLING-6289) Improve java resource change listener to use globs

[ https://issues.apache.org/jira/browse/SLING-6289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-6289. - Resolution: Fixed Changed to listen for .java file changes only > Improve java resource

[jira] [Created] (SLING-6289) Improve java resource change listener to use globs

Carsten Ziegeler created SLING-6289: --- Summary: Improve java resource change listener to use globs Key: SLING-6289 URL: https://issues.apache.org/jira/browse/SLING-6289 Project: Sling Issue

[jira] [Resolved] (SLING-6288) Improve jsp resource change listener to use globs

[ https://issues.apache.org/jira/browse/SLING-6288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-6288. - Resolution: Fixed Changed the impl to listen for changes of jsp, jspf, jspx, tld and tag

[jira] [Created] (SLING-6288) Improve jsp resource change listener to use globs

Carsten Ziegeler created SLING-6288: --- Summary: Improve jsp resource change listener to use globs Key: SLING-6288 URL: https://issues.apache.org/jira/browse/SLING-6288 Project: Sling Issue

[jira] [Resolved] (SLING-6279) Switch from event admin to Sling Resource Observation API

[ https://issues.apache.org/jira/browse/SLING-6279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-6279. - Resolution: Fixed > Switch from event admin to Sling Resource Observation API >

[jira] [Updated] (SLING-6287) support maxparallel for main job queue to be -1 or between 0.0 and 1.0

[ https://issues.apache.org/jira/browse/SLING-6287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Egli updated SLING-6287: --- Description:

[jira] [Updated] (SLING-6287) support maxparallel for main job queue to be -1 or between 0.0 and 1.0

[ https://issues.apache.org/jira/browse/SLING-6287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Egli updated SLING-6287: --- Summary: support maxparallel for main job queue to be -1 or between 0.0 and 1.0 (was: support

[jira] [Updated] (SLING-6287) support maxparallel for main job queue

[ https://issues.apache.org/jira/browse/SLING-6287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Egli updated SLING-6287: --- Attachment: SLING-6287.patch Attached [^SLING-6287.patch] which removes the check for

[jira] [Created] (SLING-6287) support maxparallel for main job queue

Stefan Egli created SLING-6287: -- Summary: support maxparallel for main job queue Key: SLING-6287 URL: https://issues.apache.org/jira/browse/SLING-6287 Project: Sling Issue Type: Improvement

[jira] [Resolved] (SLING-6286) main job queue has no service pid assigned, leading to a /config/null link

[ https://issues.apache.org/jira/browse/SLING-6286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Egli resolved SLING-6286. Resolution: Fixed Applied patch from [~cziegeler], here:

[jira] [Created] (SLING-6286) main job queue has no service pid assigned, leading to a /config/null link

Stefan Egli created SLING-6286: -- Summary: main job queue has no service pid assigned, leading to a /config/null link Key: SLING-6286 URL: https://issues.apache.org/jira/browse/SLING-6286 Project: Sling

Re: trunk build does not work // was: mountByFS does not work

Hi Julian, thanks for your feedback! Am 15.11.16 um 10:47 schrieb Julian Sedding: Hi Sandro org/apache/sling/jcr/base/LoginAdminWhitelist looks like your checkout or snapshots on your machine are not quite up to date. I removed the I'am at the latest trunk, did 'mvn clean ...' and created a

Re: [VOTE] Release Apache Sling Discovery Commons 1.0.18/Base 1.1.6/Impl 1.2.10/Oak 1.2.16

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

Re: LoginAdminWhitelist: default bundles vs additional bundles

Julian Sedding wrote > Hi all > > The LoginAdminWhitelist has two lists of whitelisted bundles, > "default" and "additional". The rational as I understand it was to > distinguish between a whitelist that is shipped with a product > (default) and a whitelist that a user of the product can

Re: [VOTE] Release Apache Sling Discovery Commons 1.0.18/Base 1.1.6/Impl 1.2.10/Oak 1.2.16

+1 Cheers, Stefan On 15/11/16 14:20, "Stefan Egli" wrote: >Hi, > >We solved 4 issues in these discovery releases: > >https://issues.apache.org/jira/browse/SLING/fixforversion/12338309 >https://issues.apache.org/jira/browse/SLING/fixforversion/12337847

Re: Bump JCR Base bundle major version?

Julian Sedding wrote > Hi all > > The JCR Base bundle's package org.apache.sling.jcr.base was recently > bumped to 3.x.y. Should the next release of the bundle reflect this? > +1 -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org

[VOTE] Release Apache Sling Discovery Commons 1.0.18/Base 1.1.6/Impl 1.2.10/Oak 1.2.16

Hi, We solved 4 issues in these discovery releases: https://issues.apache.org/jira/browse/SLING/fixforversion/12338309 https://issues.apache.org/jira/browse/SLING/fixforversion/12337847 https://issues.apache.org/jira/browse/SLING/fixforversion/12337848

[jira] [Updated] (SLING-5060) use virtual clock for discovery tests

[ https://issues.apache.org/jira/browse/SLING-5060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Egli updated SLING-5060: --- Fix Version/s: (was: Discovery Impl 1.2.10) Discovery Impl 1.2.12 > use

[jira] [Updated] (SLING-4380) Use sling mocks for the discovery impl tests

[ https://issues.apache.org/jira/browse/SLING-4380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Egli updated SLING-4380: --- Fix Version/s: (was: Discovery Impl 1.2.10) Discovery Impl 1.2.12 > Use sling

[jira] [Updated] (SLING-4135) Make discovery implementation independent from JCR

[ https://issues.apache.org/jira/browse/SLING-4135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Egli updated SLING-4135: --- Fix Version/s: (was: Discovery Impl 1.2.10) Discovery Impl 1.2.12 > Make

[jira] [Updated] (SLING-5598) Exclude slow tests by default with assume(sling.slow.tests.enabled)

[ https://issues.apache.org/jira/browse/SLING-5598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Egli updated SLING-5598: --- Fix Version/s: (was: Discovery Oak 1.2.16) (was: Discovery Commons 1.0.18)

[jira] [Updated] (SLING-6285) Implement LoginAdminWhitelist in JCR Base

[ https://issues.apache.org/jira/browse/SLING-6285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding updated SLING-6285: -- Attachment: SLING-6285-jsedding.patch Attached is a patch implementing the proposed solution.

[jira] [Resolved] (SLING-5231) Remove getAdministrativeResourceResolver() usage from Discovery components

[ https://issues.apache.org/jira/browse/SLING-5231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Egli resolved SLING-5231. Resolution: Fixed > Remove getAdministrativeResourceResolver() usage from Discovery components >

[jira] [Commented] (SLING-5231) Remove getAdministrativeResourceResolver() usage from Discovery components

[ https://issues.apache.org/jira/browse/SLING-5231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15667042#comment-15667042 ] Stefan Egli commented on SLING-5231: Merged patches from [~cziegeler] to the discovery bundles in

Re: [VOTE] Release Apache Sling JCR Resource 2.8.2 and Apache Sling JCR Oak Repository Server 1.1.2

Thanks, I didn't know that. In this case I cancel only the vote for JCR Oak Repository Server 1.1.2. The vote for JCR Resource 2.8.2 is not affected and can continue. Regards Julian On Tue, Nov 15, 2016 at 11:45 AM, Carsten Ziegeler wrote: > Julian Sedding wrote >> Is it

Re: [VOTE] Release Apache Sling JCR Resource 2.8.2 and Apache Sling JCR Oak Repository Server 1.1.2

Julian Sedding wrote > Is it possible if to release only part of the staging repository? If > so we can continue the vote for JCR Resource. Yes, you can remove files from staging and therefore remove the oak artifacts only, keeping jcr.resource there Carsten > > Regards > Julian > > On Tue,

Bump JCR Base bundle major version?

Hi all The JCR Base bundle's package org.apache.sling.jcr.base was recently bumped to 3.x.y. Should the next release of the bundle reflect this? Regards Julian

LoginAdminWhitelist: default bundles vs additional bundles

Hi all The LoginAdminWhitelist has two lists of whitelisted bundles, "default" and "additional". The rational as I understand it was to distinguish between a whitelist that is shipped with a product (default) and a whitelist that a user of the product can administer (additional). This kind of

[jira] [Commented] (SLING-6174) Use Jackrabbit/Oak globbing support

[ https://issues.apache.org/jira/browse/SLING-6174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15666779#comment-15666779 ] Carsten Ziegeler commented on SLING-6174: - Actually we need to wait for Oak 1.5.14 > Use

[jira] [Created] (SLING-6285) Implement LoginAdminWhitelist in Jcr Base

Julian Sedding created SLING-6285: - Summary: Implement LoginAdminWhitelist in Jcr Base Key: SLING-6285 URL: https://issues.apache.org/jira/browse/SLING-6285 Project: Sling Issue Type:

Re: [VOTE] Release Apache Sling JCR Resource 2.8.2 and Apache Sling JCR Oak Repository Server 1.1.2

Is it possible if to release only part of the staging repository? If so we can continue the vote for JCR Resource. Regards Julian On Tue, Nov 15, 2016 at 11:23 AM, Carsten Ziegeler wrote: > Julian Sedding wrote >> Hi all >> >> I will cancel this vote. In an offline

Re: [VOTE] Release Apache Sling JCR Resource 2.8.2 and Apache Sling JCR Oak Repository Server 1.1.2

Julian Sedding wrote > Hi all > > I will cancel this vote. In an offline discussion with Bertrand and > Carsten we concluded that the LoginAdminWhitelist, that is a private > implementation detail of the Oak Server bundle in the package under > vote, would be better moved to JCR Base, so that any

[jira] [Updated] (SLING-6285) Implement LoginAdminWhitelist in JCR Base

[ https://issues.apache.org/jira/browse/SLING-6285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding updated SLING-6285: -- Summary: Implement LoginAdminWhitelist in JCR Base (was: Implement LoginAdminWhitelist in Jcr

Re: [VOTE] Release Apache Sling JCR Resource 2.8.2 and Apache Sling JCR Oak Repository Server 1.1.2

Hi all I will cancel this vote. In an offline discussion with Bertrand and Carsten we concluded that the LoginAdminWhitelist, that is a private implementation detail of the Oak Server bundle in the package under vote, would be better moved to JCR Base, so that any implementation of its

Re: trunk build does not work // was: mountByFS does not work

Hi Sandro org/apache/sling/jcr/base/LoginAdminWhitelist looks like your checkout or snapshots on your machine are not quite up to date. I removed the method AbstractSlingRepositoryManager.getLoginAdminWhitelist(), so maybe you need to first build a local snapshot of bundles/jcr/base and then try

[jira] [Closed] (SLING-6275) Unable to impersonate user with surrogate pair character

[ https://issues.apache.org/jira/browse/SLING-6275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Antonio Sanso closed SLING-6275. > Unable to impersonate user with surrogate pair character >

[RESULT][VOTE] Release Apache Sling Authentication Service 1.3.22

The vote passed with 4 binding +1s regards antonio

[jira] [Updated] (SLING-6174) Use Jackrabbit/Oak globbing support

[ https://issues.apache.org/jira/browse/SLING-6174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-6174: Attachment: jcresource-patch.txt > Use Jackrabbit/Oak globbing support >

[jira] [Updated] (SLING-6174) Use Jackrabbit/Oak globbing support

[ https://issues.apache.org/jira/browse/SLING-6174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-6174: Attachment: (was: jcresource-patch.txt) > Use Jackrabbit/Oak globbing support >