Build failed in Jenkins: sling-trunk-1.6 #3049

See https://builds.apache.org/job/sling-trunk-1.6/3049/changes Changes: [olli] SLING-3017 improve Karaf integration tests * update bndlib [olli] SLING-3821 run launchpad integration tests against Sling on Karaf * update and add supporting bundles [olli] reflect sling-auth-openid and

Re: [VOTE] Release Apache Sling Installer Configuration Factory 1.1.2

On Thursday 12 February 2015 03:24:13 Carsten Ziegeler wrote: Hi, We solved 1 issue in this release: https://issues.apache.org/jira/browse/SLING-4410 +1 O.

Re: [VOTE] Release Apache Sling Resource Merger 1.2.6

+1 Cheers, Stefan On 2/12/15 9:33 AM, Robert Munteanu romb...@apache.org wrote: +1 Robert On Thu, 2015-02-12 at 08:09 +0100, Carsten Ziegeler wrote: +1 Carsten Am 12.02.15 um 03:23 schrieb Carsten Ziegeler: Hi, We solved 1 issue in this release:

[jira] [Updated] (SLING-4413) :applyTo should send 403 instead of 500 when operation fails

[ https://issues.apache.org/jira/browse/SLING-4413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Krapf updated SLING-4413: -- Summary: :applyTo should send 403 instead of 500 when operation fails (was: :applyTo should send 403

[jira] [Commented] (SLING-4413) :applyTo should send 403 instead of 500 when operation fails

[ https://issues.apache.org/jira/browse/SLING-4413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14318050#comment-14318050 ] Ian Boston commented on SLING-4413: --- [~fmeschbe] Thank you for the clarification. I

Re: Using adapters on Sling startup

On 12.02.2015, at 15:15, Alexander Klimetschek aklim...@adobe.com wrote: An adaptTo-only example is the sling ResourceCollectionManager that you can only retrieve via resourceResolver.adaptTo(), but there is no corresponding service. Should I create an issue? Correcting: it is a service

Re: Using adapters on Sling startup

I was just reminded of another problem: adaptTo (especially within service code) makes it hard to write unit tests. It's hard to mock. An adaptTo-only example is the sling ResourceCollectionManager that you can only retrieve via resourceResolver.adaptTo(), but there is no corresponding

Re: [VOTE] Release Apache Sling Installer Configuration Factory 1.1.2

+1 Robert On Thu, 2015-02-12 at 08:09 +0100, Carsten Ziegeler wrote: +1 Carsten Am 12.02.15 um 03:24 schrieb Carsten Ziegeler: Hi, We solved 1 issue in this release: https://issues.apache.org/jira/browse/SLING-4410 Staging repository:

[jira] [Created] (SLING-4414) :applyTo should only apply to requested resource (and below)

Lars Krapf created SLING-4414: - Summary: :applyTo should only apply to requested resource (and below) Key: SLING-4414 URL: https://issues.apache.org/jira/browse/SLING-4414 Project: Sling Issue

[jira] [Created] (SLING-4415) :applyTo should not display changeLog (when operation fails)

Lars Krapf created SLING-4415: - Summary: :applyTo should not display changeLog (when operation fails) Key: SLING-4415 URL: https://issues.apache.org/jira/browse/SLING-4415 Project: Sling Issue

[jira] [Commented] (SLING-848) Support getting versioned resources by using uri path parameters

[ https://issues.apache.org/jira/browse/SLING-848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14317924#comment-14317924 ] Tomek Rękawek commented on SLING-848: - Thanks for the feedback! {quote} I had a brief

[jira] [Updated] (SLING-848) Support getting versioned resources by using uri path parameters

[ https://issues.apache.org/jira/browse/SLING-848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomek Rękawek updated SLING-848: Attachment: SLING-848-metadata.patch Support getting versioned resources by using uri path

[jira] [Created] (SLING-4411) provide Oak features

Oliver Lietz created SLING-4411: --- Summary: provide Oak features Key: SLING-4411 URL: https://issues.apache.org/jira/browse/SLING-4411 Project: Sling Issue Type: New Feature

[jira] [Comment Edited] (SLING-848) Support getting versioned resources by using uri path parameters

[ https://issues.apache.org/jira/browse/SLING-848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14317924#comment-14317924 ] Tomek Rękawek edited comment on SLING-848 at 2/12/15 10:02 AM:

[jira] [Updated] (SLING-4318) Sling resource API does not expose any versioning features - bounty offered.

[ https://issues.apache.org/jira/browse/SLING-4318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomek Rękawek updated SLING-4318: - Fix Version/s: Servlets POST 2.3.8 Sling resource API does not expose any versioning features -

[jira] [Created] (SLING-4413) :applyTo should send 403 instead of 500 when operation fails

Lars Krapf created SLING-4413: - Summary: :applyTo should send 403 instead of 500 when operation fails Key: SLING-4413 URL: https://issues.apache.org/jira/browse/SLING-4413 Project: Sling Issue

[jira] [Commented] (SLING-4413) :applyTo should send 403 instead of 500 when operation fails

[ https://issues.apache.org/jira/browse/SLING-4413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14317931#comment-14317931 ] Felix Meschberger commented on SLING-4413: -- [~ianeboston] This was the subject of

[jira] [Commented] (SLING-848) Support getting versioned resources by using uri path parameters

[ https://issues.apache.org/jira/browse/SLING-848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14317934#comment-14317934 ] Carsten Ziegeler commented on SLING-848: [~tomek.rekawek] Patch lgtm Support

Re: [VOTE] Release Apache Sling Resource Merger 1.2.6

On Thursday 12 February 2015 03:23:40 Carsten Ziegeler wrote: Hi, We solved 1 issue in this release: https://issues.apache.org/jira/browse/SLING-4398 +1 O.

Re: [VOTE] Release Apache Sling Authentication Service 1.3.6

On Wednesday 11 February 2015 12:39:20 Antonio Sanso wrote: Hi, We solved 1 issue in this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12329064 +1 O.

[jira] [Commented] (SLING-4413) :applyTo should send 403 instead of 500 when operation fails

[ https://issues.apache.org/jira/browse/SLING-4413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14317920#comment-14317920 ] Ian Boston commented on SLING-4413: --- I cant find the discussion on dev@sling.apache.org,

[jira] [Updated] (SLING-4416) Improve HC Message/Status if a HC implementation throws an exception

[ https://issues.apache.org/jira/browse/SLING-4416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Georg Henzler updated SLING-4416: - Attachment: SLING-4416-Improved-Exception-Handling.patch Improve HC Message/Status if a HC

[jira] [Created] (SLING-4416) Improve HC Message/Status if a HC implementation throws an exception

Georg Henzler created SLING-4416: Summary: Improve HC Message/Status if a HC implementation throws an exception Key: SLING-4416 URL: https://issues.apache.org/jira/browse/SLING-4416 Project: Sling

[jira] [Updated] (SLING-848) Support getting versioned resources by using uri path parameters

[ https://issues.apache.org/jira/browse/SLING-848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-848: --- Fix Version/s: (was: Resource Resolver 1.1.14) Resource Resolver 1.2.0

[jira] [Commented] (SLING-848) Support getting versioned resources by using uri path parameters

[ https://issues.apache.org/jira/browse/SLING-848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14318233#comment-14318233 ] Tomek Rękawek commented on SLING-848: - I'll merge it as soon as I get my account

[jira] [Resolved] (SLING-4406) POJOs stored in the repository might not get recompiled when changed

[ https://issues.apache.org/jira/browse/SLING-4406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu resolved SLING-4406. - Resolution: Fixed POJOs stored in the repository might not get recompiled when changed

[jira] [Resolved] (SLING-4400) The Use-API should return a falsy value if no Use-provider was able to solve the requested object

[ https://issues.apache.org/jira/browse/SLING-4400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu resolved SLING-4400. - Resolution: Fixed The Use-API should return a falsy value if no Use-provider was able to solve

[jira] [Resolved] (SLING-4372) The use of finalize in ResourceResolver leads to performance issues

[ https://issues.apache.org/jira/browse/SLING-4372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-4372. - Resolution: Fixed The use of finalize in ResourceResolver leads to performance issues

Re: Applying SLING-4372 (fix for a potential memory leak)

Hello Carsten, On Thu, Feb 12, 2015 at 2:56 PM, Carsten Ziegeler cziege...@apache.org wrote: Therefore I plan to temporarily revert SLING-848 in that module, release the fix, and reapply the changes. My idea is to do this tomorrow morning if no one objects. (I cut create a branch for this, but

[jira] [Commented] (SLING-4372) The use of finalize in ResourceResolver leads to performance issues

[ https://issues.apache.org/jira/browse/SLING-4372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14318202#comment-14318202 ] Carsten Ziegeler commented on SLING-4372: - [~fmeschbe] We have that, it's just

[jira] [Commented] (SLING-4413) :applyTo should send 403 instead of 500 when operation fails

[ https://issues.apache.org/jira/browse/SLING-4413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14318098#comment-14318098 ] Felix Meschberger commented on SLING-4413: -- [~ianeboston] Sounds like a plan ;-)

[jira] [Comment Edited] (SLING-4372) The use of finalize in ResourceResolver leads to performance issues

[ https://issues.apache.org/jira/browse/SLING-4372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14318166#comment-14318166 ] Felix Meschberger edited comment on SLING-4372 at 2/12/15 1:18 PM:

[jira] [Commented] (SLING-4372) The use of finalize in ResourceResolver leads to performance issues

[ https://issues.apache.org/jira/browse/SLING-4372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14318166#comment-14318166 ] Felix Meschberger commented on SLING-4372: -- Looks good so far, except that I

[jira] [Commented] (SLING-4372) The use of finalize in ResourceResolver leads to performance issues

[ https://issues.apache.org/jira/browse/SLING-4372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14318185#comment-14318185 ] Carsten Ziegeler commented on SLING-4372: - [~fmeschbe] Thanks - yes, I wanted to

Jenkins build is back to normal : sling-trunk-1.6 #3050

See https://builds.apache.org/job/sling-trunk-1.6/3050/changes

Applying SLING-4372 (fix for a potential memory leak)

Hi SLING-4372 is dealing with a potential memory leak of the resource resolver module wrt to using the finalize method. I've fixed the issue with removing the finalize method and using references. It seems this problem is effecting our users lately (although that code is in there for a long

Build failed in Jenkins: sling-contrib-1.6 #1543

See https://builds.apache.org/job/sling-contrib-1.6/1543/changes Changes: [olli] SLING-4411 provide Oak features * add workaround for tika-sling -- [...truncated 9936 lines...] [INFO] Reserved port 52740 for http.port [INFO] [INFO] ---

Build failed in Jenkins: sling-trunk-1.7 #1438

See https://builds.apache.org/job/sling-trunk-1.7/1438/changes Changes: [cziegeler] SLING-4372 : The use of finalize in ResourceResolver leads to performance issues [olli] SLING-4411 provide Oak features * add workaround for tika-sling -- [...truncated

[jira] [Commented] (SLING-3735) support JNDI lookup in JDBC DataSource Provider

[ https://issues.apache.org/jira/browse/SLING-3735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14318188#comment-14318188 ] Julian Reschke commented on SLING-3735: --- It appears we'll have the same problem with

[jira] [Commented] (SLING-4372) The use of finalize in ResourceResolver leads to performance issues

[ https://issues.apache.org/jira/browse/SLING-4372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14318192#comment-14318192 ] Felix Meschberger commented on SLING-4372: -- I see. Then maybe we should consider

Jenkins build is back to normal : sling-trunk-1.7 #1440

See https://builds.apache.org/job/sling-trunk-1.7/1440/changes

Re: [VOTE] Release Apache Sling Resource Merger 1.2.6

+1 Robert On Thu, 2015-02-12 at 08:09 +0100, Carsten Ziegeler wrote: +1 Carsten Am 12.02.15 um 03:23 schrieb Carsten Ziegeler: Hi, We solved 1 issue in this release: https://issues.apache.org/jira/browse/SLING-4398 Staging repository:

[jira] [Created] (SLING-4412) upgrade Karaf to 4.0

Oliver Lietz created SLING-4412: --- Summary: upgrade Karaf to 4.0 Key: SLING-4412 URL: https://issues.apache.org/jira/browse/SLING-4412 Project: Sling Issue Type: Improvement