[jira] [Commented] (SLING-4349) [Sightly] Extend RenderContext to provide access to the ServletResolver resource resolver

[ https://issues.apache.org/jira/browse/SLING-4349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14291816#comment-14291816 ] Felix Meschberger commented on SLING-4349: -- Ref: Discussion on dev@ [\[Sightly\]

[jira] [Assigned] (SLING-4351) Expose distribution log information over http

[ https://issues.apache.org/jira/browse/SLING-4351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marius Petria reassigned SLING-4351: Assignee: Marius Petria Expose distribution log information over http

[jira] [Created] (SLING-4351) Expose distribution log information over http

Marius Petria created SLING-4351: Summary: Expose distribution log information over http Key: SLING-4351 URL: https://issues.apache.org/jira/browse/SLING-4351 Project: Sling Issue Type: New

[jira] [Updated] (SLING-4093) run performance tests to compare with JSP and Sightly

[ https://issues.apache.org/jira/browse/SLING-4093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vlad Bailescu updated SLING-4093: - Attachment: SLING-4093_-_Performance_tests_to_compare_JSP_and_Sightly.patch Added comparative

Jenkins build is back to stable : sling-trunk-1.7 #1369

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

Jenkins build is still unstable: sling-trunk-1.6 #2981

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

[jira] [Created] (SLING-4352) The ResourceResolver passed to SlingScripts should not be closeable

Radu Cotescu created SLING-4352: --- Summary: The ResourceResolver passed to SlingScripts should not be closeable Key: SLING-4352 URL: https://issues.apache.org/jira/browse/SLING-4352 Project: Sling

[jira] [Resolved] (SLING-4349) [Sightly] Extend RenderContext to provide access to the ServletResolver resource resolver

[ https://issues.apache.org/jira/browse/SLING-4349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved SLING-4349. -- Resolution: Fixed Assignee: Felix Meschberger Thanks for providing the patch. I

Jenkins build became unstable: sling-trunk-1.6 #2979

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

Re: Sling CRUD with content versioning, API architecture

On Mon, Jan 26, 2015 at 1:45 PM, Bertrand Delacretaz bdelacre...@apache.org wrote: ...The request-aware method is already marked as deprecated since 2.2.0 and there is a Javadoc stating that this method won't be invoked anymore Ok, you're right that this is not needed then. I

Jenkins build is still unstable: sling-trunk-1.6 #2980

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

Jenkins build became unstable: sling-trunk-1.8 #659

See https://builds.apache.org/job/sling-trunk-1.8/659/changes

[jira] [Updated] (SLING-4337) Sightly should only log errors from use providers if none of the use providers succeeded

[ https://issues.apache.org/jira/browse/SLING-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu updated SLING-4337: Attachment: SLING-4337.patch I attached the patch provided by [~justinedelson]

Re: Sling CRUD with content versioning, API architecture

On Mon, Jan 26, 2015 at 12:32 PM, Tomek Rękawek tomasz.reka...@cognifide.com wrote: On Mon, Jan 26, 2015 at 11:57 AM, Bertrand Delacretaz bdelacre...@apache.org wrote: ...Shouldn't PRP also extend getResource(ResourceResolver, HttpServletRequest, String) ? ...The request-aware method is

Jenkins build became unstable: sling-trunk-1.7 #1368

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

Jenkins build is still unstable: sling-trunk-1.8 #660

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

[jira] [Updated] (SLING-4351) Expose distribution log information over http

[ https://issues.apache.org/jira/browse/SLING-4351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marius Petria updated SLING-4351: - Component/s: Distribution Expose distribution log information over http

[jira] [Commented] (SLING-4337) Sightly should only log errors from use providers if none of the use providers succeeded

[ https://issues.apache.org/jira/browse/SLING-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14291930#comment-14291930 ] Ilyas Türkben commented on SLING-4337: -- [~radu.cotescu] when the patch will be

Jenkins build is back to stable : sling-trunk-1.7 #1371

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

Jenkins build is still unstable: sling-trunk-1.6 #2982

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

[jira] [Comment Edited] (SLING-4337) Sightly should only log errors from use providers if none of the use providers succeeded

[ https://issues.apache.org/jira/browse/SLING-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14292025#comment-14292025 ] Felix Meschberger edited comment on SLING-4337 at 1/26/15 4:26 PM:

[jira] [Comment Edited] (SLING-4337) Sightly should only log errors from use providers if none of the use providers succeeded

[ https://issues.apache.org/jira/browse/SLING-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14292025#comment-14292025 ] Felix Meschberger edited comment on SLING-4337 at 1/26/15 4:27 PM:

[jira] [Resolved] (SLING-4337) Sightly should only log errors from use providers if none of the use providers succeeded

[ https://issues.apache.org/jira/browse/SLING-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved SLING-4337. -- Resolution: Fixed Assignee: Felix Meschberger Thanks for providing the patch. I

Jenkins build became unstable: sling-trunk-1.7 #1370

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

[jira] [Resolved] (SLING-3832) on 'discovery bindTopologyEventListener' an INIT event can be sent after CHANGING/CHANGED

[ https://issues.apache.org/jira/browse/SLING-3832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Egli resolved SLING-3832. Resolution: Fixed Assignee: Stefan Egli on 'discovery bindTopologyEventListener' an INIT

[jira] [Updated] (SLING-4337) Sightly should only log errors from use providers if none of the use providers succeeded

[ https://issues.apache.org/jira/browse/SLING-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu updated SLING-4337: Attachment: (was: SLING-4337.patch) Sightly should only log errors from use providers if none

[jira] [Resolved] (SLING-4351) Expose distribution log information over http

[ https://issues.apache.org/jira/browse/SLING-4351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marius Petria resolved SLING-4351. -- Resolution: Fixed Expose distribution log information over http

[jira] [Updated] (SLING-4352) The ResourceResolver passed to SlingScripts should not be closeable

[ https://issues.apache.org/jira/browse/SLING-4352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu updated SLING-4352: Description: The {{SlingServletResolver}} uses an administrative resource resolver

Jenkins build is back to stable : sling-trunk-1.6 #2983

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

Jenkins build became unstable: sling-trunk-1.6 #2976

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

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=14291629#comment-14291629 ] Bertrand Delacretaz commented on SLING-4318: Should the JSON output include a

Re: [discussion] allow Script Engines to also render components based on paths

On Mon, Jan 26, 2015 at 10:39 AM, Jeff Young j...@adobe.com wrote: ...If we do use a property, it should be inherited so it can be put on entire sub-trees easily... Yes that's my idea, just put sling:script=thymeleaf on /apps/foo to indicate that thymeleaf is the preferred engine for scripts

[jira] [Updated] (SLING-4349) [Sightly] Extend RenderContext to provide access to the ServletResolver resource resolver

[ https://issues.apache.org/jira/browse/SLING-4349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu updated SLING-4349: Attachment: SLING-4349.patch The attached patch ([^SLING-4349.patch]) provides the following

[jira] [Resolved] (SLING-4302) ClusterTest.testStableClusterId sometimes fails

[ https://issues.apache.org/jira/browse/SLING-4302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Egli resolved SLING-4302. Resolution: Fixed test made more robust ClusterTest.testStableClusterId sometimes fails

Re: [discussion] allow Script Engines to also render components based on paths

Hi Am 26.01.2015 um 11:03 schrieb Bertrand Delacretaz bdelacre...@apache.org: On Mon, Jan 26, 2015 at 10:39 AM, Jeff Young j...@adobe.com wrote: ...If we do use a property, it should be inherited so it can be put on entire sub-trees easily... Yes that's my idea, just put

Re: [discussion] allow Script Engines to also render components based on paths

On Mon, Jan 26, 2015 at 11:25 AM, Felix Meschberger fmesc...@adobe.com wrote: ...Maybe we should add somewhat more to be able to declare a mapping from extension to concrete script language name,... sling:script = [ „html=thymeleaf“, „js=nashorn“ ] Ok, so this would

Jenkins build became unstable: sling-trunk-1.7 #1364

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

Re: Sling CRUD with content versioning, API architecture

Hi Tomek, This looks very interesting, thanks! I have commented in SLING-4318, about making the SLING-848 URIs discoverable. About https://github.com/apache/sling/pull/57, the URI parameters, is there an alternative that avoids modifying the ResourceProvider interface? There's probably lots of

Jenkins build became unstable: sling-trunk-1.8 #656

See https://builds.apache.org/job/sling-trunk-1.8/656/changes

Jenkins build is still unstable: sling-trunk-1.7 #1365

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

Re: [VOTE] Release Apache Sling JCR Resource 2.4.4

+1, Cheers, Stefan On 1/26/15 8:04 AM, Carsten Ziegeler cziege...@apache.org wrote: Anyone? Am 23.01.15 um 22:20 schrieb Carsten Ziegeler: Hi, we solved one critical issue https://issues.apache.org/jira/browse/SLING-4343 Staging repository:

Re: [discussion] allow Script Engines to also render components based on paths

On Sat, Jan 24, 2015 at 12:34 PM, Justin Edelson jus...@justinedelson.com wrote: ...Only the developer knows how to map their scripts to the right engine And the developer creates scripts under /apps/foo for project foo, so it makes absolute sense to set a sling:script property on /apps/foo

Re: Sling CRUD with content versioning, API architecture

Hello, the topic has been moved from the Sling Users List, as we went from support to development :) On Thu, Jan 15, 2015 at 3:08 PM, Bertrand Delacretaz wrote: On Thu, Jan 15, 2015 at 3:38 PM, Robert Munteanu rombert@... wrote: ...You _might_ be able to get away with creating a new

[jira] [Resolved] (SLING-4131) Migrate discovery.impl to httpclient 4.x

[ https://issues.apache.org/jira/browse/SLING-4131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Egli resolved SLING-4131. Resolution: Fixed Migrate discovery.impl to httpclient 4.x

[jira] [Resolved] (SLING-4224) Avoid NPE after HeartbeatHandler deactivation

[ https://issues.apache.org/jira/browse/SLING-4224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Egli resolved SLING-4224. Resolution: Fixed Avoid NPE after HeartbeatHandler deactivation

[jira] [Assigned] (SLING-4224) Avoid NPE after HeartbeatHandler deactivation

[ https://issues.apache.org/jira/browse/SLING-4224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Egli reassigned SLING-4224: -- Assignee: Stefan Egli Avoid NPE after HeartbeatHandler deactivation

Re: [VOTE] Release Apache Sling Launchpad Base 4.6.0-2.5.6

+1, Cheers, Stefan On 1/26/15 8:04 AM, Carsten Ziegeler cziege...@apache.org wrote: Anyone? Am 22.01.15 um 22:12 schrieb Carsten Ziegeler: Hi, we solved one major deadlock issue https://issues.apache.org/jira/browse/SLING/fixforversion/12329291 Staging repository:

[jira] [Created] (SLING-4350) minor typo in log message

Stefan Egli created SLING-4350: -- Summary: minor typo in log message Key: SLING-4350 URL: https://issues.apache.org/jira/browse/SLING-4350 Project: Sling Issue Type: Bug Components:

[jira] [Resolved] (SLING-4350) minor typo in log message

[ https://issues.apache.org/jira/browse/SLING-4350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Egli resolved SLING-4350. Resolution: Fixed minor typo in log message - Key:

[jira] [Resolved] (SLING-4139) regression: stale topology announcements possible after crash/reconfig

[ https://issues.apache.org/jira/browse/SLING-4139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Egli resolved SLING-4139. Resolution: Fixed fixed : topology announcements that are no longer active (thus no longer in the

[jira] [Resolved] (SLING-3726) Topology contains duplicated instances

[ https://issues.apache.org/jira/browse/SLING-3726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Egli resolved SLING-3726. Resolution: Fixed While there is still the possibility - from a code point of view - that you can

Re: [VOTE] Release Apache Sling JCR Resource 2.4.4

+1 Robert On Mon, Jan 26, 2015 at 10:43 AM, Stefan Egli stefane...@apache.org wrote: +1, Cheers, Stefan On 1/26/15 8:04 AM, Carsten Ziegeler cziege...@apache.org wrote: Anyone? Am 23.01.15 um 22:20 schrieb Carsten Ziegeler: Hi, we solved one critical issue

[jira] [Resolved] (SLING-3296) Occasional NPE in EstablishedClusterView

[ https://issues.apache.org/jira/browse/SLING-3296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Egli resolved SLING-3296. Resolution: Fixed Fix Version/s: (was: Discovery Impl 1.0.14)

Re: [discussion] allow Script Engines to also render components based on paths

I'm in agreement with Justin and Bertrand that the developer (and not the administrator) is the right person to author this information. I'm on the fence regarding whether to put it in the file or use a property. (If we do use a property, it should be inherited so it can be put on entire

[jira] [Created] (SLING-4349) [Sightly] Extend RenderContext to provide access to the ServletResolver resource resolver

Radu Cotescu created SLING-4349: --- Summary: [Sightly] Extend RenderContext to provide access to the ServletResolver resource resolver Key: SLING-4349 URL: https://issues.apache.org/jira/browse/SLING-4349

[VOTE RESULT] Release Apache Sling JCR Resource 2.4.4

The vote passed with three binding +1 votes Thanks Carsten -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org

[VOTE RESULT] Release Apache Sling Launchpad Base 4.6.0-2.5.6

The vote passed with three binding +1 votes Thanks Carsten -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org

Re: Sling CRUD with content versioning, API architecture

Hello Bertrand, On Mon, Jan 26, 2015 at 11:02 AM, Bertrand Delacretaz bdelacre...@apache.org wrote: I have commented in SLING-4318, about making the SLING-848 URIs discoverable. Thanks for the suggestion, I'll move the versions to a new subtree so we can extend the JSON in the future.

[jira] [Resolved] (SLING-4300) TopologyTest sometimes fails

[ https://issues.apache.org/jira/browse/SLING-4300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Egli resolved SLING-4300. Resolution: Fixed looked good in recent testruns, marking closed for now TopologyTest sometimes

[jira] [Resolved] (SLING-4303) ClusterLoadTest.testFourInstances sometimes fails

[ https://issues.apache.org/jira/browse/SLING-4303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Egli resolved SLING-4303. Resolution: Fixed test made more robust ClusterLoadTest.testFourInstances sometimes fails

Re: Sling CRUD with content versioning, API architecture

Hi Bertrand, On Mon, Jan 26, 2015 at 11:57 AM, Bertrand Delacretaz bdelacre...@apache.org wrote: How about creating ParametrizableResourceProvider with the extended get() method? If there are some parameters and the ResourceProvider implements also PRP, the resource resolver will

[jira] [Commented] (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:comment-tabpanelfocusedCommentId=14291725#comment-14291725 ] Tomek Rękawek commented on SLING-4318: -- I added the wrapping object. Sling resource

[jira] [Comment Edited] (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:comment-tabpanelfocusedCommentId=14289243#comment-14289243 ] Tomek Rękawek edited comment on SLING-4318 at 1/26/15 11:38 AM:

Jenkins build is back to stable : sling-trunk-1.6 #2978

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

[jira] [Closed] (SLING-4335) Deadlock on startup due to SLING-4197

[ https://issues.apache.org/jira/browse/SLING-4335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-4335. --- Deadlock on startup due to SLING-4197 -

[jira] [Closed] (SLING-4343) Iterator from JcrResourceProvider.queryResources() keeps returning same value on next()

[ https://issues.apache.org/jira/browse/SLING-4343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-4343. --- Iterator from JcrResourceProvider.queryResources() keeps returning same value on next()

Jenkins build is still unstable: sling-trunk-1.6 #2977

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

Re: Sling CRUD with content versioning, API architecture

Hi Tomek, On Mon, Jan 26, 2015 at 11:43 AM, Tomek Rękawek tomasz.reka...@cognifide.com wrote: On Mon, Jan 26, 2015 at 11:02 AM, Bertrand Delacretaz bdelacre...@apache.org wrote: About https://github.com/apache/sling/pull/57, the URI parameters, is there an alternative that avoids modifying

Jenkins build is still unstable: sling-trunk-1.8 #657

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

Jenkins build is back to stable : sling-trunk-1.7 #1366

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

[jira] [Comment Edited] (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:comment-tabpanelfocusedCommentId=14291725#comment-14291725 ] Tomek Rękawek edited comment on SLING-4318 at 1/26/15 11:38 AM:

Re: [discussion] allow Script Engines to also render components based on paths

Hi Am 26.01.2015 um 11:29 schrieb Bertrand Delacretaz bdelacre...@apache.org: On Mon, Jan 26, 2015 at 11:25 AM, Felix Meschberger fmesc...@adobe.com wrote: ...Maybe we should add somewhat more to be able to declare a mapping from extension to concrete script language name,...

Jenkins build is back to stable : sling-trunk-1.8 #658

See https://builds.apache.org/job/sling-trunk-1.8/658/changes

[jira] [Resolved] (SLING-4239) Resource Editor :: improved add node dialog, added cheat sheets, new background image

[ https://issues.apache.org/jira/browse/SLING-4239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandro Boehme resolved SLING-4239. -- Resolution: Fixed Resource Editor :: improved add node dialog, added cheat sheets, new

[jira] [Resolved] (SLING-4245) Resource Editor :: add node dialog, cheat sheets :: icons for the select2 lib

[ https://issues.apache.org/jira/browse/SLING-4245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandro Boehme resolved SLING-4245. -- Resolution: Fixed patch applied by myself Resource Editor :: add node dialog, cheat sheets ::

[jira] [Commented] (SLING-4239) Resource Editor :: improved add node dialog, added cheat sheets, new background image

[ https://issues.apache.org/jira/browse/SLING-4239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14292655#comment-14292655 ] Sandro Boehme commented on SLING-4239: -- Patches of the subtasks applied by myself in

[jira] [Resolved] (SLING-4243) Resource Editor :: add node dialog, cheat sheets :: plain text changes

[ https://issues.apache.org/jira/browse/SLING-4243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandro Boehme resolved SLING-4243. -- Resolution: Fixed patch applied by myself Resource Editor :: add node dialog, cheat sheets ::

[jira] [Resolved] (SLING-4244) Resource Editor :: add node dialog, cheat sheets :: cheat sheet icons

[ https://issues.apache.org/jira/browse/SLING-4244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sandro Boehme resolved SLING-4244. -- Resolution: Fixed patch applied by myself Resource Editor :: add node dialog, cheat sheets ::

[jira] [Commented] (SLING-4205) Clarify the licensing of resourceeditor images, fonts etc.

[ https://issues.apache.org/jira/browse/SLING-4205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14292667#comment-14292667 ] Sandro Boehme commented on SLING-4205: -- I committed 'AddNodeDialogPatch-alu.gif.txt'

[jira] [Commented] (SLING-4205) Clarify the licensing of resourceeditor images, fonts etc.

[ https://issues.apache.org/jira/browse/SLING-4205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14292676#comment-14292676 ] Sandro Boehme commented on SLING-4205: -- Ah [~bdelacretaz] is assigned. Please don't