Re: Launchpad stable and launchpad unstable

Hi Bertrand, Am 29.11.16 um 13:25 schrieb Bertrand Delacretaz: Hi Sandro, On Mon, Nov 28, 2016 at 11:45 PM, Sandro Boehme wrote: ...If I checkout and build the latest trunk I would expect that the built projects are available at the runtime of the server. This way I can

[jira] [Commented] (SLING-6174) Use Jackrabbit/Oak globbing support

[ https://issues.apache.org/jira/browse/SLING-6174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15706286#comment-15706286 ] Stefan Egli commented on SLING-6174: [~radu.cotescu], jcr.resource is back to rev 1771443 - I've

Re: LoginAdminWhitelist - do we need amendment support like we have for service users?

Sorry, I missed that mail. Thanks for clearing that up. On Tue, Nov 29, 2016 at 1:24 PM Julian Sedding wrote: > Hi Justin > > I asked the same question before[0] and Carsten seemed to be opposed. > > However, after using it a little, I believe it would much better to > have

[jira] [Commented] (SLING-6174) Use Jackrabbit/Oak globbing support

[ https://issues.apache.org/jira/browse/SLING-6174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15706144#comment-15706144 ] Stefan Egli commented on SLING-6174: I think I know what it could be: it indeed requires oak 1.5.14 -

[jira] [Commented] (SLING-6174) Use Jackrabbit/Oak globbing support

[ https://issues.apache.org/jira/browse/SLING-6174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15706133#comment-15706133 ] Stefan Egli commented on SLING-6174: [~radu.cotescu], how are you testing? Is that a unit/it test or

Re: LoginAdminWhitelist - do we need amendment support like we have for service users?

Hi Justin I asked the same question before[0] and Carsten seemed to be opposed. However, after using it a little, I believe it would much better to have amendments (or factory configs). This allows for better re-use and modularisation. With modularisation in this case I mean Sling, products

[jira] [Commented] (SLING-6336) Implement a ResourceResolverWrapper

[ https://issues.apache.org/jira/browse/SLING-6336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15706083#comment-15706083 ] Julian Sedding commented on SLING-6336: --- Thanks! And sorry for the mid-air-collision of our comments

LoginAdminWhitelist - do we need amendment support like we have for service users?

Currently, the LoginAdminWhitelist has a single central configuration. I'm wondering if this is really sustainable or if we need some kind of amendment support like we have for service users? Regards, Justin

[jira] [Commented] (SLING-6336) Implement a ResourceResolverWrapper

[ https://issues.apache.org/jira/browse/SLING-6336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15705977#comment-15705977 ] Radu Cotescu commented on SLING-6336: - [~jsedding], I've corrected the implementation pushed in

[jira] [Commented] (SLING-6174) Use Jackrabbit/Oak globbing support

[ https://issues.apache.org/jira/browse/SLING-6174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15705964#comment-15705964 ] Radu Cotescu commented on SLING-6174: - The patch from https://svn.apache.org/r1771884 seems to have

[jira] [Commented] (SLING-6341) ResourcePath injector does not correctly wraps to array

[ https://issues.apache.org/jira/browse/SLING-6341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15705906#comment-15705906 ] Santiago García Pimentel commented on SLING-6341: - the docs at

[jira] [Commented] (SLING-6341) ResourcePath injector does not correctly wraps to array

[ https://issues.apache.org/jira/browse/SLING-6341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15705902#comment-15705902 ] Santiago García Pimentel commented on SLING-6341: - A potential fix

[GitHub] sling pull request #186: Bugfix/sling 6341

GitHub user santiagozky opened a pull request: https://github.com/apache/sling/pull/186 Bugfix/sling 6341 You can merge this pull request into a Git repository by running: $ git pull https://github.com/santiagozky/sling bugfix/SLING-6341 Alternatively you can review and

[jira] [Created] (SLING-6341) ResourcePath injector does not correctly wraps to array

Santiago García Pimentel created SLING-6341: --- Summary: ResourcePath injector does not correctly wraps to array Key: SLING-6341 URL: https://issues.apache.org/jira/browse/SLING-6341 Project:

[jira] [Resolved] (SLING-6324) MonitoringDistributionPackageBuilder registering of same beans cause exception

[ https://issues.apache.org/jira/browse/SLING-6324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommaso Teofili resolved SLING-6324. Resolution: Fixed > MonitoringDistributionPackageBuilder registering of same beans cause

[jira] [Resolved] (SLING-6339) Clean-up from compiler Warning messages the Distribution Core and ITs source code

[ https://issues.apache.org/jira/browse/SLING-6339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommaso Teofili resolved SLING-6339. Resolution: Fixed thanks Simone, I've applied your patch in r1771915. > Clean-up from

[jira] [Reopened] (SLING-6174) Use Jackrabbit/Oak globbing support

[ https://issues.apache.org/jira/browse/SLING-6174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Egli reopened SLING-6174: reopening, as the pom.xml needs to be set to 1.5.14 really > Use Jackrabbit/Oak globbing support >

[jira] [Commented] (SLING-6174) Use Jackrabbit/Oak globbing support

[ https://issues.apache.org/jira/browse/SLING-6174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15705582#comment-15705582 ] Stefan Egli commented on SLING-6174: [~rombert], oh, I thought it was out already. Thx for spotting!

[jira] [Commented] (SLING-6174) Use Jackrabbit/Oak globbing support

[ https://issues.apache.org/jira/browse/SLING-6174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15705553#comment-15705553 ] Robert Munteanu commented on SLING-6174: [~egli] - but Oak 1.5.14 is not out yet, which means that

[jira] [Commented] (SLING-6174) Use Jackrabbit/Oak globbing support

[ https://issues.apache.org/jira/browse/SLING-6174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15705305#comment-15705305 ] Stefan Egli commented on SLING-6174: And upped oak dependency to 1.5.14 in

[jira] [Commented] (SLING-6305) LoginAdminWhitelist configuration is applied too late

[ https://issues.apache.org/jira/browse/SLING-6305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15705303#comment-15705303 ] Stefan Seifert commented on SLING-6305: --- did more testing on different environments - it fails only

Re: Launchpad stable and launchpad unstable

Hi Sandro, On Mon, Nov 28, 2016 at 11:45 PM, Sandro Boehme wrote: > ...If I checkout and build the latest trunk I would expect that the built > projects are available at the runtime of the server. This way I can set > breakpoints in the debugger, examine the inner workings

New JSON library

Hi, The JSON license has been moved to 'Category X' [1] which means that we can no longer use the org.json library. This has been announced on the legal@ mailing list, please see [2] for the complete picture. We have until 30 Apr 2017 to remove all dependencies and inclusions of the org.json

[jira] [Resolved] (SLING-6174) Use Jackrabbit/Oak globbing support

[ https://issues.apache.org/jira/browse/SLING-6174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Egli resolved SLING-6174. Resolution: Fixed Applied [~cziegeler]'s patch to trunk:

[jira] [Resolved] (SLING-6340) shorten JcrResourceListener.toString

[ https://issues.apache.org/jira/browse/SLING-6340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Egli resolved SLING-6340. Resolution: Fixed done in http://svn.apache.org/viewvc?rev=1771882=rev > shorten

[jira] [Created] (SLING-6340) shorten JcrResourceListener.toString

Stefan Egli created SLING-6340: -- Summary: shorten JcrResourceListener.toString Key: SLING-6340 URL: https://issues.apache.org/jira/browse/SLING-6340 Project: Sling Issue Type: Improvement

[jira] [Updated] (SLING-6339) Clean-up from compiler Warning messages the Distribution Core and ITs source code

[ https://issues.apache.org/jira/browse/SLING-6339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simone Tripodi updated SLING-6339: -- Attachment: SLING-6339.patch Proposed patch fixes the 99% of the warning messages. I have no

[jira] [Created] (SLING-6339) Clean-up from compiler Warning messages the Distribution Core and ITs source code

Simone Tripodi created SLING-6339: - Summary: Clean-up from compiler Warning messages the Distribution Core and ITs source code Key: SLING-6339 URL: https://issues.apache.org/jira/browse/SLING-6339

Re: integration test fail due to LoginAdminWhitelist

On Tue, Nov 29, 2016 at 10:51 AM, Julian Sedding wrote: > ...We need to understand the root cause If debugging doesn't help (because it changes timing) I suggest adding enough debug logs to be able to follow and understand what's happening. Those are useful for

Re: integration test fail due to LoginAdminWhitelist

Setting whitelist.bypass=true exhibits the same failures (bundle NOT whitelisted)[0]. So issues with the regexp can be ruled out as the main cause. I wonder if we should install the startupfilter(disabler) bundles? That might delay the TestClient to wait until the system is (more) ready.

Re: integration test fail due to LoginAdminWhitelist

I mostly agree with Bertrand's interpretation. However, I a config can be applied early (i.e. registered with config admin), but components are still lazily instantiated. Does anyone know if there is a guarantee that components are configured (activated) before they become visible? If there is

Re: integration test fail due to LoginAdminWhitelist

On Mon, Nov 28, 2016 at 10:47 PM, Robert Munteanu wrote: > ...That would be SLING-6305 [1] I guess. ... I haven't debugged deep down yet but intuitively it should be possible to apply very early in the startup phase all the configs that are supplied by the provisioning

Re: What to do about cancelled releases in Jira?

On Mon, Nov 28, 2016 at 9:19 PM, Robert Munteanu wrote: > ... > - move all issues from version N to version N+2 > - delete Jira version N ... +1 -Bertrand