RE: [VOTE] Release Apache Sling HApi - Sling Hypermedia API client-side tools version 1.0.0

no problem adding it later. stefan >-Original Message- >From: Andrei Dulvac [mailto:andrei.dul...@gmail.com] >Sent: Friday, July 15, 2016 7:38 PM >To: dev@sling.apache.org >Subject: Re: [VOTE] Release Apache Sling HApi - Sling Hypermedia API >client-side tools version 1.0.0 > >Hi, I'll

Re: [VOTE] Release Apache Sling HApi - Sling Hypermedia API client-side tools version 1.0.0

Hi, I'll add some docu for the client as well, thanks for pointing that out. Does it have to be for this release? -Andrei On Thu, Jul 14, 2016 at 21:58 Stefan Seifert wrote: > +1 > > perhaps you can add a short documentation for what it is good and how it > can be used

Re: [VOTE] Release Apache Sling HApi - Sling Hypermedia API client-side tools version 1.0.0

Hi Oliver, Because it's a client-side tool, meant to be used outside the Sling instance, like it HTTP tests. I guess it could become a bundle, but I don't really see the point right now. -Andrei On Fri, Jul 15, 2016 at 18:54 Oliver Lietz wrote: > On Wednesday 13 July

Re: [VOTE] Release Apache Sling HApi - Sling Hypermedia API client-side tools version 1.0.0

On Wednesday 13 July 2016 15:59:35 Andrei Dulvac wrote: > Hi, Hi Andrei, > We solved 2 issues in this release: > *https://issues.apache.org/jira/browse/SLING/fixforversion/12337959 > * >

[jira] [Commented] (SLING-5849) Inconsistent event handling between local package importer and its factory

