Idea: Caching in Sling

Hi all, We are considering to implement a resource-based caching in Sling. I have found some efforts to do something similar in the past, but they all seem to have been either abandoned or do something different from what we have in mind. So it would be great to get some feedback if it this ha

[jira] [Resolved] (SLING-3806) ServerSideScriptsTest.runScripts[0 - installer-duplicate.jsp] test failure

[ https://issues.apache.org/jira/browse/SLING-3806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-3806. - Resolution: Fixed Fix Version/s: Launchpad Testing 7 Moved OCM to contrib and remo

Re: Removing OCM Support from Launchapd

Done, moved to ocm to contrib Carsten 2014-07-29 7:06 GMT+02:00 Antonio Sanso : > +1 > On Jul 28, 2014, at 11:36 AM, Carsten Ziegeler > wrote: > > > Hi, > > > > > > the OCM stuff isn't really used and we never recommend to use it - > however, > > it's still in our launchpad. > > No one has wor

Re: Removing OCM Support from Launchapd

+1 On Jul 28, 2014, at 11:36 AM, Carsten Ziegeler wrote: > Hi, > > > the OCM stuff isn't really used and we never recommend to use it - however, > it's still in our launchpad. > No one has worked on OCM since we left the incubator and looking at the > currently included version and the package

Re: adaptTo and results ....

Hi, I just read this thread and it might be that I do not understand all the reasons behind surfacing exceptions through adaptTo. However, I wanted to share with you a variation of Bertrand¹s initial proposal which allows the consumer of the API to explicitly require an adaptation that throws ex

Jenkins build is unstable: sling-trunk-1.8 » Apache Sling SlingRepository Integration Tests #1

See

Jenkins build is unstable: sling-trunk-1.8 » Apache Sling Resource Resolver #1

See

Build failed in Jenkins: sling-trunk-1.8 #1

See -- [...truncated 20721 lines...] [INFO] Apache Sling Resource Resolver SUCCESS [12.641s] [INFO] Apache Sling System Bundle Extension: Java Transaction API SUCCESS [8.370s] [INFO] A

Jenkins build is unstable: sling-trunk-1.8 » Apache Sling Dynamic Class Loader Support #1

See

Jenkins build is unstable: sling-trunk-1.8 » Apache Sling SLF4J Implementation (Logback) #1

See

Build failed in Jenkins: sling-trunk-1.8 » Apache Sling Scripting Implementation API #1

See -- [INFO] [INFO]

[jira] [Issue Comment Deleted] (SLING-920) Sling Jenkins setup

[ https://issues.apache.org/jira/browse/SLING-920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-920: -- Comment: was deleted (was: I am out of office, back on June 22. regards antonio ) > Sling J

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

[ https://issues.apache.org/jira/browse/SLING-920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14076765#comment-14076765 ] Robert Munteanu commented on SLING-920: --- Created job sling-trunk-1.8 as a copy of sli

Re: Launchpad 7 Release?

On Monday 28 July 2014 14:56:03 Robert Munteanu wrote: > On Sun, Jul 27, 2014 at 1:09 PM, Oliver Lietz wrote: > > On Wednesday 23 July 2014 08:04:00 Carsten Ziegeler wrote: > >> 2014-07-22 23:12 GMT+02:00 Oliver Lietz : > >> > > +1, I think it's important to have a Sling 7 release soon. > >> > >

Re: adaptTo and results ....

You're missing my point. How would your Sightly script indicate that a RuntimeException should be thrown in the first place? Or are you suggesting that Sightly assume that this is always the case? On Mon, Jul 28, 2014 at 12:07 PM, Konrad Windszus wrote: > In my regard in this case a RuntimeExcept

Re: adaptTo and results ....

In my regard in this case a RuntimeException would be fine. That would be propagated correctly to the script level. So whenever a model class has the model annotation and something went wrong during the injection throwing a runtime exception would be correctly propagated and no other option woul

Re: adaptTo and results ....

Hi Konrad, In this case, I don't see how any of the options in this thread would actually help because the code which calls adaptTo() is not under your control. So there would be no way for the caller (i.e. your Sightly script) to indicate that such an exception should be thrown. Regards, Justin

Jenkins build is still unstable: sling-oak-it-1.6 #44

See

Jenkins build is still unstable: sling-oak-it-1.6 » Apache Sling Launchpad Testing #44

See

Re: adaptTo and results ....

I just came up with another example from CQ: In Sightly you can instantiate a model via the use API [1]. Since that logic will first try to adapt from Resource then from Request and as fallback tries to instantiate the class leveraging the default constructor, you won’t get any exceptions in ca

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

See

Jenkins build is back to stable : sling-trunk-1.7 » Apache Sling Launchpad Testing #714

See

Re: Removing OCM Support from Launchapd

+1 On Mon, Jul 28, 2014 at 10:49 AM, Justin Edelson wrote: > Hi, > > On Mon, Jul 28, 2014 at 5:36 AM, Carsten Ziegeler > wrote: > > Hi, > > > > > > the OCM stuff isn't really used and we never recommend to use it - > however, > > it's still in our launchpad. > > No one has worked on OCM since

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

See Changes: [bdelacretaz] Stop framework only if it is active -- [...truncated 4076 lines...] [INFO] Checking legal files in: org.apache.sling.launchpad.karaf-features-0.1.1-SNAPSHOT-sources.

Build failed in Jenkins: sling-contrib-1.6 » Apache Sling Launchpad Karaf - Integration Tests #1189

See -- [INFO] [INFO] ---

Re: Removing OCM Support from Launchapd

Hi, On Mon, Jul 28, 2014 at 5:36 AM, Carsten Ziegeler wrote: > Hi, > > > the OCM stuff isn't really used and we never recommend to use it - however, > it's still in our launchpad. > No one has worked on OCM since we left the incubator and looking at the > currently included version and the packag

[jira] [Created] (SLING-3809) Please upgrade Quartz to 2.2.1 (or later)

Amichai Rothman created SLING-3809: -- Summary: Please upgrade Quartz to 2.2.1 (or later) Key: SLING-3809 URL: https://issues.apache.org/jira/browse/SLING-3809 Project: Sling Issue Type: Impro

[jira] [Created] (SLING-3808) Please add configurable number of job recurrences to whiteboard interface

Amichai Rothman created SLING-3808: -- Summary: Please add configurable number of job recurrences to whiteboard interface Key: SLING-3808 URL: https://issues.apache.org/jira/browse/SLING-3808 Project:

Re: Launchpad 7 Release?

On Sun, Jul 27, 2014 at 1:09 PM, Oliver Lietz wrote: > On Wednesday 23 July 2014 08:04:00 Carsten Ziegeler wrote: >> 2014-07-22 23:12 GMT+02:00 Oliver Lietz : >> > > +1, I think it's important to have a Sling 7 release soon. >> > >> > Yes, but not a half-baked one. We would have even more users co

[jira] [Created] (SLING-3807) Consider adding the Maven central artifact repository by default

Robert Munteanu created SLING-3807: -- Summary: Consider adding the Maven central artifact repository by default Key: SLING-3807 URL: https://issues.apache.org/jira/browse/SLING-3807 Project: Sling

Jenkins build is still unstable: sling-oak-it-1.6 » Apache Sling Launchpad Testing #43

See

Jenkins build is still unstable: sling-oak-it-1.6 #43

See

Re: [VOTE] Release Apache Sling IDE Tooling 1.0.2

We still need another binding vote for this release... On Mon, Jul 28, 2014 at 2:40 PM, Robert Munteanu wrote: > +1 > > Robert > > On Tue, Jul 22, 2014 at 6:57 PM, Stefan Egli wrote: >> okeee :) >> >> On 7/22/14 5:56 PM, "Robert Munteanu" wrote: >> >>>On Tue, Jul 22, 2014 at 6:55 PM, Stefan Egl

Re: [VOTE] Release Apache Sling IDE Tooling 1.0.2

+1 Robert On Tue, Jul 22, 2014 at 6:57 PM, Stefan Egli wrote: > okeee :) > > On 7/22/14 5:56 PM, "Robert Munteanu" wrote: > >>On Tue, Jul 22, 2014 at 6:55 PM, Stefan Egli >>wrote: >>> I think what might me missing is an SVN tag for the release? Or am I >>>just >>> not finding it :S >> >>The re

Re: Removing OCM Support from Launchapd

On Mon, Jul 28, 2014 at 12:37 PM, Bertrand Delacretaz wrote: > On Mon, Jul 28, 2014 at 11:36 AM, Carsten Ziegeler > wrote: >> ...c) remove it from the launchpad and move it to the contrib secion until >> someone who really needs it comes along and fixes it... > > +1, modules that are not current

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

