[jira] [Updated] (SLING-6090) Avoid using nt:resource while creating file nodes via SlingPostServlet

[ https://issues.apache.org/jira/browse/SLING-6090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chetan Mehrotra updated SLING-6090: --- Description: Currently Sling uses {{nt:resource}} nodetype while creating file nodes in

Re: sling ci builds per module

Build feedback is now lot more faster and something one can rely on Thanks Robert!. Chetan Mehrotra On Wed, Oct 12, 2016 at 3:01 AM, Stefan Seifert wrote: > that's great, thanks! > > stefan > >>-Original Message- >>From: Robert Munteanu

[context-aware config] first release this week?

we've reached a quite good featureset in the current implementation of the context-ware configuration [1]. to make it usable by projects it would be useful to make a release soon. there are some planned extensions missing, but i've moved them to version 1.1.0 because i think they are not

RE: [context-aware config] context path strategy depending on request information?

we currently cannot come up with an elegant solution supporting it directly in the API/SPI. if a project needs this feature it can be implemented in project-specific code by implementing a thread local for getting the current request, and passing it into a custom

RE: sling ci builds per module

that's great, thanks! stefan >-Original Message- >From: Robert Munteanu [mailto:romb...@apache.org] >Sent: Tuesday, October 11, 2016 11:18 PM >To: dev@sling.apache.org >Subject: Re: sling ci builds per module > >For the record, this is now done. > >Robert

[jira] [Updated] (SLING-6060) Context-Aware Config: Configuration property override providers

[ https://issues.apache.org/jira/browse/SLING-6060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert updated SLING-6060: -- Description: add support similar to http://wcm.io/config/core/override-providers.html this is

[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: -- Description: the ConfigurationManager interface that is part of the "management API" dedicated

[jira] [Updated] (SLING-6060) Context-Aware Config: Configuration property override providers

[ https://issues.apache.org/jira/browse/SLING-6060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert updated SLING-6060: -- Fix Version/s: (was: Context-Aware Configuration 1.0.0) Context-Aware

[jira] [Updated] (SLING-6115) Context-Aware Config: Web Console Plugin

[ https://issues.apache.org/jira/browse/SLING-6115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert updated SLING-6115: -- Fix Version/s: (was: Context-Aware Configuration 1.0.0) Context-Aware

[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: -- Labels: contextaware-config (was: ) > Context-Aware Config: Configuration Manager - Support

[jira] [Commented] (SLING-6115) Context-Aware Config: Web Console Plugin

[ https://issues.apache.org/jira/browse/SLING-6115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15566647#comment-15566647 ] Stefan Seifert commented on SLING-6115: --- it would make sense to base the web console plugin on the

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

Stefan Seifert created SLING-6137: - Summary: Context-Aware Config: Configuration Manager - Support resource collection and property inheritance Key: SLING-6137 URL:

Re: sling ci builds per module

For the record, this is now done. Robert On Wed, 2016-09-28 at 22:52 +, Stefan Seifert wrote: > discussed at the Sling Committer Round Table @ adaptTo() 2016 > > we all agreed that we need CI build individually per module/bundle, > not a big build for all bundles at once. > > benefits: > -

[jira] [Commented] (SLING-6115) Context-Aware Config: Web Console Plugin

[ https://issues.apache.org/jira/browse/SLING-6115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15566626#comment-15566626 ] Stefan Seifert commented on SLING-6115: --- Completed: At revision: 1764356 because the current impl

[jira] [Resolved] (SLING-6061) Create per-module Jenkins jobs

[ https://issues.apache.org/jira/browse/SLING-6061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-6061. Resolution: Fixed All module jobs are now modularised. Any follow-up fixes will be handled

[GitHub] sling pull request #182: Adding dateFormat

GitHub user heervisscher opened a pull request: https://github.com/apache/sling/pull/182 Adding dateFormat PR to test the flow... You can merge this pull request into a Git repository by running: $ git pull https://github.com/heervisscher/sling SLING-6102 Alternatively you

[jira] [Resolved] (SLING-6058) Context-Aware Config: Property Inheritance/Merging

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

[jira] [Updated] (SLING-6136) Remove workaround for KARAF-4760 (FELIX-5261, comments in *.config files)

[ https://issues.apache.org/jira/browse/SLING-6136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz updated SLING-6136: Component/s: Karaf > Remove workaround for KARAF-4760 (FELIX-5261, comments in *.config files) >

[jira] [Created] (SLING-6136) Remove workaround for KARAF-4760 (FELIX-5261, comments in *.config files)

Oliver Lietz created SLING-6136: --- Summary: Remove workaround for KARAF-4760 (FELIX-5261, comments in *.config files) Key: SLING-6136 URL: https://issues.apache.org/jira/browse/SLING-6136 Project: Sling

[jira] [Commented] (SLING-6134) org.apache.sling.samples.jcr.contentloader does not build

[ https://issues.apache.org/jira/browse/SLING-6134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15566440#comment-15566440 ] Robert Munteanu commented on SLING-6134: Great, thanks for the quick fix! >

[jira] [Resolved] (SLING-6134) org.apache.sling.samples.jcr.contentloader does not build

[ https://issues.apache.org/jira/browse/SLING-6134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz resolved SLING-6134. - Resolution: Later moved to whiteboard in [r1764333|https://svn.apache.org/r1764333] and removed

Re: [VOTE] Release Apache Sling Scripting Core 2.0.40

On Tue, 2016-10-11 at 13:51 +, Radu Cotescu wrote: > Please vote to approve this release: +1 Robert signature.asc Description: This is a digitally signed message part

[jira] [Commented] (SLING-6134) org.apache.sling.samples.jcr.contentloader does not build

[ https://issues.apache.org/jira/browse/SLING-6134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15566423#comment-15566423 ] Oliver Lietz commented on SLING-6134: - [~rombert], I guess this sample is based on my work to make

[jira] [Updated] (SLING-6135) ResourceEditor build failure on Jenkins

[ https://issues.apache.org/jira/browse/SLING-6135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-6135: --- Description: The resource editor fails to build on Jenkins, and I have no idea how to tackle

[jira] [Updated] (SLING-6135) ResourceEditor build failure on Jenkins

[ https://issues.apache.org/jira/browse/SLING-6135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-6135: --- Attachment: resourceeditor_failure.txt > ResourceEditor build failure on Jenkins >

[jira] [Created] (SLING-6135) ResourceEditor build failure on Jenkins

Robert Munteanu created SLING-6135: -- Summary: ResourceEditor build failure on Jenkins Key: SLING-6135 URL: https://issues.apache.org/jira/browse/SLING-6135 Project: Sling Issue Type: Bug

[jira] [Commented] (SLING-920) Sling Jenkins setup

[ https://issues.apache.org/jira/browse/SLING-920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15566379#comment-15566379 ] Robert Munteanu commented on SLING-920: --- Disabled the following jobs, as they are replaced by

[jira] [Updated] (SLING-6134) org.apache.sling.samples.jcr.contentloader does not build

[ https://issues.apache.org/jira/browse/SLING-6134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz updated SLING-6134: Summary: org.apache.sling.samples.jcr.contentloader does not build (was:

[jira] [Created] (SLING-6134) org.apache.sling.samples.jcr.contentloader dues not build

Robert Munteanu created SLING-6134: -- Summary: org.apache.sling.samples.jcr.contentloader dues not build Key: SLING-6134 URL: https://issues.apache.org/jira/browse/SLING-6134 Project: Sling

[jira] [Updated] (SLING-6133) Refactor Event Utility

[ https://issues.apache.org/jira/browse/SLING-6133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-6133: Priority: Trivial (was: Major) > Refactor Event Utility > --- > >

[jira] [Updated] (SLING-6133) Refactor Event Utility

[ https://issues.apache.org/jira/browse/SLING-6133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-6133: Fix Version/s: Event 4.2.0 > Refactor Event Utility > --- > >

[jira] [Resolved] (SLING-6059) Context-Aware Config: Make resource inheritance for configuration collections configurable

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

[jira] [Updated] (SLING-6133) Refactor Event Utility

[ https://issues.apache.org/jira/browse/SLING-6133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jörg Hoh updated SLING-6133: Attachment: patch-SLING-6133.diff A patch including small improvements to the javadoc and a testcase >

[jira] [Created] (SLING-6133) Refactor Event Utility

Jörg Hoh created SLING-6133: --- Summary: Refactor Event Utility Key: SLING-6133 URL: https://issues.apache.org/jira/browse/SLING-6133 Project: Sling Issue Type: Improvement Components:

[jira] [Resolved] (SLING-6132) ResourceBuilder: Use absolute resource path should switch to hierachy mode

[ https://issues.apache.org/jira/browse/SLING-6132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert resolved SLING-6132. --- Resolution: Fixed Completed: At revision: 1764295 > ResourceBuilder: Use absolute

[jira] [Created] (SLING-6132) ResourceBuilder: Use absolute resource path should switch to hierachy mode

Stefan Seifert created SLING-6132: - Summary: ResourceBuilder: Use absolute resource path should switch to hierachy mode Key: SLING-6132 URL: https://issues.apache.org/jira/browse/SLING-6132 Project:

[GitHub] sling pull request #181: Issue/sling 5135

Github user bdelacretaz closed the pull request at: https://github.com/apache/sling/pull/181 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Commented] (SLING-5135) Whitelist legit usages of loginAdministrative and administrative ResourceResolver

[ https://issues.apache.org/jira/browse/SLING-5135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15565872#comment-15565872 ] Bertrand Delacretaz commented on SLING-5135: I have committed the bundles/ changes in revision

[jira] [Comment Edited] (SLING-6131) MapEntries: Invalid logic around added/changed/removed property names

[ https://issues.apache.org/jira/browse/SLING-6131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15565811#comment-15565811 ] Carsten Ziegeler edited comment on SLING-6131 at 10/11/16 3:51 PM: --- It

[jira] [Commented] (SLING-6131) MapEntries: Invalid logic around added/changed/removed property names

[ https://issues.apache.org/jira/browse/SLING-6131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15565811#comment-15565811 ] Carsten Ziegeler commented on SLING-6131: - It seems the "else" part is not sending an OSGi event

[jira] [Commented] (SLING-6131) MapEntries: Invalid logic around added/changed/removed property names

[ https://issues.apache.org/jira/browse/SLING-6131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15565788#comment-15565788 ] Bertrand Delacretaz commented on SLING-6131: Ok, I see, so I suppose something else is wrong

[jira] [Updated] (SLING-6131) MapEntries: Invalid logic around added/changed/removed property names

[ https://issues.apache.org/jira/browse/SLING-6131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-6131: Fix Version/s: Resource Resolver 1.4.20 > MapEntries: Invalid logic around

[jira] [Updated] (SLING-6131) MapEntries: Invalid logic around added/changed/removed property names

[ https://issues.apache.org/jira/browse/SLING-6131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-6131: Priority: Critical (was: Minor) > MapEntries: Invalid logic around added/changed/removed

[jira] [Commented] (SLING-6131) MapEntries: Invalid logic around added/changed/removed property names

[ https://issues.apache.org/jira/browse/SLING-6131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15565726#comment-15565726 ] Carsten Ziegeler commented on SLING-6131: - [~bdelacretaz] The change is actually intentional. If

[GitHub] sling pull request #181: Issue/sling 5135

GitHub user bdelacretaz opened a pull request: https://github.com/apache/sling/pull/181 Issue/sling 5135 Ready to commit this You can merge this pull request into a Git repository by running: $ git pull https://github.com/bdelacretaz/sling issue/SLING-5135 Alternatively you

[jira] [Updated] (SLING-6130) Restrict access for principal everyone and move configuration to repoinit

[ https://issues.apache.org/jira/browse/SLING-6130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz updated SLING-6130: Description: Currently {{everyone}} can {{read}} from {{/}} (configured in

Re: Build failed in Jenkins: sling-launchpad-builder-1.8 #33

On Tue, 2016-10-11 at 14:33 +, Apache Jenkins Server wrote: See java.io.IOException: Failed to mkdirs: Definitely looks like a Jenkins issue, filed  

Re: [VOTE] Release Apache Sling Scripting Core 2.0.40

+1 -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org

[jira] [Commented] (SLING-5135) Whitelist legit usages of loginAdministrative and administrative ResourceResolver

[ https://issues.apache.org/jira/browse/SLING-5135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15565525#comment-15565525 ] Bertrand Delacretaz commented on SLING-5135: The failing integration tests are caused by

[jira] [Created] (SLING-6131) MapEntries: Invalid logic around added/changed/removed property names

Bertrand Delacretaz created SLING-6131: -- Summary: MapEntries: Invalid logic around added/changed/removed property names Key: SLING-6131 URL: https://issues.apache.org/jira/browse/SLING-6131

Re: [VOTE] Release Apache Sling Scripting Core 2.0.40

+1 - Checked signatures and build On Tue, Oct 11, 2016 at 9:51 AM, Radu Cotescu wrote: > Hi, > > We solved 2 issues for this release: > https://issues.apache.org/jira/browse/SLING/fixforversion/12337945 > > Staging repository: >

[jira] [Updated] (SLING-6129) Sling IDE: Support bnd-maven-plugin as well

[ https://issues.apache.org/jira/browse/SLING-6129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-6129: --- Attachment: SLING-6129-v01.patch This patch comprises all changes from SLING-6112-v03 and in

[VOTE] Release Apache Sling Scripting Core 2.0.40

Hi, We solved 2 issues for this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12337945 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1533 You can use this UNIX script to download the releases and verify the signatures:

[jira] [Created] (SLING-6130) Restrict access for principal everyone and move configuration to repoinit

Oliver Lietz created SLING-6130: --- Summary: Restrict access for principal everyone and move configuration to repoinit Key: SLING-6130 URL: https://issues.apache.org/jira/browse/SLING-6130 Project: Sling

Re: restricting access for the "everyone" principal

On Thursday 06 October 2016 13:38:28 Carsten Ziegeler wrote: > Bertrand Delacretaz wrote > > > Hi, > > > > On Thu, Oct 6, 2016 at 12:03 PM, Radu Cotescu wrote: > >> ...Should we change this and only allow "jcr:read" on a new /content > >> folder > >> for "everyone"?... > > > >

[jira] [Commented] (SLING-6070) Reduce temporary storage required in JcrResourceListener, call reportChanges earlier

[ https://issues.apache.org/jira/browse/SLING-6070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15565377#comment-15565377 ] Stefan Egli commented on SLING-6070: bq. Since Oak uses a breadth-first tree traversal when compiling

[jira] [Updated] (SLING-6112) Make Sling IDE independent of m2e-tycho

[ https://issues.apache.org/jira/browse/SLING-6112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-6112: --- Attachment: SLING-6112-v03.patch Attached is a third version of the fix which # adds markers

[jira] [Commented] (SLING-6128) Sling IDE: Remove Lifecycle Mapping Extension Point for content-package

[ https://issues.apache.org/jira/browse/SLING-6128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15565362#comment-15565362 ] Konrad Windszus commented on SLING-6128: The patch v3 attached in SLING-6112 removes the lifecycle

[jira] [Resolved] (SLING-5304) Pattern Broken in resource resolver mapping

[ https://issues.apache.org/jira/browse/SLING-5304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-5304. - Resolution: Won't Fix > Pattern Broken in resource resolver mapping >

[jira] [Assigned] (SLING-6066) Clarify and complete removal resource events

[ https://issues.apache.org/jira/browse/SLING-6066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned SLING-6066: --- Assignee: Carsten Ziegeler > Clarify and complete removal resource events >

[jira] [Commented] (SLING-6126) Ability to specify TTL for separate health check

[ https://issues.apache.org/jira/browse/SLING-6126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15565227#comment-15565227 ] Georg Henzler commented on SLING-6126: -- If it is a DevOps Setup that checks for the health of an

[jira] [Commented] (SLING-5014) Installer blacklist, to avoid reinstalling older bundles

[ https://issues.apache.org/jira/browse/SLING-5014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15564988#comment-15564988 ] Dominik Süß commented on SLING-5014: [~cziegeler] - I can revisit this within the next 1-2 weeks.

[jira] [Created] (SLING-6129) Sling IDE: Support bnd-maven-plugin as well

Konrad Windszus created SLING-6129: -- Summary: Sling IDE: Support bnd-maven-plugin as well Key: SLING-6129 URL: https://issues.apache.org/jira/browse/SLING-6129 Project: Sling Issue Type:

[jira] [Reopened] (SLING-6059) Context-Aware Config: Make resource inheritance for configuration collections configurable

[ https://issues.apache.org/jira/browse/SLING-6059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert reopened SLING-6059: --- reopening: discussion in mailing list about details of the inheritance property handling - we

[jira] [Commented] (SLING-6058) Context-Aware Config: Property Inheritance/Merging

[ https://issues.apache.org/jira/browse/SLING-6058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15564789#comment-15564789 ] Stefan Seifert commented on SLING-6058: --- discussion in mailing list about details of the inheritance

RE: [context-aware config] performance impact of inhertiance

>If we think that inheritance is used sparsely then I think e) is the >best option - at least it is easy to understand. If you want to have >inheritance all over the place, it means that you have to set the >correct property all over the place. But then, this is still the >approach with less

Re: Sling IDE: Lifecycle Mapping Extension Point

Just for completeness: This feature of m2e was added in the context of https://bugs.eclipse.org/bugs/show_bug.cgi?id=337010 , so is actually pretty old, so we can safely rely on it. > On 11 Oct 2016, at 09:04, Konrad Windszus

[jira] [Created] (SLING-6128) Sling IDE: Remove Lifecycle Mapping Extension Point for content-package

Konrad Windszus created SLING-6128: -- Summary: Sling IDE: Remove Lifecycle Mapping Extension Point for content-package Key: SLING-6128 URL: https://issues.apache.org/jira/browse/SLING-6128 Project:

Re: Sling IDE: Lifecycle Mapping Extension Point

This should not be necessary. Whenever there is an unknown packaging the DefaultLifecycleMapping.java is used which derives from AbstractCustomizableLifecycleMapping as well. There is even a test explicitly written for that in

[jira] [Resolved] (SLING-6127) Update to Apache Felix Http Jetty 3.4.0 and Http Bridge 3.0.16

[ https://issues.apache.org/jira/browse/SLING-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-6127. - Resolution: Fixed Updated in rev 1764203 > Update to Apache Felix Http Jetty 3.4.0 and

[jira] [Comment Edited] (SLING-6112) Make Sling IDE independent of m2e-tycho

[ https://issues.apache.org/jira/browse/SLING-6112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15564681#comment-15564681 ] Konrad Windszus edited comment on SLING-6112 at 10/11/16 6:58 AM: -- This

[jira] [Created] (SLING-6127) Update to Apache Felix Http Jetty 3.4.0 and Http Bridge 3.0.16

Carsten Ziegeler created SLING-6127: --- Summary: Update to Apache Felix Http Jetty 3.4.0 and Http Bridge 3.0.16 Key: SLING-6127 URL: https://issues.apache.org/jira/browse/SLING-6127 Project: Sling

[jira] [Resolved] (SLING-6002) ScriptCacheImpl should move to new ResourceChangeListener API

[ https://issues.apache.org/jira/browse/SLING-6002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-6002. - Resolution: Fixed Search path handling looks fine, I've improved the impl slightly to

[jira] [Commented] (SLING-6112) Make Sling IDE independent of m2e-tycho

[ https://issues.apache.org/jira/browse/SLING-6112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15564681#comment-15564681 ] Konrad Windszus commented on SLING-6112: This is indeed expected. With m-b-p 3.2.0 it only works

[jira] [Resolved] (SLING-6001) ProcessorManagerImpl should move to new ResourceChangeListener API

[ https://issues.apache.org/jira/browse/SLING-6001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-6001. - Resolution: Fixed I've updated the implemenation to use a glob pattern and create a

[jira] [Commented] (SLING-6126) Ability to specify TTL for separate health check

[ https://issues.apache.org/jira/browse/SLING-6126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15564657#comment-15564657 ] Evgeniy Fitsner commented on SLING-6126: Dear [~henzlerg], Suddenly but this is not an option in