[ https://issues.apache.org/jira/browse/SLING-5849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15379564#comment-15379564 ] Tommaso Teofili commented on SLING-5849: sure, thanks [~marett]! > Inconsistent event handling

[jira] [Updated] (SLING-5849) Inconsistent event handling between local package importer and its factory

[ https://issues.apache.org/jira/browse/SLING-5849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothee Maret updated SLING-5849: -- Attachment: SLING-5849.diff > Inconsistent event handling between local package importer and

[jira] [Commented] (SLING-5849) Inconsistent event handling between local package importer and its factory

[ https://issues.apache.org/jira/browse/SLING-5849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15379509#comment-15379509 ] Timothee Maret commented on SLING-5849: --- [~teofili] could you review/apply this ? > Inconsistent

[jira] [Updated] (SLING-5849) Inconsistent event handling between local package importer and its factory

[ https://issues.apache.org/jira/browse/SLING-5849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothee Maret updated SLING-5849: -- Flags: Patch > Inconsistent event handling between local package importer and its factory >

[jira] [Commented] (SLING-5849) Inconsistent event handling between local package importer and its factory

[ https://issues.apache.org/jira/browse/SLING-5849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15379503#comment-15379503 ] Timothee Maret commented on SLING-5849: --- Opened PR https://github.com/apache/sling/pull/152 >

[jira] [Commented] (SLING-5849) Inconsistent event handling between local package importer and its factory

[ https://issues.apache.org/jira/browse/SLING-5849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15379502#comment-15379502 ] ASF GitHub Bot commented on SLING-5849: --- GitHub user tmaret opened a pull request:

[GitHub] sling pull request #152: SLING-5849 - Inconsistent event handling between lo...

GitHub user tmaret opened a pull request: https://github.com/apache/sling/pull/152 SLING-5849 - Inconsistent event handling between local package importer and its factory * Generate Package Events in the package importer instead of the factory You can merge this pull request into

RE: [DISCUSS] Path filtering support for ResourceChangeListeners

i personally would prefer using regex instead of glob syntax, because other areas in sling use it as well for path matching (e.g. sling mapping). about the performance implications where the filtering should take place i cannot say much currently. stefan >-Original Message- >From:

[jira] [Created] (SLING-5849) Inconsistent event handling between local package importer and its factory

Timothee Maret created SLING-5849: - Summary: Inconsistent event handling between local package importer and its factory Key: SLING-5849 URL: https://issues.apache.org/jira/browse/SLING-5849 Project:

[jira] [Commented] (SLING-5837) Allow ResourceChangeListeners to define glob patterns for resource matching

[ https://issues.apache.org/jira/browse/SLING-5837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15379371#comment-15379371 ] Radu Cotescu commented on SLING-5837: - I opened a thread at

Re: [DISCUSS] Path filtering support for ResourceChangeListeners

BTW, the issue is https://issues.apache.org/jira/browse/SLING-5837. On Fri, 15 Jul 2016 at 15:24 Radu Cotescu wrote: > Hello, > > The current release of the Sling API > org.apache.sling.api.resource.observation.ResourceChangeListener >

[DISCUSS] Path filtering support for ResourceChangeListeners

Hello, The current release of the Sling API org.apache.sling.api.resource.observation.ResourceChangeListener (org.apache.sling.api.resource.observation;version=1.0.0) specification does not provide any kind of support for path filtering or pattern matching. As I understand it, the future

[jira] [Updated] (SLING-5837) Allow ResourceChangeListeners to define glob patterns for resource matching

[ https://issues.apache.org/jira/browse/SLING-5837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu updated SLING-5837: Fix Version/s: (was: API 2.13.0) API 2.14.0 > Allow ResourceChangeListeners

[jira] [Reopened] (SLING-5837) Allow ResourceChangeListeners to define glob patterns for resource matching

[ https://issues.apache.org/jira/browse/SLING-5837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu reopened SLING-5837: - > Allow ResourceChangeListeners to define glob patterns for resource matching >

[CANCELLED][VOTE] Release Apache Sling API 2.13.0

Let's cancel this release until we all agree on a solution for the ResourceChangeListener path filtering support issues identified in SLING-5837. I'll open a new thread after I delete the tag and drop the staging repository. Thanks, Radu On Wed, 13 Jul 2016 at 15:14 Radu Cotescu

Re: [DISCUSS] new Scripting Service to provide ResourceResolvers with limited access

Hi, I think I haven't phrased properly my idea so let's give it another shot. The use cases that I'd like to cover with this service is getting a unified resource resolver that will be used for: * resolving script dependencies (data-sly-include / sling:include / other dependencies like the ones

[jira] [Commented] (SLING-5831) Support different thread pools for scheduled tasks

[ https://issues.apache.org/jira/browse/SLING-5831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15379283#comment-15379283 ] Chetan Mehrotra commented on SLING-5831: Thanks Carsten for this support!. In Oak we use following

[jira] [Commented] (SLING-5831) Support different thread pools for scheduled tasks

[ https://issues.apache.org/jira/browse/SLING-5831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15379267#comment-15379267 ] Carsten Ziegeler commented on SLING-5831: - [~chetanm] I've done a first implementation which

[RESULT] [VOTE] Release Apache Sling Testing Sling Mock 1.7.0, Sling Mock 2.0.0, Sling Mock Oak 2.0.0

Hi, The vote has passed with the following result : +1 (binding): Robert Munteanu, Carsten Ziegeler, Stefan Seifert, Oliver Lietz I will copy this release to the Sling dist directory and promote the artifacts to the central Maven repository. stefan

Re: Prefix for our service user names

On Fri, Jul 15, 2016 at 11:48 AM, Oliver Lietz wrote: > ...I don't think JCR will lead to issues but maybe our resource resolution > with > selectors and extensions... Good point so a sling- prefix is probably safer. -Bertrand

Re: Prefix for our service user names

On Friday 15 July 2016 11:35:20 Bertrand Delacretaz wrote: > Hi, Hi, > We're starting to define service users that various Sling modules will > need (like SLING-5848) and Oliver suggests using a prefix for those > usernames as a simple form of namespacing. > > How about "sling." - do people see

Prefix for our service user names

Hi, We're starting to define service users that various Sling modules will need (like SLING-5848) and Oliver suggests using a prefix for those usernames as a simple form of namespacing. How about "sling." - do people see possible issues with JCR usernames like sling.someserviceuser ? -Bertrand

[jira] [Commented] (SLING-5848) Define service user and ACLs for Scripting

[ https://issues.apache.org/jira/browse/SLING-5848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15379109#comment-15379109 ] Bertrand Delacretaz commented on SLING-5848: Good idea but let's discuss on dl-dev, I'll start

[jira] [Updated] (SLING-5848) Define service user and ACLs for Scripting

[ https://issues.apache.org/jira/browse/SLING-5848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz updated SLING-5848: Description: Scripting implementations require a (service) ResourceResolver with very limited read

[jira] [Comment Edited] (SLING-5848) Define service user and ACLs for Scripting

[ https://issues.apache.org/jira/browse/SLING-5848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15379106#comment-15379106 ] Oliver Lietz edited comment on SLING-5848 at 7/15/16 9:30 AM: -- Can we use a

[jira] [Commented] (SLING-5848) Define service user and ACLs for Scripting

[ https://issues.apache.org/jira/browse/SLING-5848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15379106#comment-15379106 ] Oliver Lietz commented on SLING-5848: - Can we use a {{.}} to separate the {{sling}} prefix? AEM is

[jira] [Commented] (SLING-5848) Define service user and ACLs for Scripting

[ https://issues.apache.org/jira/browse/SLING-5848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15379094#comment-15379094 ] Bertrand Delacretaz commented on SLING-5848: If we start creating service users that Sling

[jira] [Updated] (SLING-5848) Define service user and ACLs for Scripting

[ https://issues.apache.org/jira/browse/SLING-5848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz updated SLING-5848: Description: Scripting implementations require a (service) ResourceResolver with very limited read

[jira] [Updated] (SLING-5848) Define service user and ACLs for Scripting

[ https://issues.apache.org/jira/browse/SLING-5848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz updated SLING-5848: Description: Scripting implementations require a (service) ResourceResolver with very limited read

[jira] [Commented] (SLING-5252) Remove getAdministrativeResourceResolver() from Scripting Core

[ https://issues.apache.org/jira/browse/SLING-5252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15379090#comment-15379090 ] Oliver Lietz commented on SLING-5252: - Right. See SLING-5848 and add your comments please. > Remove

[jira] [Created] (SLING-5848) Define service user and ACLs for Scripting

Oliver Lietz created SLING-5848: --- Summary: Define service user and ACLs for Scripting Key: SLING-5848 URL: https://issues.apache.org/jira/browse/SLING-5848 Project: Sling Issue Type: Task

[jira] [Commented] (SLING-5837) Allow ResourceChangeListeners to define glob patterns for resource matching

[ https://issues.apache.org/jira/browse/SLING-5837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15379049#comment-15379049 ] Stefan Seifert commented on SLING-5837: --- really important pro or contra is only point #1 - once we

[jira] [Commented] (SLING-5252) Remove getAdministrativeResourceResolver() from Scripting Core

[ https://issues.apache.org/jira/browse/SLING-5252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15379037#comment-15379037 ] Radu Cotescu commented on SLING-5252: - For the {{ScriptCache}} we can just implement a

[jira] [Commented] (SLING-5837) Allow ResourceChangeListeners to define glob patterns for resource matching

[ https://issues.apache.org/jira/browse/SLING-5837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15379031#comment-15379031 ] Radu Cotescu commented on SLING-5837: - Let me try to answer punctually: # I've thought that glob

Re: [VOTE] Release Apache Sling HApi - Sling Hypermedia API client-side tools version 1.0.0

On Wed, Jul 13, 2016 at 5:59 PM, Andrei Dulvac wrote: > ...Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-1479/ ... +1 for the release of

Re: Updating our parent pom

On Thu, Jul 14, 2016 at 9:43 PM, Carsten Ziegeler wrote: > ...looking at our parent pom, we have there some really really old > dependencies +1 for the updates that you mentioned, as long as our full build with integration tests still works after that. -Bertrand

[jira] [Updated] (SLING-5847) Deadlock in JcrResourceBundleProvider.getResourceBundleInternal when preloading is enabled

[ https://issues.apache.org/jira/browse/SLING-5847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-5847: --- Description: Under particular timing situations the {{reloadBundle}} job and a parallel call

[jira] [Resolved] (SLING-5847) Deadlock in JcrResourceBundleProvider.getResourceBundleInternal when preloading is enabled

[ https://issues.apache.org/jira/browse/SLING-5847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus resolved SLING-5847. Resolution: Fixed Fix Version/s: i18n 2.4.8 > Deadlock in

[jira] [Commented] (SLING-5847) Deadlock in JcrResourceBundleProvider.getResourceBundleInternal when preloading is enabled

[ https://issues.apache.org/jira/browse/SLING-5847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15379004#comment-15379004 ] Konrad Windszus commented on SLING-5847: Fixed in [r1752795|https://svn.apache.org/r1752795].

[jira] [Updated] (SLING-5847) Deadlock in JcrResourceBundleProvider.getResourceBundleInternal when preloading is enabled

[ https://issues.apache.org/jira/browse/SLING-5847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-5847: --- Summary: Deadlock in JcrResourceBundleProvider.getResourceBundleInternal when preloading is

[jira] [Updated] (SLING-5847) Deadlock in JcrResourceBundleProvider.getResourceBundleInternal

[ https://issues.apache.org/jira/browse/SLING-5847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-5847: --- Priority: Critical (was: Major) > Deadlock in

[jira] [Commented] (SLING-5831) Support different thread pools for scheduled tasks

[ https://issues.apache.org/jira/browse/SLING-5831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15378928#comment-15378928 ] Chetan Mehrotra commented on SLING-5831: That would not be an issue with current implementation.

[jira] [Created] (SLING-5847) Deadlock in JcrResourceBundleProvider.getResourceBundleInternal

Konrad Windszus created SLING-5847: -- Summary: Deadlock in JcrResourceBundleProvider.getResourceBundleInternal Key: SLING-5847 URL: https://issues.apache.org/jira/browse/SLING-5847 Project: Sling