[jira] [Commented] (SLING-6350) MountByFS does not work if the Provider Root mounts below /libs or /apps and has more than 2 slashes

[ https://issues.apache.org/jira/browse/SLING-6350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15728133#comment-15728133 ] Bertrand Delacretaz commented on SLING-6350: Good catch, thanks for this Sandr

[jira] [Created] (SLING-6372) OSGi Mocks - Correctly handle static, greedy references

Francesco Mari created SLING-6372: - Summary: OSGi Mocks - Correctly handle static, greedy references Key: SLING-6372 URL: https://issues.apache.org/jira/browse/SLING-6372 Project: Sling Issue

[jira] [Commented] (SLING-6350) MountByFS does not work if the Provider Root mounts below /libs or /apps and has more than 2 slashes

[ https://issues.apache.org/jira/browse/SLING-6350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15728141#comment-15728141 ] Bertrand Delacretaz commented on SLING-6350: Linking to SLING-5909, [~radu.cot

[jira] [Updated] (SLING-6372) OSGi Mocks - Correctly handle static, greedy references

[ https://issues.apache.org/jira/browse/SLING-6372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert updated SLING-6372: -- Affects Version/s: Testing OSGi Mock 1.9.0 Testing OSGi Mock 2.2.0

[jira] [Updated] (SLING-6372) OSGi Mocks - Correctly handle static, greedy references

[ https://issues.apache.org/jira/browse/SLING-6372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert updated SLING-6372: -- Labels: mocks (was: ) > OSGi Mocks - Correctly handle static, greedy references > -

Re: Automatic cleanup of lingering ResourceResolver's

Hi Konrad The only way I can imagine this to be implemented is by fully(!) wrapping the JCR API and maintain a reference to originating ResourceResolver in each object (e.g. Session, Node etc). IMHO this is not worthwhile, as it opens a large can of worms. Imagine you want to cast Session to Jack

[jira] [Commented] (SLING-6357) Allow to extend LoginAdminWhitelist with multiple configurations

[ https://issues.apache.org/jira/browse/SLING-6357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15728501#comment-15728501 ] Julian Sedding commented on SLING-6357: --- Fixed in [r1773046|https://svn.apache.org/r

[jira] [Comment Edited] (SLING-6357) Allow to extend LoginAdminWhitelist with multiple configurations

[ https://issues.apache.org/jira/browse/SLING-6357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15728501#comment-15728501 ] Julian Sedding edited comment on SLING-6357 at 12/7/16 11:19 AM: ---

Re: Jenkins build became unstable: sling-launchpad-builder-1.8 #345

On Wed, 2016-12-07 at 11:33 +, Apache Jenkins Server wrote: > See > The launchpad has started failing with the latest changes from jcr.base, which are related to SLING-6357. http://svn.apache.org/viewvc?view=revision&revision

[jira] [Commented] (SLING-6364) FsResourceProvider wrongly (?) changed service property => mountByFS via Maven Plugin broken

[ https://issues.apache.org/jira/browse/SLING-6364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15728751#comment-15728751 ] Sandro Boehme commented on SLING-6364: -- Thanks for the changes [~sseif...@pro-vision.

[jira] [Commented] (SLING-6357) Allow to extend LoginAdminWhitelist with multiple configurations

[ https://issues.apache.org/jira/browse/SLING-6357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15728769#comment-15728769 ] Julian Sedding commented on SLING-6357: --- Changed implementation to always register t

Re: Jenkins build became unstable: sling-launchpad-builder-1.8 #345

Hi Robert It looks like it is a timing issue again. The repository gets used, before all whitelist configurations are available. The repo was registered synchronously in this case, which prevented any additional services from being registered until the repo was made available. The stack-traces act

[jira] [Commented] (SLING-6350) MountByFS does not work if the Provider Root mounts below /libs or /apps and has more than 2 slashes

[ https://issues.apache.org/jira/browse/SLING-6350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15728848#comment-15728848 ] Sandro Boehme commented on SLING-6350: -- If we just replace {{**}} in the pattern with

[jira] [Commented] (SLING-5991) [SCD] Evaluate avoiding to buffer the whole packages before streaming

[ https://issues.apache.org/jira/browse/SLING-5991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15728852#comment-15728852 ] Tommaso Teofili commented on SLING-5991: [~marett], I had an offline discussion wi

[jira] [Commented] (SLING-6350) MountByFS does not work if the Provider Root mounts below /libs or /apps and has more than 2 slashes

[ https://issues.apache.org/jira/browse/SLING-6350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15728866#comment-15728866 ] Bertrand Delacretaz commented on SLING-6350: Oops, the .../5/6 test was not wh

Re: Jenkins build became unstable: sling-launchpad-builder-1.8 #345

The last run looks better. It failed, but after the maven run completed successfully. I think it's a jenkins issue now. Regards Julian On Wed, Dec 7, 2016 at 2:33 PM, Julian Sedding wrote: > Hi Robert > > It looks like it is a timing issue again. The repository gets used, > before all whitelist

[jira] [Commented] (SLING-6350) MountByFS does not work if the Provider Root mounts below /libs or /apps and has more than 2 slashes

[ https://issues.apache.org/jira/browse/SLING-6350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15728932#comment-15728932 ] Bertrand Delacretaz commented on SLING-6350: I have refactored the tests in ht

[jira] [Commented] (SLING-6350) MountByFS does not work if the Provider Root mounts below /libs or /apps and has more than 2 slashes

[ https://issues.apache.org/jira/browse/SLING-6350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15728950#comment-15728950 ] Bertrand Delacretaz commented on SLING-6350: SLING-5837 is where this was init

[jira] [Updated] (SLING-6350) MountByFS does not work if the Provider Root mounts below /libs or /apps and has more than 2 slashes

[ https://issues.apache.org/jira/browse/SLING-6350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz updated SLING-6350: --- Attachment: testing-with-ant.patch I have attached {{testing-with-ant.patch}} which us

[jira] [Created] (SLING-6373) Context-Aware Config: Allow alternative configuration bucket names

Stefan Seifert created SLING-6373: - Summary: Context-Aware Config: Allow alternative configuration bucket names Key: SLING-6373 URL: https://issues.apache.org/jira/browse/SLING-6373 Project: Sling

[jira] [Updated] (SLING-6350) Incorrect matching in Path class causes MountByFS to fail (more than 2 slashes fails)

[ https://issues.apache.org/jira/browse/SLING-6350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz updated SLING-6350: --- Summary: Incorrect matching in Path class causes MountByFS to fail (more than 2 slashe

[jira] [Commented] (SLING-5991) [SCD] Evaluate avoiding to buffer the whole packages before streaming

[ https://issues.apache.org/jira/browse/SLING-5991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15729181#comment-15729181 ] Timothee Maret commented on SLING-5991: --- Thanks [~teofili] & [~simone.tripodi] for l

[jira] [Resolved] (SLING-6373) Context-Aware Config: Allow alternative configuration bucket names

[ https://issues.apache.org/jira/browse/SLING-6373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert resolved SLING-6373. --- Resolution: Fixed Completed: At revision: 1773130 > Context-Aware Config: Allow alternativ

[jira] [Resolved] (SLING-6374) Context-Aware Config: Allow to control property order in annotation classes

[ https://issues.apache.org/jira/browse/SLING-6374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert resolved SLING-6374. --- Resolution: Fixed Completed: At revision: 1773149 > Context-Aware Config: Allow to control

[jira] [Created] (SLING-6374) Context-Aware Config: Allow to control property order in annotation classes

Stefan Seifert created SLING-6374: - Summary: Context-Aware Config: Allow to control property order in annotation classes Key: SLING-6374 URL: https://issues.apache.org/jira/browse/SLING-6374 Project:

[jira] [Commented] (SLING-3270) html-generator to support html5

[ https://issues.apache.org/jira/browse/SLING-3270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15730302#comment-15730302 ] Ben Fortuna commented on SLING-3270: This issue still affects Sling Rewriter 1.1.2.

[jira] [Commented] (SLING-5745) Provide a button to clear all registered entities and reinstall those

[ https://issues.apache.org/jira/browse/SLING-5745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15730412#comment-15730412 ] Alexander Klimetschek commented on SLING-5745: -- +1 We just had such a situat

[jira] [Comment Edited] (SLING-5745) Provide a button to clear all registered entities and reinstall those

[ https://issues.apache.org/jira/browse/SLING-5745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15730412#comment-15730412 ] Alexander Klimetschek edited comment on SLING-5745 at 12/8/16 12:24 AM:

[jira] [Comment Edited] (SLING-3270) html-generator to support html5

[ https://issues.apache.org/jira/browse/SLING-3270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15730878#comment-15730878 ] Ben Fortuna edited comment on SLING-3270 at 12/8/16 2:34 AM: -

[jira] [Commented] (SLING-3270) html-generator to support html5

[ https://issues.apache.org/jira/browse/SLING-3270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15730878#comment-15730878 ] Ben Fortuna commented on SLING-3270: After further investigation I think this is an is

[jira] [Comment Edited] (SLING-3270) html-generator to support html5

[ https://issues.apache.org/jira/browse/SLING-3270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15730878#comment-15730878 ] Ben Fortuna edited comment on SLING-3270 at 12/8/16 2:36 AM: -

Re: Automatic cleanup of lingering ResourceResolver's

You are probably right that this is not that easy to detect and basically there are always cases which you would not be able to detect. Therefore I propose to at least log a big WARN in case a resolver has been closed by the finalizer thread in https://github.com/apache/sling/blob/trunk/bundles

[jira] [Created] (SLING-6375) Log a warning in case a resource resolver is closed by the Sling RR Finalizer thread

Konrad Windszus created SLING-6375: -- Summary: Log a warning in case a resource resolver is closed by the Sling RR Finalizer thread Key: SLING-6375 URL: https://issues.apache.org/jira/browse/SLING-6375

Re: Automatic cleanup of lingering ResourceResolver's

I created https://issues.apache.org/jira/browse/SLING-6375 for logging a WARN. > On 8 Dec 2016, at 07:59, Konrad Windszus wrote: > > You are probably right that this is not that easy to detect and basically > there are always cases which you would not be able to detect. > > Therefore I propose