[jira] [Resolved] (SLING-6333) Context-Aware Config: Allow to mark Config Annotation Classes as "Collections"

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

[jira] [Updated] (SLING-6333) Context-Aware Config: Allow to mark Config Annotation Classes as "Collections"

[ https://issues.apache.org/jira/browse/SLING-6333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert updated SLING-6333: -- Summary: Context-Aware Config: Allow to mark Config Annotation Classes as "Collections" (was:

[jira] [Commented] (SLING-6329) RR.isResourceType() broken with jcr.resource 2.8.2

[ https://issues.apache.org/jira/browse/SLING-6329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15696401#comment-15696401 ] Julian Sedding commented on SLING-6329: --- Fixed in [r1771346|https://svn.apache.org/r1771346]. Added

[jira] [Resolved] (SLING-6329) RR.isResourceType() broken with jcr.resource 2.8.2

[ https://issues.apache.org/jira/browse/SLING-6329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding resolved SLING-6329. --- Resolution: Fixed Fix Version/s: Resource Resolver 1.5.6 > RR.isResourceType() broken

Re: How to handle minor version updates in API for provider bundles?

I think the core problem is that we have provider-type classes and consumer-type classes mixed in packages of sling.api. Maybe we should start thinking about how to improve the situation there? For now, I think what we normally do is update everything to snapshots that needs it and then start

[jira] [Commented] (SLING-6327) ResourceResolverImpl.isResourceType() should compare relative resource types (and ignore any search path prefixes)

[ https://issues.apache.org/jira/browse/SLING-6327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15696370#comment-15696370 ] Konrad Windszus commented on SLING-6327: The problem is the increased minor version of

[jira] [Created] (SLING-6333) Context-Aware Config: Inventory Printer Web Console Plugin

Stefan Seifert created SLING-6333: - Summary: Context-Aware Config: Inventory Printer Web Console Plugin Key: SLING-6333 URL: https://issues.apache.org/jira/browse/SLING-6333 Project: Sling

How to handle minor version updates in API for provider bundles?

With https://issues.apache.org/jira/browse/SLING-6327 I increased the minor version of o.a.s.resource from 2.9.0 to 2.10.0 (because of added methods to a ResourceUtil). That means that all provider bundles for this package (namely o.a.s.jcr.resource and o.a.s.resourceresolver) need to be

[jira] [Updated] (SLING-6137) Context-Aware Config: Configuration Manager - Support resource collection and property inheritance

[ https://issues.apache.org/jira/browse/SLING-6137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert updated SLING-6137: -- Fix Version/s: Context-Aware Configuration SPI 1.2.0 > Context-Aware Config: Configuration

[jira] [Commented] (SLING-6327) ResourceResolverImpl.isResourceType() should compare relative resource types (and ignore any search path prefixes)

[ https://issues.apache.org/jira/browse/SLING-6327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15696290#comment-15696290 ] Robert Munteanu commented on SLING-6327: Well, the launchpad (still) uses the latest snapshots for

[jira] [Commented] (SLING-6327) ResourceResolverImpl.isResourceType() should compare relative resource types (and ignore any search path prefixes)

[ https://issues.apache.org/jira/browse/SLING-6327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15696267#comment-15696267 ] Konrad Windszus commented on SLING-6327: Fixed by downgrading to the latest release of

[jira] [Commented] (SLING-6327) ResourceResolverImpl.isResourceType() should compare relative resource types (and ignore any search path prefixes)

[ https://issues.apache.org/jira/browse/SLING-6327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15696246#comment-15696246 ] Konrad Windszus commented on SLING-6327: The reason is that resource resolver in version

[jira] [Updated] (SLING-5788) Implement a Sightly Maven Plugin

[ https://issues.apache.org/jira/browse/SLING-5788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu updated SLING-5788: Labels: Sling-9-ReleaseNotes (was: ) > Implement a Sightly Maven Plugin >

[jira] [Updated] (SLING-6166) Update the HTL bundles to use the SLING-6165 request-scoped resource resolver

[ https://issues.apache.org/jira/browse/SLING-6166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu updated SLING-6166: Description: The fix for SLING-6156 brings in a performance penalty for the JS Use Provider since

[jira] [Updated] (SLING-6166) Update the HTL bundles to use the SLING-6165 request-scoped resource resolver

[ https://issues.apache.org/jira/browse/SLING-6166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu updated SLING-6166: Affects Version/s: Scripting HTL Engine 1.0.26 > Update the HTL bundles to use the SLING-6165

[jira] [Updated] (SLING-6166) Update the HTL bundles to use the SLING-6165 request-scoped resource resolver

[ https://issues.apache.org/jira/browse/SLING-6166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu updated SLING-6166: Fix Version/s: Scripting HTL Engine 1.0.28 > Update the HTL bundles to use the SLING-6165

[jira] [Updated] (SLING-6166) Update the HTL bundles to use the SLING-6165 request-scoped resource resolver

[ https://issues.apache.org/jira/browse/SLING-6166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu updated SLING-6166: Summary: Update the HTL bundles to use the SLING-6165 request-scoped resource resolver (was:

[jira] [Resolved] (SLING-6331) Move bundles/extensions/explorer to the attic

[ https://issues.apache.org/jira/browse/SLING-6331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-6331. Resolution: Fixed > Move bundles/extensions/explorer to the attic >

[jira] [Reopened] (SLING-6331) Move bundles/extensions/explorer to the attic

[ https://issues.apache.org/jira/browse/SLING-6331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu reopened SLING-6331: > Move bundles/extensions/explorer to the attic > -

[jira] [Commented] (SLING-6331) Move bundles/extensions/explorer to the attic

[ https://issues.apache.org/jira/browse/SLING-6331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15696039#comment-15696039 ] Robert Munteanu commented on SLING-6331: * [r1771329|https://svn.apache.org/r1771329] - moved

[jira] [Commented] (SLING-6330) Replace Sling Explorer with Composum

[ https://issues.apache.org/jira/browse/SLING-6330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15696031#comment-15696031 ] Robert Munteanu commented on SLING-6330: * [r1771325|https://svn.apache.org/r1771325] - remove

[jira] [Resolved] (SLING-6330) Replace Sling Explorer with Composum

[ https://issues.apache.org/jira/browse/SLING-6330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-6330. Resolution: Fixed > Replace Sling Explorer with Composum >

[jira] [Commented] (SLING-6332) Configurations with same PID but different features/run modes in provisioning model are ignored

[ https://issues.apache.org/jira/browse/SLING-6332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15696018#comment-15696018 ] Robert Munteanu commented on SLING-6332: Your title looks better, I think Jira needs some

[jira] [Updated] (SLING-6332) Configurations with same PID but different features/run modes in provisioning model are ignored

[ https://issues.apache.org/jira/browse/SLING-6332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-6332: --- Summary: Configurations with same PID but different features/run modes in provisioning model

[jira] [Commented] (SLING-6332) Configurations with same PID but different features/run modes in provisioning model are ignored

[ https://issues.apache.org/jira/browse/SLING-6332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15696009#comment-15696009 ] Bertrand Delacretaz commented on SLING-6332: I had another go at the title, feel free to tweak

[jira] [Updated] (SLING-6332) Configurations with same PID but different features/run modes in provisioning model are ignored

[ https://issues.apache.org/jira/browse/SLING-6332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz updated SLING-6332: --- Summary: Configurations with same PID but different features/run modes in

[jira] [Updated] (SLING-6332) Slingstart plugin ignores configurations with same PID but different features/run modes

[ https://issues.apache.org/jira/browse/SLING-6332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz updated SLING-6332: --- Summary: Slingstart plugin ignores configurations with same PID but different

[jira] [Updated] (SLING-6332) Slingstart plugin: configurations from different features/run modes are silently discarded

[ https://issues.apache.org/jira/browse/SLING-6332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz updated SLING-6332: --- Summary: Slingstart plugin: configurations from different features/run modes are

[jira] [Updated] (SLING-6332) Configurations from different features are silently discarded

[ https://issues.apache.org/jira/browse/SLING-6332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-6332: --- Summary: Configurations from different features are silently discarded (was: Configurations

[jira] [Commented] (SLING-6332) Configurations from different features are silently discarded

[ https://issues.apache.org/jira/browse/SLING-6332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15696000#comment-15696000 ] Robert Munteanu commented on SLING-6332: I've updated the title to reflect the current situation -

[jira] [Updated] (SLING-6332) Configurations from slingstart dependencies are not overwritten or merged

[ https://issues.apache.org/jira/browse/SLING-6332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-6332: --- Fix Version/s: (was: Slingstart Maven Plugin 1.7.0) Sling Provisioning

[jira] [Updated] (SLING-6332) Configurations from slingstart dependencies are not overwritten or merged

[ https://issues.apache.org/jira/browse/SLING-6332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-6332: --- Component/s: (was: Maven Plugins and Archetypes) Tooling >

[jira] [Commented] (SLING-6332) Configurations from slingstart dependencies are not overwritten or merged

[ https://issues.apache.org/jira/browse/SLING-6332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15695992#comment-15695992 ] Robert Munteanu commented on SLING-6332: That's a good point. in slingstart.txt both

[jira] [Commented] (SLING-6332) Configurations from slingstart dependencies are not overwritten or merged

[ https://issues.apache.org/jira/browse/SLING-6332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15695974#comment-15695974 ] Bertrand Delacretaz commented on SLING-6332: I think the {{target/slingstart.txt}} file should

[jira] [Commented] (SLING-6332) Configurations from slingstart dependencies are not overwritten or merged

[ https://issues.apache.org/jira/browse/SLING-6332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15695926#comment-15695926 ] Robert Munteanu commented on SLING-6332: I've tried to debug with no luck. It seems that

[jira] [Updated] (SLING-6330) Replace Sling Explorer with Composum

[ https://issues.apache.org/jira/browse/SLING-6330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-6330: --- Attachment: SLING-6330.zip Unfortunately I'm blocked by a bug in the slingstart-maven-plugin,

[jira] [Created] (SLING-6332) Configurations from slingstart dependencies are not overwritten or merged

Robert Munteanu created SLING-6332: -- Summary: Configurations from slingstart dependencies are not overwritten or merged Key: SLING-6332 URL: https://issues.apache.org/jira/browse/SLING-6332 Project:

[jira] [Updated] (SLING-6330) Replace Sling Explorer with Composum

[ https://issues.apache.org/jira/browse/SLING-6330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-6330: --- Labels: Sling-9-ReleaseNotes (was: ) > Replace Sling Explorer with Composum >

[jira] [Updated] (SLING-6330) Replace Sling Explorer with Composum

[ https://issues.apache.org/jira/browse/SLING-6330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-6330: --- Fix Version/s: Launchpad Content 2.0.10 > Replace Sling Explorer with Composum >

[jira] [Created] (SLING-6331) Move bundles/extensions/explorer to the attic

Robert Munteanu created SLING-6331: -- Summary: Move bundles/extensions/explorer to the attic Key: SLING-6331 URL: https://issues.apache.org/jira/browse/SLING-6331 Project: Sling Issue Type:

Re: What repository explorer should we ship with Launchpad 9?

On Mon, 2016-11-21 at 14:32 +0100, Bertrand Delacretaz wrote: > On Mon, Nov 21, 2016 at 2:14 PM, Stefan Seifert de> wrote: > > ...composum console [1] is published with MIT license, not sure if > > this is a problem... > > That's fine, as per

[jira] [Updated] (SLING-6330) Replace Sling Explorer with Composum

[ https://issues.apache.org/jira/browse/SLING-6330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-6330: --- Issue Type: New Feature (was: Bug) > Replace Sling Explorer with Composum >

[jira] [Created] (SLING-6330) Replace Sling Explorer with Composum

Robert Munteanu created SLING-6330: -- Summary: Replace Sling Explorer with Composum Key: SLING-6330 URL: https://issues.apache.org/jira/browse/SLING-6330 Project: Sling Issue Type: Bug

[jira] [Commented] (SLING-6327) ResourceResolverImpl.isResourceType() should compare relative resource types (and ignore any search path prefixes)

[ https://issues.apache.org/jira/browse/SLING-6327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15695841#comment-15695841 ] Robert Munteanu commented on SLING-6327: Looks like there are more adjustments to be made - the

[jira] [Commented] (SLING-6329) RR.isResourceType() broken with jcr.resource 2.8.2

[ https://issues.apache.org/jira/browse/SLING-6329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15695755#comment-15695755 ] Bertrand Delacretaz commented on SLING-6329: IIUC this causes

[jira] [Resolved] (SLING-6327) ResourceResolverImpl.isResourceType() should compare relative resource types (and ignore any search path prefixes)

[ https://issues.apache.org/jira/browse/SLING-6327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus resolved SLING-6327. Resolution: Fixed Fix Version/s: Resource Resolver 1.5.6 API

[jira] [Updated] (SLING-6327) ResourceResolverImpl.isResourceType() should compare relative resource types (and ignore any search path prefixes)

[ https://issues.apache.org/jira/browse/SLING-6327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-6327: --- Summary: ResourceResolverImpl.isResourceType() should compare relative resource types (and

[jira] [Updated] (SLING-6327) ResourceResolverImpl.isResourceType() should compare relative resource types (and strip off search path prefixes)

[ https://issues.apache.org/jira/browse/SLING-6327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-6327: --- Summary: ResourceResolverImpl.isResourceType() should compare relative resource types (and

[jira] [Commented] (SLING-5228) Remove loginAdministrative() usage from org.apache.sling.installer.provider.jcr

[ https://issues.apache.org/jira/browse/SLING-5228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15695701#comment-15695701 ] Julian Sedding commented on SLING-5228: --- [~rombert] Thanks, that's fine with me. If this is too

[jira] [Updated] (SLING-6329) RR.isResourceType() broken with jcr.resource 2.8.2

[ https://issues.apache.org/jira/browse/SLING-6329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding updated SLING-6329: -- Attachment: SLING-6329-jsedding.patch Proposed patch. Still working on a test case. >

[jira] [Created] (SLING-6329) RR.isResourceType() broken with jcr.resource 2.8.2

Julian Sedding created SLING-6329: - Summary: RR.isResourceType() broken with jcr.resource 2.8.2 Key: SLING-6329 URL: https://issues.apache.org/jira/browse/SLING-6329 Project: Sling Issue

Re: [VOTE] Release Apache Sling JCR Installer version 3.1.20

On Fri, 2016-11-25 at 13:24 +0200, Robert Munteanu wrote: > Please vote to approve this release: +1 Robert signature.asc Description: This is a digitally signed message part

[VOTE] Release Apache Sling JCR Installer version 3.1.20

Hi, We solved 5 issues in this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12334867 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1583 You can use this UNIX script to download the release and verify the signatures:

[jira] [Commented] (SLING-5229) Remove getAdministrativeResourceResolver() and loginAdministrative() usage from JCR components

[ https://issues.apache.org/jira/browse/SLING-5229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15695606#comment-15695606 ] Robert Munteanu commented on SLING-5229: Removing JCR installer from the target versions as for

[jira] [Updated] (SLING-5229) Remove getAdministrativeResourceResolver() and loginAdministrative() usage from JCR components

[ https://issues.apache.org/jira/browse/SLING-5229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-5229: --- Fix Version/s: (was: JCR Installer 3.1.20) > Remove getAdministrativeResourceResolver()

[jira] [Commented] (SLING-5228) Remove loginAdministrative() usage from org.apache.sling.installer.provider.jcr

[ https://issues.apache.org/jira/browse/SLING-5228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15695599#comment-15695599 ] Robert Munteanu commented on SLING-5228: * [r1771282|https://svn.apache.org/r1771282] - removed

[jira] [Resolved] (SLING-5228) Remove loginAdministrative() usage from org.apache.sling.installer.provider.jcr

[ https://issues.apache.org/jira/browse/SLING-5228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-5228. Resolution: Fixed > Remove loginAdministrative() usage from >

[jira] [Commented] (SLING-6327) ResourceResolverImpl.isResourceType() should consider resource resolver's search path

[ https://issues.apache.org/jira/browse/SLING-6327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15695418#comment-15695418 ] Julian Sedding commented on SLING-6327: --- TL;DR: I think always stripping off any search-path

[jira] [Updated] (SLING-6219) Allow for creating users with repoinit

[ https://issues.apache.org/jira/browse/SLING-6219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz updated SLING-6219: --- Summary: Allow for creating users with repoinit (was: Allow to create users with

[jira] [Commented] (SLING-6219) Allow to create users with repoinit

[ https://issues.apache.org/jira/browse/SLING-6219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15695408#comment-15695408 ] Bertrand Delacretaz commented on SLING-6219: I have added a warning in

[jira] [Commented] (SLING-6219) Allow to create users with repoinit

[ https://issues.apache.org/jira/browse/SLING-6219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15695374#comment-15695374 ] Roy Teeuwen commented on SLING-6219: Thanks, must have missed that :) > Allow to create users with

[jira] [Commented] (SLING-6219) Allow to create users with repoinit

[ https://issues.apache.org/jira/browse/SLING-6219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15695356#comment-15695356 ] Bertrand Delacretaz commented on SLING-6219: See the repoinit docs at

[jira] [Commented] (SLING-6328) JSP concurrent compiling issue

[ https://issues.apache.org/jira/browse/SLING-6328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15695278#comment-15695278 ] Felix Meschberger commented on SLING-6328: -- [~rombert] According to the bug referenced this is a

[jira] [Commented] (SLING-6328) JSP concurrent compiling issue

[ https://issues.apache.org/jira/browse/SLING-6328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15695219#comment-15695219 ] Robert Munteanu commented on SLING-6328: Thanks for the report. This isn't my area of expertise,