See

Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Launchpad Testing #713

See

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

See Changes: [bdelacretaz] Remove unnecessary snapshot [bdelacretaz] Use CRANKSTART_CONFIG_ID property to avoid creating duplicate factory configs -- [...truncated 6508 lines...] Downloading:

Jenkins build became unstable: sling-contrib-1.6 » Apache Sling Replication Integration Tests #1188

See

Build failed in Jenkins: sling-contrib-1.6 » Apache Sling Launchpad Karaf - Integration Tests #1188

See -- [INFO] [INFO] ---

Jenkins build is still unstable: sling-oak-it-1.6 #42

See

Jenkins build is still unstable: sling-oak-it-1.6 » Apache Sling Launchpad Testing #42

See

[jira] [Commented] (SLING-3786) Add tests and refactor JSON to String conversion

[ https://issues.apache.org/jira/browse/SLING-3786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14076073#comment-14076073 ] Bertrand Delacretaz commented on SLING-3786: Updating our fork would be great

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

See

Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Launchpad Testing #712

See

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

See

[jira] [Commented] (SLING-3786) Add tests and refactor JSON to String conversion

[ https://issues.apache.org/jira/browse/SLING-3786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14076070#comment-14076070 ] Felix Meschberger commented on SLING-3786: -- While I agree with the goal, I doubt

Jenkins build is back to stable : sling-trunk-1.6 » Apache Sling Launchpad Testing #2334

See

[jira] [Resolved] (SLING-3786) Add tests and refactor JSON to String conversion

[ https://issues.apache.org/jira/browse/SLING-3786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz resolved SLING-3786. Resolution: Fixed Refactoring is done, used in SLING-3776, test coverage of the ren

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

See Changes: [bdelacretaz] SLING-3721 - shutdown OSGi framework at JVM exit - based on a patch contributed by Artyom Stetsenko, thanks! [bdelacretaz] Fix constructor access -- [...truncated 4

Jenkins build is back to stable : sling-contrib-1.6 » Apache Sling Replication Integration Tests #1187

See

Build failed in Jenkins: sling-contrib-1.6 » Apache Sling Launchpad Karaf - Integration Tests #1187

See -- [INFO] [INFO] ---

[jira] [Commented] (SLING-3806) ServerSideScriptsTest.runScripts[0 - installer-duplicate.jsp] test failure

[ https://issues.apache.org/jira/browse/SLING-3806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14076049#comment-14076049 ] Carsten Ziegeler commented on SLING-3806: - I've removed the jcr ocm bundle for now

[jira] [Resolved] (SLING-3721) Crankstart does not stop the framework gracefully on exit

[ https://issues.apache.org/jira/browse/SLING-3721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz resolved SLING-3721. Resolution: Fixed Assignee: Bertrand Delacretaz Thanks for your contribution

[jira] [Assigned] (SLING-3806) ServerSideScriptsTest.runScripts[0 - installer-duplicate.jsp] test failure

[ https://issues.apache.org/jira/browse/SLING-3806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned SLING-3806: --- Assignee: Carsten Ziegeler > ServerSideScriptsTest.runScripts[0 - installer-duplicate

Re: Removing OCM Support from Launchapd

On Mon, Jul 28, 2014 at 11:36 AM, Carsten Ziegeler wrote: > ...c) remove it from the launchpad and move it to the contrib secion until > someone who really needs it comes along and fixes it... +1, modules that are not currently maintained belong under contrib. -Bertrand

Removing OCM Support from Launchapd

Hi, the OCM stuff isn't really used and we never recommend to use it - however, it's still in our launchpad. No one has worked on OCM since we left the incubator and looking at the currently included version and the package imports I doubt that it actually really works. While fixing an obvious b

Jenkins build is back to stable : sling-trunk-1.7 » Apache Sling Resource-Based Discovery Service #711

See

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

See

Jenkins build is still unstable: sling-trunk-1.7 » Apache Sling Launchpad Testing #711

See

[jira] [Commented] (SLING-3806) ServerSideScriptsTest.runScripts[0 - installer-duplicate.jsp] test failure

[ https://issues.apache.org/jira/browse/SLING-3806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14076039#comment-14076039 ] Carsten Ziegeler commented on SLING-3806: - I've updated the JCR OCM Bundle to the

[jira] [Updated] (SLING-3806) ServerSideScriptsTest.runScripts[0 - installer-duplicate.jsp] test failure

[ https://issues.apache.org/jira/browse/SLING-3806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-3806: --- Description: {{org.apache.sling.launchpad.webapp.integrationtest.ServerSideScriptsTest.runScr

[jira] [Created] (SLING-3806) ServerSideScriptsTest.runScripts[0 - installer-duplicate.jsp] test failure

Robert Munteanu created SLING-3806: -- Summary: ServerSideScriptsTest.runScripts[0 - installer-duplicate.jsp] test failure Key: SLING-3806 URL: https://issues.apache.org/jira/browse/SLING-3806 Project:

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

See

Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling Launchpad Testing #2333

See

Jenkins build became unstable: sling-trunk-1.7 » Apache Sling Resource-Based Discovery Service #710

See

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

See

Jenkins build became unstable: sling-trunk-1.7 » Apache Sling Launchpad Testing #710

See

Build failed in Jenkins: sling-contrib-1.6 » Apache Sling Launchpad Karaf - Integration Tests #1186

See -- [INFO] [INFO] ---

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

See Changes: [cziegeler] Remove unnecessary annotation [cziegeler] Fields for dynamic references must be volatile [cziegeler] Fields for dynamic references must be volatile [cziegeler] SLING-3805 : Fields for dynamic references mus

Jenkins build became unstable: sling-contrib-1.6 » Apache Sling Replication Integration Tests #1186

See

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

See

Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling Launchpad Testing #2332

See

[jira] [Resolved] (SLING-3805) Fields for dynamic references must be volatile

[ https://issues.apache.org/jira/browse/SLING-3805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-3805. - Resolution: Fixed Fixed in rev 1613901 > Fields for dynamic references must be volatile

[jira] [Created] (SLING-3805) Fields for dynamic references must be volatile

Carsten Ziegeler created SLING-3805: --- Summary: Fields for dynamic references must be volatile Key: SLING-3805 URL: https://issues.apache.org/jira/browse/SLING-3805 Project: Sling Issue Type

[jira] [Resolved] (SLING-3804) Fields for dynamic references must be volatile

[ https://issues.apache.org/jira/browse/SLING-3804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-3804. - Resolution: Fixed Fixed in rev 1613900 > Fields for dynamic references must be volatile

[jira] [Created] (SLING-3804) Fields for dynamic references must be volatile

Carsten Ziegeler created SLING-3804: --- Summary: Fields for dynamic references must be volatile Key: SLING-3804 URL: https://issues.apache.org/jira/browse/SLING-3804 Project: Sling Issue Type

[jira] [Created] (SLING-3803) Fields for dynamic references must be volatile

Carsten Ziegeler created SLING-3803: --- Summary: Fields for dynamic references must be volatile Key: SLING-3803 URL: https://issues.apache.org/jira/browse/SLING-3803 Project: Sling Issue Type

[jira] [Resolved] (SLING-3803) Fields for dynamic references must be volatile

[ https://issues.apache.org/jira/browse/SLING-3803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-3803. - Resolution: Fixed Fixed in rev 1613898 > Fields for dynamic references must be volatile

[jira] [Resolved] (SLING-3802) Fields for dynamic references must be volatile

[ https://issues.apache.org/jira/browse/SLING-3802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-3802. - Resolution: Fixed Fixed in rev 1613895 > Fields for dynamic references must be volatile

[jira] [Updated] (SLING-3802) Fields for dynamic references must be volatile

[ https://issues.apache.org/jira/browse/SLING-3802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-3802: Affects Version/s: (was: Scripting API 2.1.6) Scripting Core 2.0.

[jira] [Created] (SLING-3802) Fields for dynamic references must be volatile

Carsten Ziegeler created SLING-3802: --- Summary: Fields for dynamic references must be volatile Key: SLING-3802 URL: https://issues.apache.org/jira/browse/SLING-3802 Project: Sling Issue Type

[jira] [Updated] (SLING-3802) Fields for dynamic references must be volatile

[ https://issues.apache.org/jira/browse/SLING-3802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-3802: Fix Version/s: (was: Scripting API 2.1.8) Scripting Core 2.0.28 > Fi