Re: Releasing the repoinit parser and JCR modules?

2016-07-30 Thread Oliver Lietz
On Friday 29 July 2016 14:45:19 Bertrand Delacretaz wrote: > Hi, Hi Bertrand, > I have implemented the new "register namespace" and "register > nodetypes" statements for the repoinit language, documented at [1]. > > Does the syntax work for you guys, and are you otherwise ok with me > releasing

Re: [Context Aware Configs] Merging?

2016-07-30 Thread Roy Teeuwen
+1 for me too, one of the real life examples that I have in most of my projects is that you have a site /content/mysite and you have some languages like /content/mysite/en and /content/mysite/fr It would be nice to put all your global mysite configs on /content/mysite, but still have the

[jira] [Resolved] (SLING-5930) Provide repoinit statements as bundle resource

2016-07-30 Thread Oliver Lietz (JIRA)
[ https://issues.apache.org/jira/browse/SLING-5930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz resolved SLING-5930. - Resolution: Done [r1754607|https://svn.apache.org/r1754607] > Provide repoinit statements as

[jira] [Created] (SLING-5930) Provide repoinit statements as bundle resource

2016-07-30 Thread Oliver Lietz (JIRA)
Oliver Lietz created SLING-5930: --- Summary: Provide repoinit statements as bundle resource Key: SLING-5930 URL: https://issues.apache.org/jira/browse/SLING-5930 Project: Sling Issue Type: New

[jira] [Resolved] (SLING-5896) Include org.apache.felix.webconsole.plugins.ds in SlingOptions.webconsole

2016-07-30 Thread Oliver Lietz (JIRA)
[ https://issues.apache.org/jira/browse/SLING-5896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz resolved SLING-5896. - Resolution: Invalid > Include org.apache.felix.webconsole.plugins.ds in SlingOptions.webconsole >

[jira] [Updated] (SLING-5896) Include org.apache.felix.webconsole.plugins.ds in SlingOptions.webconsole

2016-07-30 Thread Oliver Lietz (JIRA)
[ https://issues.apache.org/jira/browse/SLING-5896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz updated SLING-5896: Fix Version/s: (was: Testing Pax Exam 0.0.2) > Include org.apache.felix.webconsole.plugins.ds

[jira] [Commented] (SLING-5896) Include org.apache.felix.webconsole.plugins.ds in SlingOptions.webconsole

2016-07-30 Thread Oliver Lietz (JIRA)
[ https://issues.apache.org/jira/browse/SLING-5896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15400550#comment-15400550 ] Oliver Lietz commented on SLING-5896: - Plugin should be added by developer when required for

[jira] [Resolved] (SLING-5929) Provide Pax URL and Pax URL Classpath as Options for Pax Exam

2016-07-30 Thread Oliver Lietz (JIRA)
[ https://issues.apache.org/jira/browse/SLING-5929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz resolved SLING-5929. - Resolution: Done [r1754597|https://svn.apache.org/r1754597] > Provide Pax URL and Pax URL

Sling Health Check Executor Optimisation

2016-07-30 Thread Georg Henzler
As it turned out the HC executor wastes 50ms by using a hardcoded Thread.sleep() which does not sound like a lot (and often it's not a problem), but some use cases it's not ideal (e.g. when calling it from a load balancer). The pull request in SLING-5874 fixes it... Carsten or Betrand, the two

[jira] [Created] (SLING-5929) Provide Pax URL and Pax URL Classpath as Options for Pax Exam

2016-07-30 Thread Oliver Lietz (JIRA)
Oliver Lietz created SLING-5929: --- Summary: Provide Pax URL and Pax URL Classpath as Options for Pax Exam Key: SLING-5929 URL: https://issues.apache.org/jira/browse/SLING-5929 Project: Sling

Sling Oak Restrictions - Release 1.0.0 now?

2016-07-30 Thread Georg Henzler
Hi all, with SLING-5768/SLING-5891 fixed and the documentation in https://sling.apache.org/documentation/bundles/sling-oak-restrictions.html we have everything needed to cut a first release IMHO - could someone take care of it? Thanks & Regards Georg

Re: [Context Aware Configs] Merging?

2016-07-30 Thread Georg Henzler
A big +1 from my side to support merging (all the way down to property level) from the very first release. IMHO it's not that hard to implement and it saves a lot of frustration downstream. On 2016-07-29 17:10, Justin Edelson wrote: Allow me to disagree. This lack of merging is actually one of