[jira] [Resolved] (SLING-9308) Remove Threaddump Option

[ https://issues.apache.org/jira/browse/SLING-9308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz resolved SLING-9308. - Resolution: Done > Remove Threaddump Option > > > Key:

[jira] [Created] (SLING-9308) Remove Threaddump Option

Oliver Lietz created SLING-9308: --- Summary: Remove Threaddump Option Key: SLING-9308 URL: https://issues.apache.org/jira/browse/SLING-9308 Project: Sling Issue Type: Task Components:

Re: [DISCUSS] Resource Mapping SPI

Hi Georg, Is the class https://github.com/apache/sling-org-apache-sling-api/blob/7dd23418280fcef234b42dbabf6e13e43ef2d4d0/src/main/java/org/apache/sling/api/resource/uri/ResourceURI.java

Re: Deprecate https://github.com/apache/sling-org-apache-sling-installer-factory-subsystems?

Done in https://github.com/apache/sling-org-apache-sling-installer-factory-subsystems/commit/189d84f794c430450b5053255ddd7a70ff83d84d . Konrad > On 4. Mar 2020, at

[jira] [Updated] (SLING-9307) Make build fully reproducible

[ https://issues.apache.org/jira/browse/SLING-9307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-9307: --- Description: According to https://github.com/jvm-repo-rebuild/reproducible-central#results

[jira] [Updated] (SLING-9307) Make build fully reproducible

[ https://issues.apache.org/jira/browse/SLING-9307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-9307: --- Description: According to https://github.com/jvm-repo-rebuild/reproducible-central#results

[jira] [Created] (SLING-9307) Make build fully reproducible

Konrad Windszus created SLING-9307: -- Summary: Make build fully reproducible Key: SLING-9307 URL: https://issues.apache.org/jira/browse/SLING-9307 Project: Sling Issue Type: Bug

[jira] [Created] (SLING-9306) Provide a path capability for scripts which are not part of a resource type

Radu Cotescu created SLING-9306: --- Summary: Provide a path capability for scripts which are not part of a resource type Key: SLING-9306 URL: https://issues.apache.org/jira/browse/SLING-9306 Project:

[jira] [Created] (SLING-9304) Provide Commons Messaging Option

Oliver Lietz created SLING-9304: --- Summary: Provide Commons Messaging Option Key: SLING-9304 URL: https://issues.apache.org/jira/browse/SLING-9304 Project: Sling Issue Type: Task

[jira] [Created] (SLING-9305) Provide Commons Messaging Mail Option

Oliver Lietz created SLING-9305: --- Summary: Provide Commons Messaging Mail Option Key: SLING-9305 URL: https://issues.apache.org/jira/browse/SLING-9305 Project: Sling Issue Type: Task

[jira] [Created] (SLING-9303) Provide Commons Crypto Option

Oliver Lietz created SLING-9303: --- Summary: Provide Commons Crypto Option Key: SLING-9303 URL: https://issues.apache.org/jira/browse/SLING-9303 Project: Sling Issue Type: Task

Re: Sonar complains about no assertion when using Awaitility

On Mon, Mar 30, 2020 at 5:58 AM Robert Munteanu wrote: > Hi Christian, > > On Mon, 2020-03-30 at 11:38 +0200, Christian Schneider wrote: > > In some of our tests we use Awaitility as the expected result will > > happen > > asynchronously. > > The code looks like: > > > >

Re: [VOTE] Release Apache Sling Repoinit Parser 1.6.2, Repoinit JCR 1.1.24

+1 Georg On 2020-03-30 12:58, Carsten Ziegeler wrote: +1 Carsten On 30.03.2020 11:10, Bertrand Delacretaz wrote: Hi, We solved the following issuess in this release: https://issues.apache.org/jira/projects/SLING/versions/12347795

Re: [VOTE] Release Apache Sling Repoinit Parser 1.6.2, Repoinit JCR 1.1.24

+1 Carsten On 30.03.2020 11:10, Bertrand Delacretaz wrote: Hi, We solved the following issuess in this release: https://issues.apache.org/jira/projects/SLING/versions/12347795 https://issues.apache.org/jira/projects/SLING/versions/12347796 Staging repository:

[jira] [Created] (SLING-9302) Remove NoSQL Options

Oliver Lietz created SLING-9302: --- Summary: Remove NoSQL Options Key: SLING-9302 URL: https://issues.apache.org/jira/browse/SLING-9302 Project: Sling Issue Type: Task Components:

Re: [VOTE] Release Apache Sling Repoinit Parser 1.6.2, Repoinit JCR 1.1.24

On Mon, 2020-03-30 at 11:10 +0200, Bertrand Delacretaz wrote: > Please vote to approve this release: +1 Robert signature.asc Description: This is a digitally signed message part

[jira] [Created] (SLING-9301) CI validator does not take into account additional artifacts

Robert Munteanu created SLING-9301: -- Summary: CI validator does not take into account additional artifacts Key: SLING-9301 URL: https://issues.apache.org/jira/browse/SLING-9301 Project: Sling

[jira] [Created] (SLING-9300) Provide Commons OSGi Option

Oliver Lietz created SLING-9300: --- Summary: Provide Commons OSGi Option Key: SLING-9300 URL: https://issues.apache.org/jira/browse/SLING-9300 Project: Sling Issue Type: New Feature

[jira] [Created] (SLING-9299) Provide Commons OSGi feature

Oliver Lietz created SLING-9299: --- Summary: Provide Commons OSGi feature Key: SLING-9299 URL: https://issues.apache.org/jira/browse/SLING-9299 Project: Sling Issue Type: New Feature

Re: Sonar complains about no assertion when using Awaitility

Hi Christian, On Mon, 2020-03-30 at 11:38 +0200, Christian Schneider wrote: > In some of our tests we use Awaitility as the expected result will > happen > asynchronously. > The code looks like: > > await().until(checker::isAvailable); > > > This actually is like an assertion but sonar then

Sonar complains about no assertion when using Awaitility

In some of our tests we use Awaitility as the expected result will happen asynchronously. The code looks like: await().until(checker::isAvailable); This actually is like an assertion but sonar then complains that the test does not assert anything. Is there a way to let sonar know that using an

Re: [VOTE] Release Apache Sling Content Distribution Journal Core 0.1.10

+1 (non binding) Christian Am Do., 26. März 2020 um 18:18 Uhr schrieb Timothee Maret : > Hi, > > We solved 6 issues in this release: > https://issues.apache.org/jira/projects/SLING/versions/12346963 > > There are still some outstanding issues: >

[VOTE] Release Apache Sling Repoinit Parser 1.6.2, Repoinit JCR 1.1.24

Hi, We solved the following issuess in this release: https://issues.apache.org/jira/projects/SLING/versions/12347795 https://issues.apache.org/jira/projects/SLING/versions/12347796 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-2228/ You can use this UNIX

[jira] [Resolved] (SLING-9171) Support for settings properties on paths created via repoinit create path

[ https://issues.apache.org/jira/browse/SLING-9171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz resolved SLING-9171. Resolution: Fixed > Support for settings properties on paths created via repoinit

[jira] [Updated] (SLING-6423) Allow for specifying ACL merge mode (ACHandling) in repoinit

[ https://issues.apache.org/jira/browse/SLING-6423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz updated SLING-6423: --- Fix Version/s: (was: Repoinit JCR 1.1.24) > Allow for specifying ACL merge mode

[jira] [Resolved] (SLING-7147) Support ACL remove * statement

[ https://issues.apache.org/jira/browse/SLING-7147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz resolved SLING-7147. Fix Version/s: (was: Repoinit JCR 1.1.24) Resolution: Duplicate Marking

[jira] [Assigned] (SLING-7147) Support ACL remove * statement

[ https://issues.apache.org/jira/browse/SLING-7147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz reassigned SLING-7147: -- Assignee: Bertrand Delacretaz > Support ACL remove * statement >

Re: [DISCUSS] Resource Mapping SPI

Hi Ruben, so in general nothing would change about how to use rr.map() from a consumer side (if that still happens via the rewriter pipeline by e.g. "a link checker" as provided downstream, that's totally fine). Now for people that want to replace the rewriter pipeline, we can just extend the

[jira] [Updated] (SLING-8483) Sling Feature Launcher with Content Package depends on Classpath Order and Needs Package Init Bundle

[ https://issues.apache.org/jira/browse/SLING-8483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-8483: Fix Version/s: (was: Feature Model Launcher 1.1.4) > Sling Feature Launcher with

[jira] [Resolved] (SLING-9298) Switch to commons.text

[ https://issues.apache.org/jira/browse/SLING-9298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-9298. - Resolution: Fixed Changed in

[jira] [Updated] (SLING-9298) Switch to commons.text

[ https://issues.apache.org/jira/browse/SLING-9298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler updated SLING-9298: Priority: Minor (was: Major) > Switch to commons.text > -- > >

[jira] [Created] (SLING-9298) Switch to commons.text

Carsten Ziegeler created SLING-9298: --- Summary: Switch to commons.text Key: SLING-9298 URL: https://issues.apache.org/jira/browse/SLING-9298 Project: Sling Issue Type: Improvement