[jira] [Updated] (SLING-6063) plumber servlet doesn't persist changes anymore

[ https://issues.apache.org/jira/browse/SLING-6063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Peltier updated SLING-6063: --- Attachment: SLING-6063.patch fixed in attached patch > plumber servlet doesn't persist

[jira] [Created] (SLING-6063) plumber servlet doesn't persist changes anymore

Nicolas Peltier created SLING-6063: -- Summary: plumber servlet doesn't persist changes anymore Key: SLING-6063 URL: https://issues.apache.org/jira/browse/SLING-6063 Project: Sling Issue

Re: [Oak] Too many OSGi configurations required

On Tuesday 20 September 2016 16:04:07 Carsten Ziegeler wrote: > > On Tuesday 20 September 2016 14:57:40 Robert Munteanu wrote: > >> On Tue, 2016-09-20 at 13:49 +0200, Carsten Ziegeler wrote: > >>> I think we created a monster when it comes to configuration > >>> requirements > >>> with the Oak

RE: [VOTE] Release Apache Sling Testing Clients 1.0.0, Apache Sling Server Setup Tools 1.0.0 and Apache Sling Testing Rules 1.0.0

+1 this is a lot of interesting stuff - do we already have some documentation/sample project for this? stefan

[jira] [Commented] (SLING-5999) JcrResourceBundleProvider should move to new ResourceChangeListener API

[ https://issues.apache.org/jira/browse/SLING-5999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15506936#comment-15506936 ] Carsten Ziegeler commented on SLING-5999: - This is more complicated as right now the listener

[jira] [Updated] (SLING-5999) JcrResourceBundleProvider should move to new ResourceChangeListener API

[ https://issues.apache.org/jira/browse/SLING-5999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-5999: Component/s: (was: Extensions) i18n > JcrResourceBundleProvider should

[jira] [Updated] (SLING-5999) JcrResourceBundleProvider should move to new ResourceChangeListener API

[ https://issues.apache.org/jira/browse/SLING-5999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-5999: Fix Version/s: i18n 2.5.4 > JcrResourceBundleProvider should move to new

[jira] [Assigned] (SLING-5999) JcrResourceBundleProvider should move to new ResourceChangeListener API

[ https://issues.apache.org/jira/browse/SLING-5999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned SLING-5999: --- Assignee: Carsten Ziegeler > JcrResourceBundleProvider should move to new

[jira] [Resolved] (SLING-5997) JobManagerImpl should move to new ResourceChangeListener API

[ https://issues.apache.org/jira/browse/SLING-5997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-5997. - Resolution: Fixed Updated the code to use the ResourceChangeListener The IT tests have

[jira] [Updated] (SLING-5417) Jobs are only partially persisted

[ https://issues.apache.org/jira/browse/SLING-5417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-5417: Fix Version/s: (was: Event 4.2.0) > Jobs are only partially persisted >

[jira] [Updated] (SLING-5417) Jobs are only partially persisted

[ https://issues.apache.org/jira/browse/SLING-5417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-5417: Component/s: (was: Extensions) Event > Jobs are only partially

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

[ https://issues.apache.org/jira/browse/SLING-5202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-5202: Component/s: (was: Extensions) Event > Use new resource API for

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

[ https://issues.apache.org/jira/browse/SLING-5202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-5202: Fix Version/s: (was: Event 4.2.0) > Use new resource API for querying and copy/move >

[jira] [Resolved] (SLING-5870) Switch event ITs to use Oak

[ https://issues.apache.org/jira/browse/SLING-5870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-5870. - Resolution: Fixed I just did another try and this time it nearly worked out of the box >

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

[ https://issues.apache.org/jira/browse/SLING-5203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned SLING-5203: --- Assignee: Carsten Ziegeler > Move integration tests to Oak >

[jira] [Assigned] (SLING-5870) Switch event ITs to use Oak

[ https://issues.apache.org/jira/browse/SLING-5870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned SLING-5870: --- Assignee: Carsten Ziegeler > Switch event ITs to use Oak >

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

[ https://issues.apache.org/jira/browse/SLING-5203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-5203. - Resolution: Fixed > Move integration tests to Oak > - > >

[jira] [Assigned] (SLING-5997) JobManagerImpl should move to new ResourceChangeListener API

[ https://issues.apache.org/jira/browse/SLING-5997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned SLING-5997: --- Assignee: Carsten Ziegeler > JobManagerImpl should move to new

[jira] [Updated] (SLING-5997) JobManagerImpl should move to new ResourceChangeListener API

[ https://issues.apache.org/jira/browse/SLING-5997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-5997: Fix Version/s: Event 4.2.0 > JobManagerImpl should move to new ResourceChangeListener API >

Re: [Oak] Too many OSGi configurations required

> On Tuesday 20 September 2016 14:57:40 Robert Munteanu wrote: >> On Tue, 2016-09-20 at 13:49 +0200, Carsten Ziegeler wrote: >>> I think we created a monster when it comes to configuration >>> requirements >>> with the Oak server bundle. >>> >>> Have a look at [1] where I had to add dozens of

Re: [Oak] Too many OSGi configurations required

> On Tue, 2016-09-20 at 13:49 +0200, Carsten Ziegeler wrote: >> I think we created a monster when it comes to configuration >> requirements >> with the Oak server bundle. >> >> Have a look at [1] where I had to add dozens of configurations just >> to >> get a JCR repository running. And this

[jira] [Commented] (SLING-6056) achieve 1:1 mapping between observation and resource change listener

[ https://issues.apache.org/jira/browse/SLING-6056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15506623#comment-15506623 ] Stefan Egli commented on SLING-6056: perhaps this should go on a separate ticket, but related to

[jira] [Updated] (SLING-5879) StatementCache interceptor configured by default causes ResultSets to remain open

[ https://issues.apache.org/jira/browse/SLING-5879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated SLING-5879: -- Attachment: SLING-5879.diff proposed patch; [~chetanm] can you check, apply, and release? >

[jira] [Resolved] (SLING-5998) NewJobSender should move to new ResourceChangeListener API

[ https://issues.apache.org/jira/browse/SLING-5998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-5998. - Resolution: Fixed > NewJobSender should move to new ResourceChangeListener API >

Re: [Oak] Too many OSGi configurations required

On Tuesday 20 September 2016 14:57:40 Robert Munteanu wrote: > On Tue, 2016-09-20 at 13:49 +0200, Carsten Ziegeler wrote: > > I think we created a monster when it comes to configuration > > requirements > > with the Oak server bundle. > > > > Have a look at [1] where I had to add dozens of

Re: [VOTE] Release Apache Sling Testing Clients 1.0.0, Apache Sling Server Setup Tools 1.0.0 and Apache Sling Testing Rules 1.0.0

Hi, Karl is absolutely right: clients, serversetup, rules. Although if you build from trunk, each of them should build, as I've deployed the SNAPSHOTS. -Andrei On Tue, Sep 20, 2016 at 2:04 PM Karl Pauls wrote: > On Tue, Sep 20, 2016 at 2:01 PM, Daniel Klco

Re: [VOTE] Release Apache Sling Testing Clients 1.0.0, Apache Sling Server Setup Tools 1.0.0 and Apache Sling Testing Rules 1.0.0

On Tue, Sep 20, 2016 at 2:01 PM, Daniel Klco wrote: > Andrei, > > What is the correct order to build these modules in? > its clients, seversetup, rules. FWIW, it did build for me. regards, Karl > Thanks, > > On Tue, Sep 20, 2016 at 4:50 AM, Karl Pauls

Re: [VOTE] Release Apache Sling Testing Clients 1.0.0, Apache Sling Server Setup Tools 1.0.0 and Apache Sling Testing Rules 1.0.0

Andrei, What is the correct order to build these modules in? Thanks, On Tue, Sep 20, 2016 at 4:50 AM, Karl Pauls wrote: > +1 > > regards, > > Karl > > On Mon, Sep 19, 2016 at 4:54 PM, Andrei Dulvac wrote: > > > Hi, > > > > These are the first releases

Re: [Oak] Too many OSGi configurations required

On Tue, 2016-09-20 at 13:49 +0200, Carsten Ziegeler wrote: > I think we created a monster when it comes to configuration > requirements > with the Oak server bundle. > > Have a look at [1] where I had to add dozens of configurations just > to > get a JCR repository running. And this requires not

[Oak] Too many OSGi configurations required

I think we created a monster when it comes to configuration requirements with the Oak server bundle. Have a look at [1] where I had to add dozens of configurations just to get a JCR repository running. And this requires not only OSGi configurations but also framework properties. Let's start with

[jira] [Commented] (SLING-5998) NewJobSender should move to new ResourceChangeListener API

[ https://issues.apache.org/jira/browse/SLING-5998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15506243#comment-15506243 ] Carsten Ziegeler commented on SLING-5998: - Thanks for your patch [~hanishbansal93] I've applied a

[jira] [Assigned] (SLING-5998) NewJobSender should move to new ResourceChangeListener API

[ https://issues.apache.org/jira/browse/SLING-5998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned SLING-5998: --- Assignee: Carsten Ziegeler > NewJobSender should move to new ResourceChangeListener

Re: CI alternatives for Sling (was: [i18n] IT Tests failing in reactor build)

Hi Andrei, (Kind request - please don't top post, at least not in a long conversation thread which uses bottom-posting, it's quite hard to understand what you're replying to :-) ) On Tue, 2016-09-20 at 09:45 +, Andrei Dulvac wrote: > Hi Robert, > > Have a quick look at

Re: CI alternatives for Sling (was: [i18n] IT Tests failing in reactor build)

Hi Robert, Have a quick look at https://jenkins.io/doc/pipeline/jenkinsfile/ It is a jenkins 1.X plugin, formerly known as "Workflow plugin": https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Plugin It is part of jenkins 2.0 now (https://jenkins.io/2.0/) and it will definitely surpass usage of

Re: Clarification on https://sling.apache.org/documentation/the-sling-engine/url-decomposition.html

Thanks, got it. Indeed the algorithm seems to differ whether it resolves to an existing path or a non-existing path. Are there any more tests for the resolve method except for the basic ones in

Re: CI alternatives for Sling (was: [i18n] IT Tests failing in reactor build)

On Tue, 2016-09-20 at 09:36 +0200, Bertrand Delacretaz wrote: > Hi, > > On Mon, Sep 19, 2016 at 10:26 PM, Robert Munteanu > wrote: > > > > ...Another benefit is that if a contributor wants to reproduce a > > problem > > on Jenkins, all the effort that is required is to run

[jira] [Created] (SLING-6062) Make it simple to run Jenkins jobs locally

Robert Munteanu created SLING-6062: -- Summary: Make it simple to run Jenkins jobs locally Key: SLING-6062 URL: https://issues.apache.org/jira/browse/SLING-6062 Project: Sling Issue Type:

Re: Clarification on https://sling.apache.org/documentation/the-sling-engine/url-decomposition.html

> Hi Bertrand, I agree that referencing test cases is for sure good and > validating those assumptions with those as well (if that is not yet the > case). Currently though I have troubles to find the according code. > The selector, extension and suffix handling is in >

Re: Clarification on https://sling.apache.org/documentation/the-sling-engine/url-decomposition.html

Hi Bertrand, I agree that referencing test cases is for sure good and validating those assumptions with those as well (if that is not yet the case). Currently though I have troubles to find the according code. The selector, extension and suffix handling is in

Re: [VOTE] Release Apache Sling Testing Clients 1.0.0, Apache Sling Server Setup Tools 1.0.0 and Apache Sling Testing Rules 1.0.0

+1 regards, Karl On Mon, Sep 19, 2016 at 4:54 PM, Andrei Dulvac wrote: > Hi, > > These are the first releases for these three modules that depend on > each other and there is no explicit component yet. > > Staging repository:https://repository.apache.org/content/ >

Re: [VOTE] Name pattern for system users

It sounds like [a] is the safer option. [a] +1 regards, Karl On Tue, Sep 20, 2016 at 9:38 AM, Bertrand Delacretaz wrote: > On Sat, Sep 17, 2016 at 3:14 PM, Oliver Lietz > wrote: > > ...Closing this vote without result due to poor attendance...

[jira] [Commented] (SLING-6007) XSSFilterImpl should move to new ResourceChangeListener API

[ https://issues.apache.org/jira/browse/SLING-6007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15506027#comment-15506027 ] abdul hameed pathan commented on SLING-6007: Fixed > XSSFilterImpl should move to new

[jira] [Updated] (SLING-5998) NewJobSender should move to new ResourceChangeListener API

[ https://issues.apache.org/jira/browse/SLING-5998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-5998: Fix Version/s: Event 4.2.0 > NewJobSender should move to new ResourceChangeListener API >

Re: Clarification on https://sling.apache.org/documentation/the-sling-engine/url-decomposition.html

Hi Konrad, On Mon, Sep 19, 2016 at 11:37 AM, Konrad Windszus wrote: > ...So basically we have to distinguish between existing and non existing > resource paths... Even if someone knew these details off the top of their head (which I don't) IMO the only sane way to document

Re: [VOTE] Name pattern for system users

On Sat, Sep 17, 2016 at 3:14 PM, Oliver Lietz wrote: > ...Closing this vote without result due to poor attendance... Sorry about that, I missed it. I'm also +1 for >> [a] dashes only -Bertrand

Re: CI alternatives for Sling (was: [i18n] IT Tests failing in reactor build)

Hi, On Mon, Sep 19, 2016 at 10:26 PM, Robert Munteanu wrote: > ...Another benefit is that if a contributor wants to reproduce a problem > on Jenkins, all the effort that is required is to run Jenkins via > docker, install a couple of plugins, create the seed job and all the >