Re: Updating our parent pom

Hi, >> 9. Add the bnd maven plugin 3.2.0 >> (see https://github.com/bndtools/bnd/tree/master/maven/bnd-maven-plugin) >> This plugin is newer than the maven bundle plugin and closer to bnd >> change. So we can start using this in our modules. > > we should make clear how to use bnd.bnd files. Do

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

On Thursday 14 July 2016 20:55:26 Carsten Ziegeler wrote: > > On Thursday 14 July 2016 16:02:46 Carsten Ziegeler wrote: > >> I think we should have the service user concept and getting a service > >> user is pretty easy. So I don't see the need for something need, > >> competing with service

Re: Updating our parent pom

On Thursday 14 July 2016 21:43:45 Carsten Ziegeler wrote: > Hi, Hi Carsten, > looking at our parent pom, we have there some really really old > dependencies. The reasoning behind this is that we usually try to use > the minimal possible version for a dependency. However, for some things > newer

[jira] [Created] (SLING-5846) Update SCR Annotations to 1.11.0

Carsten Ziegeler created SLING-5846: --- Summary: Update SCR Annotations to 1.11.0 Key: SLING-5846 URL: https://issues.apache.org/jira/browse/SLING-5846 Project: Sling Issue Type: Task

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

+1 perhaps you can add a short documentation for what it is good and how it can be used - [1] does not mention the client. stefan [1] https://github.com/apache/sling/tree/trunk/contrib/extensions/hapi

RE: Updating our parent pom

+1 >-Original Message- >From: Carsten Ziegeler [mailto:cziege...@apache.org] >Sent: Thursday, July 14, 2016 9:44 PM >To: Sling Developers >Subject: Updating our parent pom > >Hi, > >looking at our parent pom, we have there some really really old >dependencies. The reasoning behind this is

Re: [VOTE] Release Apache Sling Resource Resolver 1.4.14

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

RE: [VOTE] Release Apache Sling Discovery Base 1.1.4, Discovery Impl 1.2.8, Discovery Oak 1.2.8

+1

Updating our parent pom

Hi, looking at our parent pom, we have there some really really old dependencies. The reasoning behind this is that we usually try to use the minimal possible version for a dependency. However, for some things newer versions are out for some time and are the de-facto standard. I think we should

RE: [VOTE] Release Apache Sling Resource Resolver 1.4.14

+1

[jira] [Resolved] (SLING-5845) Update maven plugin versions

[ https://issues.apache.org/jira/browse/SLING-5845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-5845. - Resolution: Fixed Done in rev 1752731 > Update maven plugin versions >

[jira] [Created] (SLING-5845) Update maven plugin versions

Carsten Ziegeler created SLING-5845: --- Summary: Update maven plugin versions Key: SLING-5845 URL: https://issues.apache.org/jira/browse/SLING-5845 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=15378195#comment-15378195 ] Stefan Seifert commented on SLING-5837: --- i've no opinion whether {{java.nio.file.PathMatcher}} may

[jira] [Resolved] (SLING-5844) Update to Apache parent pom 18

[ https://issues.apache.org/jira/browse/SLING-5844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-5844. - Done in rev 1752729 > Update to Apache parent pom 18 > -- > >

[jira] [Created] (SLING-5844) Update to Apache parent pom 18

Carsten Ziegeler created SLING-5844: --- Summary: Update to Apache parent pom 18 Key: SLING-5844 URL: https://issues.apache.org/jira/browse/SLING-5844 Project: Sling Issue Type: Task

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

[ https://issues.apache.org/jira/browse/SLING-5831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned SLING-5831: --- Assignee: Carsten Ziegeler > Support different thread pools for scheduled tasks >

Re: [VOTE] Release Apache Sling Discovery Base 1.1.4, Discovery Impl 1.2.8, Discovery Oak 1.2.8

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

[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=15378134#comment-15378134 ] Carsten Ziegeler commented on SLING-5831: - As a first step I've refactored the code and created a

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

> On Thursday 14 July 2016 16:02:46 Carsten Ziegeler wrote: >> I think we should have the service user concept and getting a service >> user is pretty easy. So I don't see the need for something need, >> competing with service users. >> >> We can discuss about a scripting service user which gets

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

On Thursday 14 July 2016 16:02:46 Carsten Ziegeler wrote: > I think we should have the service user concept and getting a service > user is pretty easy. So I don't see the need for something need, > competing with service users. > > We can discuss about a scripting service user which gets the

[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=15377348#comment-15377348 ] Carsten Ziegeler commented on SLING-5831: - [~chetanm] I think the above does not work, imagine the

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

> No, the goal is to expose a ResourceResolver backed by the same > service-user to all scripting modules that need to perform read operations > on resources from the search paths. You can share the service user between bundles, I don't understand the problem to be honest Carsten > > On Thu,

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

On Thu, Jul 14, 2016 at 4:13 PM, Radu Cotescu wrote: >...I was proposing to have a generic service that would be able to > provide these Resolvers to scripting consumers But IIUC your goal is only to make some mostly static values available from those services? If that's

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

No, the goal is to expose a ResourceResolver backed by the same service-user to all scripting modules that need to perform read operations on resources from the search paths. On Thu, 14 Jul 2016 at 16:31 Bertrand Delacretaz wrote: > But IIUC your goal is only to make

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

Hi Bertrand, Most of the scripting engines from Sling rely on a ResourceResolver to read Resources from /libs and /apps. Currently some of them use the administrative resolver from the ScriptContext attributes and pass that further wherever they might need it. Instead of relying on an

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

Hi, On Thu, Jul 14, 2016 at 3:58 PM, Radu Cotescu wrote: > ...what's your opinion about defining a new service in > o.a.s.scripting.api (implemented in o.a.s.scripting.core) that would > provide ResourceResolvers with restricted access for o.a.s.scripting.* > modules - for

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

I think we should have the service user concept and getting a service user is pretty easy. So I don't see the need for something need, competing with service users. We can discuss about a scripting service user which gets the required access rights though Carsten > Hi, > > In the context of

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

Hi, In the context of [1] and corroborated by the fact that repoinit was released, what's your opinion about defining a new service in o.a.s.scripting.api (implemented in o.a.s.scripting.core) that would provide ResourceResolvers with restricted access for o.a.s.scripting.* modules - for starters

[jira] [Updated] (SLING-5842) Register JCR nodetypes from the provisioning model

[ https://issues.apache.org/jira/browse/SLING-5842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz updated SLING-5842: --- Description: Now that we can create repository paths from the provisioning model [1]

[jira] [Created] (SLING-5843) Register JCR namespaces from the provisioning model

Bertrand Delacretaz created SLING-5843: -- Summary: Register JCR namespaces from the provisioning model Key: SLING-5843 URL: https://issues.apache.org/jira/browse/SLING-5843 Project: Sling

[jira] [Created] (SLING-5842) Register JCR nodetypes from the provisioning model

Bertrand Delacretaz created SLING-5842: -- Summary: Register JCR nodetypes from the provisioning model Key: SLING-5842 URL: https://issues.apache.org/jira/browse/SLING-5842 Project: Sling

[VOTE] Release Apache Sling Discovery Base 1.1.4, Discovery Impl 1.2.8, Discovery Oak 1.2.8

Hi, we solved 1 issue in Apache Sling Discovery Base 1.1.4: https://issues.apache.org/jira/browse/SLING/fixforversion/12334213 we solved 2 issues in Apache Sling Discovery Impl 1.2.8: https://issues.apache.org/jira/browse/SLING/fixforversion/12334201 we solved 3 issues in Apache Sling Discovery

[jira] [Closed] (SLING-5341) Update Jackrabbit in Commons Testing to 2.11.2

[ https://issues.apache.org/jira/browse/SLING-5341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz closed SLING-5341. --- > Update Jackrabbit in Commons Testing to 2.11.2 > -- > >

[jira] [Created] (SLING-5841) Self closing DIV when using 'html' context in Sightly

Dan Chapman created SLING-5841: -- Summary: Self closing DIV when using 'html' context in Sightly Key: SLING-5841 URL: https://issues.apache.org/jira/browse/SLING-5841 Project: Sling Issue Type:

[jira] [Resolved] (SLING-4849) Create Metrics instumentation bundle using ASM.

[ https://issues.apache.org/jira/browse/SLING-4849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ian Boston resolved SLING-4849. --- Resolution: Implemented Moved feature to separate repo to avoid bloating Sling repo. > Create

[jira] [Commented] (SLING-4849) Create Metrics instumentation bundle using ASM.

[ https://issues.apache.org/jira/browse/SLING-4849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15376536#comment-15376536 ] Ian Boston commented on SLING-4849: --- The branch has been re-homed to https://github.com/ieb/slingmetrics

[jira] [Commented] (SLING-5803) FilterRuleExcludeCategoryIgnoreIfTest fails on Jenkins

[ https://issues.apache.org/jira/browse/SLING-5803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15376529#comment-15376529 ] Andrei Dulvac commented on SLING-5803: -- Ok, makes sense, I've reopened the issue. >

[jira] [Reopened] (SLING-5803) FilterRuleExcludeCategoryIgnoreIfTest fails on Jenkins

[ https://issues.apache.org/jira/browse/SLING-5803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrei Dulvac reopened SLING-5803: -- > FilterRuleExcludeCategoryIgnoreIfTest fails on Jenkins >

[jira] [Commented] (SLING-5803) FilterRuleExcludeCategoryIgnoreIfTest fails on Jenkins

[ https://issues.apache.org/jira/browse/SLING-5803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15376468#comment-15376468 ] Bertrand Delacretaz commented on SLING-5803: I first thought _JUnit Computer_ was a typo but

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

On Tuesday 12 July 2016 10:41:32 Stefan Seifert wrote: > Hi, > > Apache Sling Testing Sling Mock 1.7.0 (3 issues) > https://issues.apache.org/jira/browse/SLING/fixforversion/12334802 +1 > Apache Sling Testing Sling Mock 2.0.0 (6 issues) >