[jira] [Commented] (SLING-5602) The Discovery module does not work any more after a ResourceResolverFactory reactivation

[ https://issues.apache.org/jira/browse/SLING-5602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15199354#comment-15199354 ] Stefan Egli commented on SLING-5602: sounds good what I saw just now as another potential lead is

[jira] [Commented] (SLING-5614) Ignore the avro-maven-plugin in Eclipse

[ https://issues.apache.org/jira/browse/SLING-5614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15199562#comment-15199562 ] Robert Munteanu commented on SLING-5614: Nothing changes for the Maven builds. It's just for not

[jira] [Commented] (SLING-5560) Delay job processing at startup to avoid unnecessary stale job handling

[ https://issues.apache.org/jira/browse/SLING-5560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15197594#comment-15197594 ] Carsten Ziegeler commented on SLING-5560: - JobManagerConfiguration.backgroundLoadDelay was used

[jira] [Commented] (SLING-5612) AssertCalendar needlessly compares timezone offsets

[ https://issues.apache.org/jira/browse/SLING-5612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15197253#comment-15197253 ] Robert Munteanu commented on SLING-5612: Looks good to me, thanks for looking into this >

[jira] [Assigned] (SLING-5617) Add missing JSR305 annotations to ResourceProvider

[ https://issues.apache.org/jira/browse/SLING-5617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus reassigned SLING-5617: -- Assignee: Konrad Windszus > Add missing JSR305 annotations to ResourceProvider >

Re: Trunk Build Failure

On Wed, 2016-03-16 at 17:01 -0700, Andreas Schaefer Sr. wrote: > There is another issue I encountered. The RAT plugin is complaining > about IntelliJ Module files (*.iml) files. > > I did include the exclude for **/*.iml but that is only local. I will > include the change to the Parent POM inside

Re: [RESULT[VOTE] Release Apache Sling Maven Sling Plugin 2.1.8

Konrad Windszus wrote > Hi, > > The vote has passed with the following result : > > +1 (binding): Robert Munteanu, Carsten Ziegeler, Stefan Seifert > > I will promote the artifacts to the central Maven repository. > Could some PMC member please move the artifacts to dist? Done Thanks Carsten

Re: [RT] Improve resource type handling

I like the proposal and definitely agree with the idea of deprecating Resource.getResourceSuperType(), it seems confusing and I've never seen it actually used. Just to confirm, regarding the flat list comment, you just mean that the list of components can be cached in a list structure, not that

Re: [RT] Improve resource type handling

Maybe we should tackle this in steps. From what I heard so far, it seems we can agree on: a) forget about Resource#getResourceSuperType. This method is ignored from now on (and deprecated) How about having a dedicated service, like: d) we create a service which has three methods // get

Re: [RT] Improve resource type handling

Daniel Klco wrote > I like the proposal and definitely agree with the idea of deprecating > Resource.getResourceSuperType(), it seems confusing and I've never seen it > actually used. > > Just to confirm, regarding the flat list comment, you just mean that the > list of components can be cached

Re: [RT] Improve resource type handling

Justin Edelson wrote > > I guess I'm not really understanding the advantage of this flat list (which > wouldn't be a single flat list, but multiple flat lists). What is the the > difference between > > /apps/myco/components/bar > /libs/myco/components/bar > > and > >

[jira] [Comment Edited] (SLING-5614) Ignore the avro-maven-plugin in Eclipse

[ https://issues.apache.org/jira/browse/SLING-5614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15199452#comment-15199452 ] Tommaso Teofili edited comment on SLING-5614 at 3/17/16 1:00 PM: - I see,

Re: [RT] Improve resource type handling

I know I am talking out of AEM experience, but I don’t see why one would only go for a flat resourceSuperType list? The most simple example here where that would have massive consequences is in how you would build a page. At this moment you have a basepage, and X child pages which all have the

Re: [RT] Improve resource type handling

Hi, On Fri, Mar 18, 2016 at 5:03 AM Carsten Ziegeler wrote: > Oliver Lietz wrote > > On Friday 18 March 2016 08:08:55 Carsten Ziegeler wrote: > >> Hi, > > > > Hi Carsten, > > > >> in the past years we added a lot of things here and there which over > >> time resulted in

Re: [RT] Improve resource type handling

Roy Teeuwen wrote > I know I am talking out of AEM experience, but I don’t see why one would only > go for a flat resourceSuperType list? > > The most simple example here where that would have massive consequences is in > how you would build a page. > At this moment you have a basepage, and X

[jira] [Commented] (SLING-5602) The Discovery module does not work any more after a ResourceResolverFactory reactivation

[ https://issues.apache.org/jira/browse/SLING-5602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15199908#comment-15199908 ] Carsten Ziegeler commented on SLING-5602: - I think I found the problem: the resource resolver

[jira] [Created] (SLING-5619) 3 IT failures in org.apache.sling.distribution.it

Robert Munteanu created SLING-5619: -- Summary: 3 IT failures in org.apache.sling.distribution.it Key: SLING-5619 URL: https://issues.apache.org/jira/browse/SLING-5619 Project: Sling Issue

Re: Trunk Build Failure

On Thursday 17 March 2016 09:52:13 Andreas Schaefer Sr. wrote: > Ok, took some time to reproduce but it fails in the "Apache Sling Testing > Modules Reactor” module. > > [INFO] Rat check: Summary of files. Unapproved: 3 unknown: 3 generated: 0 > approved: 1 license. > > Rat.txt: > >

[jira] [Resolved] (SLING-5619) 3 IT failures in org.apache.sling.distribution.it

[ https://issues.apache.org/jira/browse/SLING-5619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marius Petria resolved SLING-5619. -- Resolution: Fixed Assignee: Marius Petria (was: Tommaso Teofili) Fix Version/s:

[jira] [Updated] (SLING-5560) Delay job processing at startup to avoid unnecessary stale job handling

[ https://issues.apache.org/jira/browse/SLING-5560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Egli updated SLING-5560: --- Attachment: SLING-5560.patch Attached [^SLING-5560.patch] as a suggested implementation of the

[jira] [Updated] (SLING-5617) Add missing JSR305 annotations to ResourceProvider

[ https://issues.apache.org/jira/browse/SLING-5617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-5617: --- Description: Currently the {{o.a.s.spi.resource.provider.ResourceProvider}} is lacking some

Re: [GitHub] sling pull request: Pull Request for Eclipse Independent Resource ...

Created a JIRA ticket for this: https://issues.apache.org/jira/browse/SLING-5618 Cheers - Andy Schaefer > On Mar 16, 2016, at 10:06 PM, schaefa wrote: > > GitHub user schaefa opened a pull request: > >

[jira] [Closed] (SLING-5559) Improve WebDAV support for installing a bundle

[ https://issues.apache.org/jira/browse/SLING-5559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus closed SLING-5559. -- > Improve WebDAV support for installing a bundle > -- >

[jira] [Commented] (SLING-5602) The Discovery module does not work any more after a ResourceResolverFactory reactivation

[ https://issues.apache.org/jira/browse/SLING-5602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15199451#comment-15199451 ] Carsten Ziegeler commented on SLING-5602: - I've readded the old logic, except for the 2 second

[jira] [Commented] (SLING-5560) Delay job processing at startup to avoid unnecessary stale job handling

[ https://issues.apache.org/jira/browse/SLING-5560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15201142#comment-15201142 ] Carsten Ziegeler commented on SLING-5560: - [~egli] The patch lgtm, +1 > Delay job processing at

Re: [RT] Improve resource type handling

On Friday 18 March 2016 08:08:55 Carsten Ziegeler wrote: > Hi, Hi Carsten, > in the past years we added a lot of things here and there which over > time resulted in cruft and sometimes hard to understand / debug > problems. In order to have an even better framework which is easier to > manage

[RT] Improve resource type handling

Hi, in the past years we added a lot of things here and there which over time resulted in cruft and sometimes hard to understand / debug problems. In order to have an even better framework which is easier to manage but also scales better for the things to come, we should get rid of this

[jira] [Commented] (SLING-5614) Ignore the avro-maven-plugin in Eclipse

[ https://issues.apache.org/jira/browse/SLING-5614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15199459#comment-15199459 ] Robert Munteanu commented on SLING-5614: Right, the change is in the parent pom ( see fix version

[jira] [Created] (SLING-5614) Ignore the avro-maven-plugin in Eclipse

Robert Munteanu created SLING-5614: -- Summary: Ignore the avro-maven-plugin in Eclipse Key: SLING-5614 URL: https://issues.apache.org/jira/browse/SLING-5614 Project: Sling Issue Type:

[jira] [Commented] (SLING-5614) Ignore the avro-maven-plugin in Eclipse

[ https://issues.apache.org/jira/browse/SLING-5614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15199450#comment-15199450 ] Robert Munteanu commented on SLING-5614: When you import the project in Eclipse, an error is

[jira] [Commented] (SLING-5602) The Discovery module does not work any more after a ResourceResolverFactory reactivation

[ https://issues.apache.org/jira/browse/SLING-5602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15199296#comment-15199296 ] Carsten Ziegeler commented on SLING-5602: - "then I see handlers getting removed from the new

Re: [RT] Improve resource type handling

Hi, On Sat, Mar 19, 2016 at 6:11 AM Carsten Ziegeler wrote: > Justin Edelson wrote > > > > I guess I'm not really understanding the advantage of this flat list > (which > > wouldn't be a single flat list, but multiple flat lists). What is the the > > difference between > >

[jira] [Commented] (SLING-5602) The Discovery module does not work any more after a ResourceResolverFactory reactivation

[ https://issues.apache.org/jira/browse/SLING-5602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15199234#comment-15199234 ] Stefan Egli commented on SLING-5602: [~cziegeler], to recap the somewhat confusing, nightly comment

[jira] [Updated] (SLING-5577) Distribution package implementation should be independent of serialization

[ https://issues.apache.org/jira/browse/SLING-5577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommaso Teofili updated SLING-5577: --- Attachment: (was: SLING-5577.2.patch) > Distribution package implementation should be

Re: Trunk Build Failure

Ok, took some time to reproduce but it fails in the "Apache Sling Testing Modules Reactor” module. [INFO] Rat check: Summary of files. Unapproved: 3 unknown: 3 generated: 0 approved: 1 license. Rat.txt: *** Unapproved licenses:

Re: [RT] Improve resource type handling

For me it would help a lot to quickly reconsider the current situation. As far as I know resource super types are used for two different things in Sling right now: 1. Script resolution: Influences which script is being picked up (initially or via includes from other scripts), documented in

[jira] [Commented] (SLING-5612) AssertCalendar needlessly compares timezone offsets

[ https://issues.apache.org/jira/browse/SLING-5612?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15199332#comment-15199332 ] Joel Richard commented on SLING-5612: - [~bdelacretaz], [~rombert], the reason why I had to change this

[jira] [Created] (SLING-5618) Pull Request for Eclipse Independent Resource Change Command Factory

Andreas Schaefer created SLING-5618: --- Summary: Pull Request for Eclipse Independent Resource Change Command Factory Key: SLING-5618 URL: https://issues.apache.org/jira/browse/SLING-5618 Project:

Re: Trunk Build Failure

On Wednesday 16 March 2016 17:01:01 Andreas Schaefer Sr. wrote: > There is another issue I encountered. The RAT plugin is complaining about > IntelliJ Module files (*.iml) files. > > I did include the exclude for **/*.iml but that is only local. I will > include the change to the Parent POM

Re: Trunk Build Failure

There is another issue I encountered. The RAT plugin is complaining about IntelliJ Module files (*.iml) files. I did include the exclude for **/*.iml but that is only local. I will include the change to the Parent POM inside the latest project but there are other POM files that do not have the

[jira] [Commented] (SLING-5602) The Discovery module does not work any more after a ResourceResolverFactory reactivation

[ https://issues.apache.org/jira/browse/SLING-5602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15199414#comment-15199414 ] Carsten Ziegeler commented on SLING-5602: - I think this is more or less a different form of

[jira] [Commented] (SLING-5602) The Discovery module does not work any more after a ResourceResolverFactory reactivation

[ https://issues.apache.org/jira/browse/SLING-5602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15199337#comment-15199337 ] Carsten Ziegeler commented on SLING-5602: - [~egli] I think as a first step we should restore the

[jira] [Resolved] (SLING-5615) Upgrade pluginMgmt to maven-sling-plugin 2.1.8

[ https://issues.apache.org/jira/browse/SLING-5615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus resolved SLING-5615. Resolution: Fixed Fix Version/s: Parent 27 Fixed with

Large number of Karaf IT failures

Hi, The sling-contrib-1.7 build has a large number of failures caused by the Karaf ITs: org.apache.sling:org.apache.sling.launchpad.karaf-integration-tests: 29/145 org.apache.sling:org.apache.sling.launchpad.karaf-launchpad-oak-tar- integration-tests: 522/527 Can someone look into them?

[jira] [Updated] (SLING-5602) The Discovery module does not work any more after a ResourceResolverFactory reactivation

[ https://issues.apache.org/jira/browse/SLING-5602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Egli updated SLING-5602: --- Assignee: Carsten Ziegeler (was: Stefan Egli) Affects Version/s: (was: Discovery Oak

[jira] [Updated] (SLING-5577) Distribution package implementation should be independent of serialization

[ https://issues.apache.org/jira/browse/SLING-5577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommaso Teofili updated SLING-5577: --- Attachment: SLING-5577.2.patch improved patch: using {{ResourceDistributionPackage}} in

[jira] [Comment Edited] (SLING-5614) Ignore the avro-maven-plugin in Eclipse

[ https://issues.apache.org/jira/browse/SLING-5614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15199452#comment-15199452 ] Tommaso Teofili edited comment on SLING-5614 at 3/17/16 1:02 PM: - I see,

[jira] [Commented] (SLING-5614) Ignore the avro-maven-plugin in Eclipse

[ https://issues.apache.org/jira/browse/SLING-5614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15199469#comment-15199469 ] Konrad Windszus commented on SLING-5614: Since this maven plugin is only used in that one module,

[jira] [Commented] (SLING-5560) Delay job processing at startup to avoid unnecessary stale job handling

[ https://issues.apache.org/jira/browse/SLING-5560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15199356#comment-15199356 ] Chetan Mehrotra commented on SLING-5560: +1 for "simply by single config" as it would be easier

Re: [RT] Improve resource type handling

Oliver Lietz wrote > On Friday 18 March 2016 08:08:55 Carsten Ziegeler wrote: >> Hi, > > Hi Carsten, > >> in the past years we added a lot of things here and there which over >> time resulted in cruft and sometimes hard to understand / debug >> problems. In order to have an even better framework

Re: [RT] Improve resource type handling

Konrad Windszus wrote > For me it would help a lot to quickly reconsider the current situation. > As far as I know resource super types are used for two different things in > Sling right now: > > 1. Script resolution: Influences which script is being picked up (initially > or via includes from

[jira] [Updated] (SLING-5581) Transport doesn't throw an exception if a 400+ status is returned

[ https://issues.apache.org/jira/browse/SLING-5581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommaso Teofili updated SLING-5581: --- Fix Version/s: (was: Content Distribution Core 0.1.14) Content

[jira] [Commented] (SLING-5602) The Discovery module does not work any more after a ResourceResolverFactory reactivation

[ https://issues.apache.org/jira/browse/SLING-5602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15199268#comment-15199268 ] Stefan Egli commented on SLING-5602: [~cziegeler] that didn't help unfortunately. What I do see though

[jira] [Created] (SLING-5615) Upgrade pluginMgmt to maven-sling-plugin 2.1.8

Konrad Windszus created SLING-5615: -- Summary: Upgrade pluginMgmt to maven-sling-plugin 2.1.8 Key: SLING-5615 URL: https://issues.apache.org/jira/browse/SLING-5615 Project: Sling Issue Type:

[jira] [Updated] (SLING-5560) Delay job processing at startup to avoid unnecessary stale job handling

[ https://issues.apache.org/jira/browse/SLING-5560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Egli updated SLING-5560: --- Attachment: SLING-5560.v2.patch bq. yet have to write a separate test class for the new delaying

Re: Build failed in Jenkins: sling-samples-1.7 #231

On Thu, 2016-03-17 at 20:00 +, Apache Jenkins Server wrote: > See > > [ERROR] Failed to execute goal org.apache.rat:apache-rat- > plugin:0.11:check (default) on project > org.apache.sling.sample.slingshot: Too many files with unapproved >

[jira] [Resolved] (SLING-5602) The Discovery module does not work any more after a ResourceResolverFactory reactivation

[ https://issues.apache.org/jira/browse/SLING-5602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-5602. - Resolution: Fixed Ok, let's assume we fixed it > The Discovery module does not work any

[jira] [Updated] (SLING-5617) Add missing JSR305 annotations to ResourceProvider

[ https://issues.apache.org/jira/browse/SLING-5617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-5617: --- Description: Currently the {{o.a.s.spi.resource.provider.ResourceProvider}} is lacking some

[jira] [Reopened] (SLING-5576) Optimize queue items listing for big number of items by using iterators

[ https://issues.apache.org/jira/browse/SLING-5576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marius Petria reopened SLING-5576: -- Reopened as this caused IT failures (see SLING-5619). > Optimize queue items listing for big

[RESULT[VOTE] Release Apache Sling Maven Sling Plugin 2.1.8

Hi, The vote has passed with the following result : +1 (binding): Robert Munteanu, Carsten Ziegeler, Stefan Seifert I will promote the artifacts to the central Maven repository. Could some PMC member please move the artifacts to dist? Thanks for voting, Konrad

[jira] [Resolved] (SLING-5617) Add missing JSR305 annotations to ResourceProvider

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

Re: Welcome Radu Cotescu as a Sling PMC member!

Thank you! @PMC: can you please move my artifacts to dist? ;) Regards, Radu On Thu, 17 Mar 2016 at 16:32 Stefan Egli wrote: > Welcome Radu! :) > > Cheers, > Stefan > > On 17/03/16 15:27, "Bertrand Delacretaz" wrote: > > >Hi Sling community, > >

Re: [RESULT][VOTE] Release Apache Sling Scripting Sightly Engine 1.0.18

On Friday 18 March 2016 10:09:11 Radu Cotescu wrote: > Hi, > > The vote passed with 3 +1 from Robert Munteanu, Carsten Ziegeler and Stefan > Seifert. Please move the artifacts to dist. Thanks, O. > Thanks, > Radu

Re: Trunk Build Failure

Ok, that did the trick. If I get a setup working I will debug it as I had a similar issue (JCR Calendar issues based on timezones) in the past. I also will see if I can reproduce it consistently. But at least I am now good to test my merge for a pull request. Thanks - Andy > On Mar 16, 2016,

Re: Large number of Karaf IT failures

On Thursday 17 March 2016 15:28:51 Robert Munteanu wrote: > Hi, hi Robert, > The sling-contrib-1.7 build has a large number of failures caused by > the Karaf ITs: > > org.apache.sling:org.apache.sling.launchpad.karaf-integration-tests: > 29/145 >

[jira] [Commented] (SLING-5560) Delay job processing at startup to avoid unnecessary stale job handling

[ https://issues.apache.org/jira/browse/SLING-5560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15197535#comment-15197535 ] Stefan Egli commented on SLING-5560: [~chetanm] re bq. 30 sec default (as was the case earlier) I

RE: Welcome Radu Cotescu as a Sling PMC member!

welcome! stefan >-Original Message- >From: Bertrand Delacretaz [mailto:bdelacre...@apache.org] >Sent: Thursday, March 17, 2016 3:27 PM >To: dev >Subject: Welcome Radu Cotescu as a Sling PMC member! > >Hi Sling community, > >I'm pleased to announce that the Sling PMC has just elected Radu

[jira] [Commented] (SLING-5602) The Discovery module does not work any more after a ResourceResolverFactory reactivation

[ https://issues.apache.org/jira/browse/SLING-5602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15199301#comment-15199301 ] Stefan Egli commented on SLING-5602: yes > The Discovery module does not work any more after a

Welcome Radu Cotescu as a Sling PMC member!

Hi Sling community, I'm pleased to announce that the Sling PMC has just elected Radu as a new PMC member, and he has accepted. Radu has been making steady and good contributions to Sling for quite some time, so I think this is very well deserved. Congrats and welcome Radu! -Bertrand

Re: [VOTE] Release Apache Sling Content Distribution Core version 0.1.16

On Fri, 2016-03-18 at 14:09 +, Tommaso Teofili wrote: > Please vote to approve this release: +1 Robert signature.asc Description: This is a digitally signed message part

[jira] [Commented] (SLING-5614) Ignore the avro-maven-plugin in Eclipse

[ https://issues.apache.org/jira/browse/SLING-5614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15199432#comment-15199432 ] Tommaso Teofili commented on SLING-5614: I am not sure I understand, the

[jira] [Commented] (SLING-920) Sling Jenkins setup

[ https://issues.apache.org/jira/browse/SLING-920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15199614#comment-15199614 ] Oliver Lietz commented on SLING-920: with Java 7 there are 2 errors in

[GitHub] sling pull request: Pull Request for Eclipse Independent Resource ...

GitHub user schaefa opened a pull request: https://github.com/apache/sling/pull/130 Pull Request for Eclipse Independent Resource Change Command Factory This pull request provides the New Resource Change Command Factory, its support class and some test classes copied from

Re: [VOTE] Release Apache Sling Content Distribution Core version 0.1.16

+1 Tommaso Il giorno ven 18 mar 2016 alle ore 15:09 Tommaso Teofili < tommaso.teof...@gmail.com> ha scritto: > Hi, > > We solved 2 issues in this release: > https://issues.apache.org/jira/browse/SLING/fixforversion/12335354 > > There are still some outstanding issues: >