[jira] [Commented] (SLING-3987) move from Subversion to Git

2017-09-12 Thread Oliver Lietz (JIRA)
[ https://issues.apache.org/jira/browse/SLING-3987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16162663#comment-16162663 ] Oliver Lietz commented on SLING-3987: - [~rombert], I had to remove those repos on GitH

[jira] [Commented] (SLING-3987) move from Subversion to Git

2017-09-12 Thread Robert Munteanu (JIRA)
[ https://issues.apache.org/jira/browse/SLING-3987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16162725#comment-16162725 ] Robert Munteanu commented on SLING-3987: [~olli] - Ouch :-) Right, I mean a detac

[jira] [Resolved] (SLING-7099) add csv pipe

2017-09-12 Thread Nicolas Peltier (JIRA)
[ https://issues.apache.org/jira/browse/SLING-7099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Peltier resolved SLING-7099. Resolution: Fixed fixed in r1808090 and r1808091 > add csv pipe > > >

[jira] [Commented] (SLING-3987) move from Subversion to Git

2017-09-12 Thread Oliver Lietz (JIRA)
[ https://issues.apache.org/jira/browse/SLING-3987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16162767#comment-16162767 ] Oliver Lietz commented on SLING-3987: - I didn't try, because I prefer non-crossing com

[jira] [Commented] (SLING-7121) improved scheduler hc log messages

2017-09-12 Thread Stefan Egli (JIRA)
[ https://issues.apache.org/jira/browse/SLING-7121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16162769#comment-16162769 ] Stefan Egli commented on SLING-7121: Improved wording [here|http://svn.apache.org/view

[jira] [Commented] (SLING-3987) move from Subversion to Git

2017-09-12 Thread Robert Munteanu (JIRA)
[ https://issues.apache.org/jira/browse/SLING-3987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16162819#comment-16162819 ] Robert Munteanu commented on SLING-3987: Ack, thanks. Well, we can't have cross-re

[jira] [Comment Edited] (SLING-7121) improved scheduler hc log messages

2017-09-12 Thread Stefan Egli (JIRA)
[ https://issues.apache.org/jira/browse/SLING-7121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16162769#comment-16162769 ] Stefan Egli edited comment on SLING-7121 at 9/12/17 11:38 AM: --

[jira] [Commented] (SLING-3987) move from Subversion to Git

2017-09-12 Thread Oliver Lietz (JIRA)
[ https://issues.apache.org/jira/browse/SLING-3987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16162832#comment-16162832 ] Oliver Lietz commented on SLING-3987: - Parent is just an example and we did bulk updat

[RT] Context-Aware Services - Multitenancy for SPI implementations

2017-09-12 Thread Stefan Seifert
consider the following use case: - an OSGi/Sling-based library provides a SPI interface - applications of multiple tenants are deployed on the same instance - each tenant uses a different content tree, e.g. /content/tenant1 and /content/tenant2 - each tenant's application wants to register a diffe

Re: [RT] Context-Aware Services - Multitenancy for SPI implementations

2017-09-12 Thread Carsten Ziegeler
Hi Stefan this is definitely an interesting approach. I can see the potential, but so far I haven't really seen use cases (which doesn't mean there are non). If I understand correctly, you do the matching based on the path which avoids the need of introducing an explicit concept of a tenant. On t

Re: [RT] Context-Aware Services - Multitenancy for SPI implementations

2017-09-12 Thread Bertrand Delacretaz
Hi, On Tue, Sep 12, 2017 at 7:47 AM, Stefan Seifert wrote: > ...do you have better ideas for configuring the mapping or the > implementation?... I don't know if it's a better idea but here are some thoughts. In my upcoming adaptTo talk I'll mention making resource types multi-tenant, by prefix

[jira] [Assigned] (SLING-7105) Some JSP tests fail under Java 9 - parameterized types are only available if source level is 1.5 or greater

2017-09-12 Thread Robert Munteanu (JIRA)
[ https://issues.apache.org/jira/browse/SLING-7105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu reassigned SLING-7105: -- Assignee: Robert Munteanu > Some JSP tests fail under Java 9 - parameterized types are

[jira] [Updated] (SLING-7105) Some JSP tests fail under Java 9 - parameterized types are only available if source level is 1.5 or greater

2017-09-12 Thread Robert Munteanu (JIRA)
[ https://issues.apache.org/jira/browse/SLING-7105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-7105: --- Fix Version/s: (was: Launchpad Testing 9) Commons Compiler 2.3.2 > Some

[jira] [Updated] (SLING-7105) Some JSP tests fail under Java 9 - parameterized types are only available if source level is 1.5 or greater

2017-09-12 Thread Robert Munteanu (JIRA)
[ https://issues.apache.org/jira/browse/SLING-7105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-7105: --- Component/s: (was: Testing) Commons > Some JSP tests fail under Java 9 -

[jira] [Commented] (SLING-7105) Some JSP tests fail under Java 9 - parameterized types are only available if source level is 1.5 or greater

2017-09-12 Thread Robert Munteanu (JIRA)
[ https://issues.apache.org/jira/browse/SLING-7105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16163548#comment-16163548 ] Robert Munteanu commented on SLING-7105: Actually the problem was a bit less excit

[jira] [Resolved] (SLING-7105) Some JSP tests fail under Java 9 - parameterized types are only available if source level is 1.5 or greater

2017-09-12 Thread Robert Munteanu (JIRA)
[ https://issues.apache.org/jira/browse/SLING-7105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-7105. Resolution: Fixed Fixed in [r1808147|https://svn.apache.org/r1808147] > Some JSP tests fail

[jira] [Resolved] (SLING-7107) Some JSP tests fail under Java 9 - The method getProperty(String) is undefined for the type AdapterType

2017-09-12 Thread Robert Munteanu (JIRA)
[ https://issues.apache.org/jira/browse/SLING-7107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-7107. Resolution: Duplicate > Some JSP tests fail under Java 9 - The method getProperty(String) is

[jira] [Updated] (SLING-7107) Some JSP tests fail under Java 9 - The method getProperty(String) is undefined for the type AdapterType

2017-09-12 Thread Robert Munteanu (JIRA)
[ https://issues.apache.org/jira/browse/SLING-7107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-7107: --- Fix Version/s: (was: Launchpad Testing 9) > Some JSP tests fail under Java 9 - The method

[jira] [Updated] (SLING-7107) Some JSP tests fail under Java 9 - The method getProperty(String) is undefined for the type AdapterType

2017-09-12 Thread Robert Munteanu (JIRA)
[ https://issues.apache.org/jira/browse/SLING-7107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-7107: --- Component/s: (was: Testing) > Some JSP tests fail under Java 9 - The method getProperty(St

[jira] [Updated] (SLING-7105) Some JSP tests fail under Java 9 - parameterized types are only available if source level is 1.5 or greater

2017-09-12 Thread Robert Munteanu (JIRA)
[ https://issues.apache.org/jira/browse/SLING-7105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-7105: --- Fix Version/s: (was: Commons Compiler 2.3.2) Commons Compiler 2.3.4 > S

[VOTE] Release Apache Sling Commons Java Compiler version 2.3.4

2017-09-12 Thread Robert Munteanu
Hi, We solved 1 issue in this release: https://issues.apache.org/jira/projects/SLING/versions/12341614 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1783 You can use this UNIX script to download the release and verify the signatures: http://svn.apache.org/

Re: [VOTE] Release Apache Sling Commons Java Compiler version 2.3.4

2017-09-12 Thread Robert Munteanu
On Tue, 2017-09-12 at 23:04 +0300, Robert Munteanu wrote: > Please vote to approve this release: +1 Robert signature.asc Description: This is a digitally signed message part

[jira] [Closed] (SLING-7111) Compiler creates class files even if compilation fails

2017-09-12 Thread Carsten Ziegeler (JIRA)
[ https://issues.apache.org/jira/browse/SLING-7111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler closed SLING-7111. --- > Compiler creates class files even if compilation fails > ---

Re: [VOTE] Release Apache Sling Commons Java Compiler version 2.3.4

2017-09-12 Thread Carsten Ziegeler
+1   -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org

OAK-6575 - Support for external binary URLs.

2017-09-12 Thread Ian Boston
Hi, Background: OAK-6575 adds support for a Oak DataStore to implement a service implementing org.apache.jackrabbit.oak.api.conversion.URIProvider which converts a JCR Value to a URI. The implementation in OAK-6575 is for the Oak S3 DataStore to convert to a CloudFront signed url as detailed in [

Re: OAK-6575 - Support for external binary URLs.

2017-09-12 Thread Carsten Ziegeler
I think there are two parts to be discussed: a) whether to directly code this into the get servlet b) how to mark the resource as being handled this way I think a) makes sense, it's a central place and allows any resource provider to use it. However, this is also the problem I see :) For each and

Re: OAK-6575 - Support for external binary URLs.

2017-09-12 Thread Ian Boston
Hi, On 12 September 2017 at 17:09, Carsten Ziegeler wrote: > I think there are two parts to be discussed: > a) whether to directly code this into the get servlet > b) how to mark the resource as being handled this way > > I think a) makes sense, it's a central place and allows any resource > pro

Re: OAK-6575 - Support for external binary URLs.

2017-09-12 Thread Carsten Ziegeler
Ian Boston wrote > Hi, > > On 12 September 2017 at 17:09, Carsten Ziegeler > wrote: > > I think there are two parts to be discussed: > a) whether to directly code this into the get servlet > b) how to mark the resource as being handled this way > > I