[jira] [Resolved] (SLING-3468) Standalone Launchpad does not start on trunk

[ https://issues.apache.org/jira/browse/SLING-3468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-3468. - Resolution: Fixed Assignee: Carsten Ziegeler Thanks for the patch David, it's appli

Re: [VOTE] Release Apache Sling

FYI - vote email is Missing JIRA link: https://issues.apache.org/jira/browse/SLING/fixforversion/12326520/ +1 On Thu, Mar 20, 2014 at 8:29 PM, Carsten Ziegeler wrote: > Hi, > > this vote is about the release of > > Apache Sling JCR Resource 2.3.6 > > This release is required to match the new Sli

Re: [VOTE] Release Apache Sling Resource Merger 1.1.2

+1 On Thu, Mar 20, 2014 at 8:30 PM, Carsten Ziegeler wrote: > Hi, > > this vote is about the release of > > Apache Sling Resource Merger 1.1.2 > https://issues.apache.org/jira/browse/SLING/fixforversion/12326447 > > Staging repository: > https://repository.apache.org/content/repositories/orgapach

Re: [VOTE] Release JMX Resource Provider 1.0.2

+1 On Thu, Mar 20, 2014 at 8:32 PM, Carsten Ziegeler wrote: > Hi, > > this vote is about the release of > > Apache Sling JMX Resource Provider 1.0.2 > https://issues.apache.org/jira/browse/SLING/fixforversion/12326446 > > Staging repository: > https://repository.apache.org/content/repositories/or

Re: [VOTE] Release Apache Sling API 2.7.0

+1 On Thu, Mar 20, 2014 at 8:28 PM, Carsten Ziegeler wrote: > Hi, > > this vote is about the release of > > Apache Sling API 2.7.0 > https://issues.apache.org/jira/browse/SLING/fixforversion/12326284 > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-1036

[jira] [Updated] (SLING-3451) Support for deep reads from a value map

[ https://issues.apache.org/jira/browse/SLING-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-3451: Fix Version/s: JCR Resource 2.3.6 > Support for deep reads from a value map > -

[VOTE] Release JMX Resource Provider 1.0.2

Hi, this vote is about the release of Apache Sling JMX Resource Provider 1.0.2 https://issues.apache.org/jira/browse/SLING/fixforversion/12326446 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1039 You can use this UNIX script to download the release and v

[VOTE] Release Apache Sling Resource Merger 1.1.2

Hi, this vote is about the release of Apache Sling Resource Merger 1.1.2 https://issues.apache.org/jira/browse/SLING/fixforversion/12326447 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1038 You can use this UNIX script to download the release and verify

[VOTE] Release Apache Sling

Hi, this vote is about the release of Apache Sling JCR Resource 2.3.6 This release is required to match the new Sling API 2.7.0 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1037 You can use this UNIX script to download the release and verify the signatu

[VOTE] Release Apache Sling API 2.7.0

Hi, this vote is about the release of Apache Sling API 2.7.0 https://issues.apache.org/jira/browse/SLING/fixforversion/12326284 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1036 You can use this UNIX script to download the release and verify the signatur

Re: Removing sling:features support from the resource resolver?

I really would llke to get a release of the resource resolver out and I don't want to have an experimental feature in a release. Once we have something out, we have to support it. Carsten 2014-03-20 11:56 GMT-07:00 Justin Edelson : > This sounds mildly silly, but why don't we leave the feature

[jira] [Commented] (SLING-3464) The DynamicClassLoaderManager doesn't reload classes when a bundle transitions from STARTED to RESOLVED

[ https://issues.apache.org/jira/browse/SLING-3464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13942252#comment-13942252 ] Justin Edelson commented on SLING-3464: --- I'm not sure how this is inconsistent. I do

Re: [jira] [Created] (SLING-3464) The DynamicClassLoaderManager doesn't reload classes when a bundle transitions from STARTED to RESOLVED

Hi, Could someone please take a look at this and confirm if we're talking about a bug or a feature? Thanks, Radu On Wednesday, March 19, 2014, Radu Cotescu (JIRA) wrote: > Radu Cotescu created SLING-3464: > --- > > Summary: The DynamicClassLoaderMan

Re: Removing sling:features support from the resource resolver?

This sounds mildly silly, but why don't we leave the feature in, but only enable it based on the presence of a particular feature flag? Shipping an "experimental" feature which can be toggled on or off seems like a perfect use case for feature flags. WDYT? Justin On Thu, Mar 20, 2014 at 2:26 PM

Re: Removing sling:features support from the resource resolver?

I think, let's remove this stuff from the resource resolver for now, experiment with the flags in general and once we have a better picture, we can add it back again - either in the same way or totally different. We could also move the code to a branch or whiteboard so people can install the experi

Re: Removing sling:features support from the resource resolver?

The post problem is fixed, btw - features are only evaluated for GET/HEAD requests Carsten 2014-03-20 8:32 GMT-07:00 Justin Edelson : > Hi, > > On Thu, Mar 20, 2014 at 11:19 AM, Bertrand Delacretaz > wrote: > > Hi, > > > > On Thu, Mar 20, 2014 at 4:16 PM, Justin Edelson > > wrote: > >> ...Fea

Re: Performance and stability of Sling Models

Ah, good point. Yes, I think we should have a custom @Inject-like meta-annotation. Can't think of a good name now :) On Thu, Mar 20, 2014 at 11:48 AM, Konrad Windszus wrote: > Hi Justin, > Unfortunately to annotate an annotation with @Inject is not allowed. The > annotation is only allowed on m

Re: Performance and stability of Sling Models

Hi Justin, Unfortunately to annotate an annotation with @Inject is not allowed. The annotation is only allowed on methods, constructors and fields. Do you think that it would be acceptable to come up with another inject-annotation which is also allowed on annotations? That should just be an alter

Re: Removing sling:features support from the resource resolver?

Hi, On Thu, Mar 20, 2014 at 11:19 AM, Bertrand Delacretaz wrote: > Hi, > > On Thu, Mar 20, 2014 at 4:16 PM, Justin Edelson > wrote: >> ...Feature Flags may look similar to >> ACLs, but they are useful for a different set of use cases than ACLs. >> Feature flags are about "orchestrating" features

Re: Removing sling:features support from the resource resolver?

Hi, On Thu, Mar 20, 2014 at 4:16 PM, Justin Edelson wrote: > ...Feature Flags may look similar to > ACLs, but they are useful for a different set of use cases than ACLs. > Feature flags are about "orchestrating" features. Resource access is > *one* part of this orchestration, but it is not the on

Re: Removing sling:features support from the resource resolver?

Hi, FWIW, when this feature was first added, I had some misgivings for similar reasons (ACL confusion, caching, etc.). After having used it, however, I have changed my mind. Feature Flags may look similar to ACLs, but they are useful for a different set of use cases than ACLs. Feature flags are abo

[jira] [Commented] (SLING-3470) Add Sling Replication ITs for all the exposed resources

[ https://issues.apache.org/jira/browse/SLING-3470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13941795#comment-13941795 ] Tommaso Teofili commented on SLING-3470: improved covered resources in r1579646 (e

[jira] [Commented] (SLING-3471) Add Sling Replication IT for commands

[ https://issues.apache.org/jira/browse/SLING-3471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13941796#comment-13941796 ] Tommaso Teofili commented on SLING-3471: added ReplicationAgentCommandsIntegration

[jira] [Created] (SLING-3471) Add Sling Replication IT for commands

Tommaso Teofili created SLING-3471: -- Summary: Add Sling Replication IT for commands Key: SLING-3471 URL: https://issues.apache.org/jira/browse/SLING-3471 Project: Sling Issue Type: Improveme

Re: Removing sling:features support from the resource resolver?

Big +1, I never liked this approach and it can too easily be abused as a poor replacement for ACLs. As you say, we should remove all code from the resource resolver, as well as some stuff from the feature flags bundle which relates to that code and is not used anywhere else. If we really want to

Removing sling:features support from the resource resolver?

Hi, Me and some of my colleagues have been experimenting with the sling:features support that we have now in the o.a.s.resourceresolver bundle, and I don't like it. Although the concept sounds cool, we've had a number of subtle issues that make me think that feature is not ready for prime time an

[jira] [Commented] (SLING-3470) Add Sling Replication ITs for all the exposed resources

[ https://issues.apache.org/jira/browse/SLING-3470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13941617#comment-13941617 ] Tommaso Teofili commented on SLING-3470: I've added a simple base IT class, with a

[jira] [Created] (SLING-3470) Add Sling Replication ITs for all the exposed resources

Tommaso Teofili created SLING-3470: -- Summary: Add Sling Replication ITs for all the exposed resources Key: SLING-3470 URL: https://issues.apache.org/jira/browse/SLING-3470 Project: Sling Iss