[jira] [Resolved] (SLING-8354) Migrate all existing Health Checks in Sling to Felix HC API
[
https://issues.apache.org/jira/browse/SLING-8354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Georg Henzler resolved SLING-8354.
--
Resolution: Fixed
> Migrate all existing Health Checks in Sling to Felix HC API
> ---
>
> Key: SLING-8354
> URL: https://issues.apache.org/jira/browse/SLING-8354
> Project: Sling
> Issue Type: New Feature
> Components: Health Check
>Reporter: Georg Henzler
>Assignee: Georg Henzler
>Priority: Major
> Fix For: JUnit Health Check 1.0.8, Content Distribution Core
> 0.4.4, Installer Health Checks 2.0.4, Commons Scheduler 2.7.8, Discovery Oak
> 1.2.32
>
>
> Migrate all health checks in Sling project to use the new Felix HC API.
> Generally make the package import to {{org.apache.felix.hc.api}} optional (to
> make the base functionality still available if the HC framework is not
> available)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (SLING-8354) Migrate all existing Health Checks in Sling to Felix HC API
[
https://issues.apache.org/jira/browse/SLING-8354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Georg Henzler updated SLING-8354:
-
Summary: Migrate all existing Health Checks in Sling to Felix HC API (was:
Migrate all existing Sling Health Checks to Felix HC API)
> Migrate all existing Health Checks in Sling to Felix HC API
> ---
>
> Key: SLING-8354
> URL: https://issues.apache.org/jira/browse/SLING-8354
> Project: Sling
> Issue Type: New Feature
> Components: Health Check
>Reporter: Georg Henzler
>Assignee: Georg Henzler
>Priority: Major
> Fix For: JUnit Health Check 1.0.8, Content Distribution Core
> 0.4.4, Installer Health Checks 2.0.4, Commons Scheduler 2.7.8, Discovery Oak
> 1.2.32
>
>
> Migrate all health checks in Sling project to use the new Felix HC API.
> Generally make the package import to {{org.apache.felix.hc.api}} optional (to
> make the base functionality still available if the HC framework is not
> available)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (SLING-8354) Migrate all existing Sling Health Checks to Felix HC API
[
https://issues.apache.org/jira/browse/SLING-8354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Georg Henzler updated SLING-8354:
-
Fix Version/s: JUnit Health Check 1.0.8
> Migrate all existing Sling Health Checks to Felix HC API
>
>
> Key: SLING-8354
> URL: https://issues.apache.org/jira/browse/SLING-8354
> Project: Sling
> Issue Type: New Feature
> Components: Health Check
>Reporter: Georg Henzler
>Assignee: Georg Henzler
>Priority: Major
> Fix For: JUnit Health Check 1.0.8, Content Distribution Core
> 0.4.4, Installer Health Checks 2.0.4, Commons Scheduler 2.7.8, Discovery Oak
> 1.2.32
>
>
> Migrate all health checks in Sling project to use the new Felix HC API.
> Generally make the package import to {{org.apache.felix.hc.api}} optional (to
> make the base functionality still available if the HC framework is not
> available)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (SLING-8354) Migrate all existing Sling Health Checks to Felix HC API
[
https://issues.apache.org/jira/browse/SLING-8354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17171195#comment-17171195
]
Georg Henzler commented on SLING-8354:
--
Fixed for org-apache-sling-junit-healthcheck in
[a9e947c25401db|https://github.com/apache/sling-org-apache-sling-junit-healthcheck/commit/a9e947c25401db062ae3cd7b5f1fde1db649c1b6]
> Migrate all existing Sling Health Checks to Felix HC API
>
>
> Key: SLING-8354
> URL: https://issues.apache.org/jira/browse/SLING-8354
> Project: Sling
> Issue Type: New Feature
> Components: Health Check
>Reporter: Georg Henzler
>Assignee: Georg Henzler
>Priority: Major
> Fix For: Content Distribution Core 0.4.4, Installer Health Checks
> 2.0.4, Commons Scheduler 2.7.8, Discovery Oak 1.2.32
>
>
> Migrate all health checks in Sling project to use the new Felix HC API.
> Generally make the package import to {{org.apache.felix.hc.api}} optional (to
> make the base functionality still available if the HC framework is not
> available)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (SLING-8354) Migrate all existing Sling Health Checks to Felix HC API
[
https://issues.apache.org/jira/browse/SLING-8354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Georg Henzler updated SLING-8354:
-
Fix Version/s: Installer Health Checks 2.0.4
> Migrate all existing Sling Health Checks to Felix HC API
>
>
> Key: SLING-8354
> URL: https://issues.apache.org/jira/browse/SLING-8354
> Project: Sling
> Issue Type: New Feature
> Components: Health Check
>Reporter: Georg Henzler
>Assignee: Georg Henzler
>Priority: Major
> Fix For: Content Distribution Core 0.4.4, Installer Health Checks
> 2.0.4, Commons Scheduler 2.7.8, Discovery Oak 1.2.32
>
>
> Migrate all health checks in Sling project to use the new Felix HC API.
> Generally make the package import to {{org.apache.felix.hc.api}} optional (to
> make the base functionality still available if the HC framework is not
> available)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (SLING-8354) Migrate all existing Sling Health Checks to Felix HC API
[
https://issues.apache.org/jira/browse/SLING-8354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17171189#comment-17171189
]
Georg Henzler commented on SLING-8354:
--
Fixed for org-apache-sling-installer-hc in
[e70731be8fcaf62|https://github.com/apache/sling-org-apache-sling-installer-hc/commit/e70731be8fcaf624c6df15260559d76f5c51f850]
> Migrate all existing Sling Health Checks to Felix HC API
>
>
> Key: SLING-8354
> URL: https://issues.apache.org/jira/browse/SLING-8354
> Project: Sling
> Issue Type: New Feature
> Components: Health Check
>Reporter: Georg Henzler
>Assignee: Georg Henzler
>Priority: Major
> Fix For: Content Distribution Core 0.4.4, Commons Scheduler
> 2.7.8, Discovery Oak 1.2.32
>
>
> Migrate all health checks in Sling project to use the new Felix HC API.
> Generally make the package import to {{org.apache.felix.hc.api}} optional (to
> make the base functionality still available if the HC framework is not
> available)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (SLING-8354) Migrate all existing Sling Health Checks to Felix HC API
[
https://issues.apache.org/jira/browse/SLING-8354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17171181#comment-17171181
]
Georg Henzler commented on SLING-8354:
--
Fixed for
sling-org-apache-sling-commons-scheduler in
[f6a4f78a9fbfe37|https://github.com/apache/sling-org-apache-sling-commons-scheduler/commit/f6a4f78a9fbfe37e127f36fbb96e5615f963d4bf]
> Migrate all existing Sling Health Checks to Felix HC API
>
>
> Key: SLING-8354
> URL: https://issues.apache.org/jira/browse/SLING-8354
> Project: Sling
> Issue Type: New Feature
> Components: Health Check
>Reporter: Georg Henzler
>Assignee: Georg Henzler
>Priority: Major
> Fix For: Content Distribution Core 0.4.4, Discovery Oak 1.2.32
>
>
> Migrate all health checks in Sling project to use the new Felix HC API.
> Generally make the package import to {{org.apache.felix.hc.api}} optional (to
> make the base functionality still available if the HC framework is not
> available)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (SLING-8354) Migrate all existing Sling Health Checks to Felix HC API
[
https://issues.apache.org/jira/browse/SLING-8354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Georg Henzler updated SLING-8354:
-
Fix Version/s: Commons Scheduler 2.7.8
> Migrate all existing Sling Health Checks to Felix HC API
>
>
> Key: SLING-8354
> URL: https://issues.apache.org/jira/browse/SLING-8354
> Project: Sling
> Issue Type: New Feature
> Components: Health Check
>Reporter: Georg Henzler
>Assignee: Georg Henzler
>Priority: Major
> Fix For: Content Distribution Core 0.4.4, Commons Scheduler
> 2.7.8, Discovery Oak 1.2.32
>
>
> Migrate all health checks in Sling project to use the new Felix HC API.
> Generally make the package import to {{org.apache.felix.hc.api}} optional (to
> make the base functionality still available if the HC framework is not
> available)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (SLING-8354) Migrate all existing Sling Health Checks to Felix HC API
[
https://issues.apache.org/jira/browse/SLING-8354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Georg Henzler updated SLING-8354:
-
Fix Version/s: Discovery Oak 1.2.32
> Migrate all existing Sling Health Checks to Felix HC API
>
>
> Key: SLING-8354
> URL: https://issues.apache.org/jira/browse/SLING-8354
> Project: Sling
> Issue Type: New Feature
> Components: Health Check
>Reporter: Georg Henzler
>Assignee: Georg Henzler
>Priority: Major
> Fix For: Content Distribution Core 0.4.4, Discovery Oak 1.2.32
>
>
> Migrate all health checks in Sling project to use the new Felix HC API.
> Generally make the package import to {{org.apache.felix.hc.api}} optional (to
> make the base functionality still available if the HC framework is not
> available)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (SLING-8354) Migrate all existing Sling Health Checks to Felix HC API
[
https://issues.apache.org/jira/browse/SLING-8354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Georg Henzler updated SLING-8354:
-
Description:
Migrate all health checks in Sling project to use the new Felix HC API.
Generally make the package import to {{org.apache.felix.hc.api}} optional (to
make the base functionality still available if the HC framework is not
available)
was:
Migrate all health checks in Sling project to use the new Felix HC API.
Generally make the package import to optional (to make the base functionality
still available if the HC framework is not available)
> Migrate all existing Sling Health Checks to Felix HC API
>
>
> Key: SLING-8354
> URL: https://issues.apache.org/jira/browse/SLING-8354
> Project: Sling
> Issue Type: New Feature
> Components: Health Check
>Reporter: Georg Henzler
>Assignee: Georg Henzler
>Priority: Major
> Fix For: Content Distribution Core 0.4.4
>
>
> Migrate all health checks in Sling project to use the new Felix HC API.
> Generally make the package import to {{org.apache.felix.hc.api}} optional (to
> make the base functionality still available if the HC framework is not
> available)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (SLING-8354) Migrate all existing Sling Health Checks to Felix HC API
[ https://issues.apache.org/jira/browse/SLING-8354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17171177#comment-17171177 ] Georg Henzler commented on SLING-8354: -- Fixed for org.apache.sling.discovery.oak in [e84a875062ecc17ed6d5|https://github.com/apache/sling-org-apache-sling-distribution-core/commit/e84a875062ecc17ed6d5711ef6e666c932dbe7ab] > Migrate all existing Sling Health Checks to Felix HC API > > > Key: SLING-8354 > URL: https://issues.apache.org/jira/browse/SLING-8354 > Project: Sling > Issue Type: New Feature > Components: Health Check >Reporter: Georg Henzler >Assignee: Georg Henzler >Priority: Major > Fix For: Content Distribution Core 0.4.4 > > > Migrate all health checks in Sling project to use the new Felix HC API. > Generally make the package import to optional (to make the base functionality > still available if the HC framework is not available) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (SLING-8354) Migrate all existing Sling Health Checks to Felix HC API
[ https://issues.apache.org/jira/browse/SLING-8354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Georg Henzler updated SLING-8354: - Fix Version/s: Content Distribution Core 0.4.4 > Migrate all existing Sling Health Checks to Felix HC API > > > Key: SLING-8354 > URL: https://issues.apache.org/jira/browse/SLING-8354 > Project: Sling > Issue Type: New Feature > Components: Health Check >Reporter: Georg Henzler >Assignee: Georg Henzler >Priority: Major > Fix For: Content Distribution Core 0.4.4 > > > Migrate all health checks in Sling project to use the new Felix HC API. > Generally make the package import to optional (to make the base functionality > still available if the HC framework is not available) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (SLING-8354) Migrate all existing Sling Health Checks to Felix HC API
[ https://issues.apache.org/jira/browse/SLING-8354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17171172#comment-17171172 ] Georg Henzler commented on SLING-8354: -- Fixed for sling-org-apache-sling-distribution-core in [e84a875062ecc17ed6d5|https://github.com/apache/sling-org-apache-sling-distribution-core/commit/e84a875062ecc17ed6d5711ef6e666c932dbe7ab] > Migrate all existing Sling Health Checks to Felix HC API > > > Key: SLING-8354 > URL: https://issues.apache.org/jira/browse/SLING-8354 > Project: Sling > Issue Type: New Feature > Components: Health Check >Reporter: Georg Henzler >Assignee: Georg Henzler >Priority: Major > > Migrate all health checks in Sling project to use the new Felix HC API. > Generally make the package import to optional (to make the base functionality > still available if the HC framework is not available) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (SLING-8354) Migrate all existing Sling Health Checks to Felix HC API
[ https://issues.apache.org/jira/browse/SLING-8354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Georg Henzler updated SLING-8354: - Description: Migrate all health checks in Sling project to use the new Felix HC API. Generally make the package import to optional (to make the base functionality still available if the HC framework is not available) was:Migrate all health checks in Sling project to use the new Felix HC API. > Migrate all existing Sling Health Checks to Felix HC API > > > Key: SLING-8354 > URL: https://issues.apache.org/jira/browse/SLING-8354 > Project: Sling > Issue Type: New Feature > Components: Health Check >Reporter: Georg Henzler >Assignee: Georg Henzler >Priority: Major > > Migrate all health checks in Sling project to use the new Felix HC API. > Generally make the package import to optional (to make the base functionality > still available if the HC framework is not available) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [sling-org-apache-sling-dynamic-include] geetika95 commented on pull request #13: SLING-9045 - Rebase of PR #1 - Adding option to disable URL params check
geetika95 commented on pull request #13: URL: https://github.com/apache/sling-org-apache-sling-dynamic-include/pull/13#issuecomment-668843166 We tried testing this feature in one of the projects, SDI functionality doesn't seem to work at all. Even the default behavior of SDI without the URL params is not working with the latest version. Is there any special configuration we need to do/add to make it work? Current Version: 3.2.0 with AEM 6.5.3 (Functionality not working at all) Previous Version: 3.1.2 with AEM 6.5.3 (Working as expected) This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Closed] (SLING-9605) Upgrade to parent 39
[
https://issues.apache.org/jira/browse/SLING-9605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Norman closed SLING-9605.
--
Completed with the 2.2.10 release
> Upgrade to parent 39
>
>
> Key: SLING-9605
> URL: https://issues.apache.org/jira/browse/SLING-9605
> Project: Sling
> Issue Type: Sub-task
>Reporter: Eric Norman
>Assignee: Eric Norman
>Priority: Minor
> Fix For: JCR Jackrabbit User Manager 2.2.10
>
>
> Update to version 39 of the {{sling-bundle-parent}} pom, in order to allow
> builds with Java 11 and above.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (SLING-7937) A post to update a nested "Date" property for a user or group sets the property at the wrong path
[ https://issues.apache.org/jira/browse/SLING-7937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Norman closed SLING-7937. -- Completed with the 2.2.10 release > A post to update a nested "Date" property for a user or group sets the > property at the wrong path > - > > Key: SLING-7937 > URL: https://issues.apache.org/jira/browse/SLING-7937 > Project: Sling > Issue Type: Bug >Affects Versions: JCR Jackrabbit User Manager 2.2.8 >Reporter: Eric Norman >Assignee: Eric Norman >Priority: Major > Fix For: JCR Jackrabbit User Manager 2.2.10 > > > When posting an update for a user or group, the handing of nested "Date" > properties is not correct as it is setting the property at the wrong path. > It is ignoring the posted property path and setting the value using the > property name as the path. So post an update to "nested/key1" would store > the value at "key1" instead of "nested/key1". > > For example: > # create a test user > curl -u admin -F:name=user1 -Fpwd=password -FpwdConfirm=password > [http://localhost:8080/system/userManager/user.create.html] > # update a nested date property for the user > curl -u user1 "-Fnested/key1=2018-10-10" "-Fnested/key1@TypeHint=Date" > [http://localhost:8080/system/userManager/user/user1.update.html] > # fetching the user resource json should not contain the "key1" value > curl -u user1 [http://localhost:8080/system/userManager/user/user1.json] > # instead it is expected that the "nested/key1" should be stored under the > /home/users/*/*[rep:User]/nested folder for the user > curl -u user1 > http://localhost:8080/user_path_from_json_from_#3_here/nested.json -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Closed] (SLING-9604) Resolve deprecation warning about usage of Bnd versioning annotations
[
https://issues.apache.org/jira/browse/SLING-9604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Norman closed SLING-9604.
--
Completed with the 2.2.10 release
> Resolve deprecation warning about usage of Bnd versioning annotations
> -
>
> Key: SLING-9604
> URL: https://issues.apache.org/jira/browse/SLING-9604
> Project: Sling
> Issue Type: Bug
>Reporter: Eric Norman
>Assignee: Eric Norman
>Priority: Minor
> Fix For: JCR Jackrabbit User Manager 2.2.10
>
>
> During the maven build, the following warning is logged to the console. To
> resolve this warning, the dependency on the org.apache.sling.api artifact
> must be increased to version 2.15.0 or later where the migration to OSGi
> versioning annotations was already done.
>
> {{[WARNING] Bundle
> org.apache.sling:org.apache.sling.jcr.jackrabbit.usermanager:bundle:2.2.9-SNAPSHOT
> : aQute.bnd.annotation.ProviderType annotation used in class
> org.apache.sling.api.request.RequestParameter. Bnd versioning annotations are
> deprecated as of Bnd 3.2 and support will be removed in Bnd 4.0. Please
> change to use OSGi versioning annotations.}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
Re: [VOTE] Release Apache Sling JCR Base 3.1.4
+1 On Tue, Aug 4, 2020 at 12:11 PM Andreas Schaefer wrote: > +1 (non-binding) > > - Andy > > > On Aug 4, 2020, at 8:22 AM, Robert Munteanu wrote: > > > > Hi, > > > > We solved 3 issues in this release: > > https://issues.apache.org/jira/browse/SLING/fixforversion/12348659 > > > > Staging repository: > > https://repository.apache.org/content/repositories/orgapachesling-2314/ > > > > You can use this UNIX script to download the release and verify the > signatures: > > > https://gitbox.apache.org/repos/asf?p=sling-tooling-release.git;a=blob;f=check_staged_release.sh;hb=HEAD > > > > Usage: > > sh check_staged_release.sh 2314 /tmp/sling-staging > > > > Please vote to approve this release: > > > > [ ] +1 Approve the release > > [ ] 0 Don't care > > [ ] -1 Don't release, because ... > > > > This majority vote is open for at least 72 hours. > > > > Regards, > > Robert Munteanu > >
Re: [RESULT] [VOTE] Release Apache Sling JCR Jackrabbit User Manager version 2.2.10
Hi Robert, Thank you for the assist. I will proceed with the remaining release activities. Regards, Eric On Tue, Aug 4, 2020 at 12:27 AM Robert Munteanu wrote: > On Mon, 2020-08-03 at 10:00 -0700, Eric Norman wrote: > > I need someone from the PMC to copy the release to the Sling dist > > directory. > > Done in r40850. > > Thanks, > Robert > >
Re: [VOTE] Release Apache Sling JCR Base 3.1.4
+1 (non-binding) - Andy > On Aug 4, 2020, at 8:22 AM, Robert Munteanu wrote: > > Hi, > > We solved 3 issues in this release: > https://issues.apache.org/jira/browse/SLING/fixforversion/12348659 > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-2314/ > > You can use this UNIX script to download the release and verify the > signatures: > https://gitbox.apache.org/repos/asf?p=sling-tooling-release.git;a=blob;f=check_staged_release.sh;hb=HEAD > > Usage: > sh check_staged_release.sh 2314 /tmp/sling-staging > > Please vote to approve this release: > > [ ] +1 Approve the release > [ ] 0 Don't care > [ ] -1 Don't release, because ... > > This majority vote is open for at least 72 hours. > > Regards, > Robert Munteanu
[jira] [Closed] (SLING-9249) Exception thrown when running the Sling Starter - UseRuntimeException: The bindUseProvider method has thrown an exception
[
https://issues.apache.org/jira/browse/SLING-9249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radu Cotescu closed SLING-9249.
---
> Exception thrown when running the Sling Starter - UseRuntimeException: The
> bindUseProvider method has thrown an exception
> -
>
> Key: SLING-9249
> URL: https://issues.apache.org/jira/browse/SLING-9249
> Project: Sling
> Issue Type: Bug
> Components: Scripting
>Affects Versions: Scripting HTL Engine 1.3.2-1.4.0
>Reporter: Robert Munteanu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: Scripting HTL Engine 1.4.0-1.4.0
>
> Attachments: log.txt
>
>
> To reproduce: run {{mvn clean verify}} on the current sling starter -
> org.apache.sling.starter-11-77-g85dfd1c.
> I see the following error logged on the console:
> {noformat}ERROR: bundle org.apache.sling.scripting.sightly:1.3.2.0
> (167)[org.apache.sling.scripting.sightly.impl.engine.extension.use.UseRuntimeExtension(311)]
> : The bindUseProvider method has thrown an exception
> java.lang.NullPointerException
> at
> java.base/java.util.concurrent.ConcurrentSkipListMap.put(ConcurrentSkipListMap.java:1345)
> at
> org.apache.sling.scripting.sightly.impl.engine.extension.use.UseRuntimeExtension.bindUseProvider(UseRuntimeExtension.java:91)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.apache.felix.scr.impl.inject.methods.BaseMethod.invokeMethod(BaseMethod.java:228)
> at
> org.apache.felix.scr.impl.inject.methods.BaseMethod.access$500(BaseMethod.java:41)
> at
> org.apache.felix.scr.impl.inject.methods.BaseMethod$Resolved.invoke(BaseMethod.java:664)
> at
> org.apache.felix.scr.impl.inject.methods.BaseMethod.invoke(BaseMethod.java:510)
> at
> org.apache.felix.scr.impl.inject.methods.BindMethod.invoke(BindMethod.java:42)
> at
> org.apache.felix.scr.impl.manager.DependencyManager.doInvokeBindMethod(DependencyManager.java:1813)
> at
> org.apache.felix.scr.impl.manager.DependencyManager.invokeBindMethod(DependencyManager.java:1788)
> at
> org.apache.felix.scr.impl.manager.SingleComponentManager.invokeBindMethod(SingleComponentManager.java:435)
> at
> org.apache.felix.scr.impl.manager.DependencyManager$MultipleDynamicCustomizer.addedService(DependencyManager.java:325)
> at
> org.apache.felix.scr.impl.manager.DependencyManager$MultipleDynamicCustomizer.addedService(DependencyManager.java:294)
> at
> org.apache.felix.scr.impl.manager.ServiceTracker$Tracked.customizerAdded(ServiceTracker.java:1216)
> at
> org.apache.felix.scr.impl.manager.ServiceTracker$Tracked.customizerAdded(ServiceTracker.java:1137)
> at
> org.apache.felix.scr.impl.manager.ServiceTracker$AbstractTracked.trackAdding(ServiceTracker.java:944)
> at
> org.apache.felix.scr.impl.manager.ServiceTracker$AbstractTracked.track(ServiceTracker.java:880)
> at
> org.apache.felix.scr.impl.manager.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:1168)
> at
> org.apache.felix.scr.impl.BundleComponentActivator$ListenerInfo.serviceChanged(BundleComponentActivator.java:125)
> at
> org.apache.felix.framework.EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:990)
> at
> org.apache.felix.framework.EventDispatcher.fireEventImmediately(EventDispatcher.java:838)
> at
> org.apache.felix.framework.EventDispatcher.fireServiceEvent(EventDispatcher.java:545)
> at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:4833)
> at org.apache.felix.framework.Felix.registerService(Felix.java:3804)
> at
> org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:328)
> at
> org.apache.felix.scr.impl.manager.AbstractComponentManager$3.register(AbstractComponentManager.java:906)
> at
> org.apache.felix.scr.impl.manager.AbstractComponentManager$3.register(AbstractComponentManager.java:892)
> at
> org.apache.felix.scr.impl.manager.RegistrationManager.changeRegistration(RegistrationManager.java:128)
> at
> org.apache.felix.scr.impl.manager.AbstractComponentManager.registerService(AbstractComponentManager.java:959)
> at
> org.apache.felix.scr.impl.manager.AbstractComponentManager.activateInternal(AbstractComponentManager.java:732)
> at
>
[jira] [Resolved] (SLING-9249) Exception thrown when running the Sling Starter - UseRuntimeException: The bindUseProvider method has thrown an exception
[
https://issues.apache.org/jira/browse/SLING-9249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radu Cotescu resolved SLING-9249.
-
Fix Version/s: Scripting HTL Engine 1.4.0-1.4.0
Resolution: Fixed
> Exception thrown when running the Sling Starter - UseRuntimeException: The
> bindUseProvider method has thrown an exception
> -
>
> Key: SLING-9249
> URL: https://issues.apache.org/jira/browse/SLING-9249
> Project: Sling
> Issue Type: Bug
> Components: Scripting
>Affects Versions: Scripting HTL Engine 1.3.2-1.4.0
>Reporter: Robert Munteanu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: Scripting HTL Engine 1.4.0-1.4.0
>
> Attachments: log.txt
>
>
> To reproduce: run {{mvn clean verify}} on the current sling starter -
> org.apache.sling.starter-11-77-g85dfd1c.
> I see the following error logged on the console:
> {noformat}ERROR: bundle org.apache.sling.scripting.sightly:1.3.2.0
> (167)[org.apache.sling.scripting.sightly.impl.engine.extension.use.UseRuntimeExtension(311)]
> : The bindUseProvider method has thrown an exception
> java.lang.NullPointerException
> at
> java.base/java.util.concurrent.ConcurrentSkipListMap.put(ConcurrentSkipListMap.java:1345)
> at
> org.apache.sling.scripting.sightly.impl.engine.extension.use.UseRuntimeExtension.bindUseProvider(UseRuntimeExtension.java:91)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.apache.felix.scr.impl.inject.methods.BaseMethod.invokeMethod(BaseMethod.java:228)
> at
> org.apache.felix.scr.impl.inject.methods.BaseMethod.access$500(BaseMethod.java:41)
> at
> org.apache.felix.scr.impl.inject.methods.BaseMethod$Resolved.invoke(BaseMethod.java:664)
> at
> org.apache.felix.scr.impl.inject.methods.BaseMethod.invoke(BaseMethod.java:510)
> at
> org.apache.felix.scr.impl.inject.methods.BindMethod.invoke(BindMethod.java:42)
> at
> org.apache.felix.scr.impl.manager.DependencyManager.doInvokeBindMethod(DependencyManager.java:1813)
> at
> org.apache.felix.scr.impl.manager.DependencyManager.invokeBindMethod(DependencyManager.java:1788)
> at
> org.apache.felix.scr.impl.manager.SingleComponentManager.invokeBindMethod(SingleComponentManager.java:435)
> at
> org.apache.felix.scr.impl.manager.DependencyManager$MultipleDynamicCustomizer.addedService(DependencyManager.java:325)
> at
> org.apache.felix.scr.impl.manager.DependencyManager$MultipleDynamicCustomizer.addedService(DependencyManager.java:294)
> at
> org.apache.felix.scr.impl.manager.ServiceTracker$Tracked.customizerAdded(ServiceTracker.java:1216)
> at
> org.apache.felix.scr.impl.manager.ServiceTracker$Tracked.customizerAdded(ServiceTracker.java:1137)
> at
> org.apache.felix.scr.impl.manager.ServiceTracker$AbstractTracked.trackAdding(ServiceTracker.java:944)
> at
> org.apache.felix.scr.impl.manager.ServiceTracker$AbstractTracked.track(ServiceTracker.java:880)
> at
> org.apache.felix.scr.impl.manager.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:1168)
> at
> org.apache.felix.scr.impl.BundleComponentActivator$ListenerInfo.serviceChanged(BundleComponentActivator.java:125)
> at
> org.apache.felix.framework.EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:990)
> at
> org.apache.felix.framework.EventDispatcher.fireEventImmediately(EventDispatcher.java:838)
> at
> org.apache.felix.framework.EventDispatcher.fireServiceEvent(EventDispatcher.java:545)
> at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:4833)
> at org.apache.felix.framework.Felix.registerService(Felix.java:3804)
> at
> org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:328)
> at
> org.apache.felix.scr.impl.manager.AbstractComponentManager$3.register(AbstractComponentManager.java:906)
> at
> org.apache.felix.scr.impl.manager.AbstractComponentManager$3.register(AbstractComponentManager.java:892)
> at
> org.apache.felix.scr.impl.manager.RegistrationManager.changeRegistration(RegistrationManager.java:128)
> at
> org.apache.felix.scr.impl.manager.AbstractComponentManager.registerService(AbstractComponentManager.java:959)
> at
>
[jira] [Commented] (SLING-9249) Exception thrown when running the Sling Starter - UseRuntimeException: The bindUseProvider method has thrown an exception
[
https://issues.apache.org/jira/browse/SLING-9249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170911#comment-17170911
]
Radu Cotescu commented on SLING-9249:
-
Thanks! I'll close it then.
> Exception thrown when running the Sling Starter - UseRuntimeException: The
> bindUseProvider method has thrown an exception
> -
>
> Key: SLING-9249
> URL: https://issues.apache.org/jira/browse/SLING-9249
> Project: Sling
> Issue Type: Bug
> Components: Scripting
>Affects Versions: Scripting HTL Engine 1.3.2-1.4.0
>Reporter: Robert Munteanu
>Assignee: Radu Cotescu
>Priority: Major
> Attachments: log.txt
>
>
> To reproduce: run {{mvn clean verify}} on the current sling starter -
> org.apache.sling.starter-11-77-g85dfd1c.
> I see the following error logged on the console:
> {noformat}ERROR: bundle org.apache.sling.scripting.sightly:1.3.2.0
> (167)[org.apache.sling.scripting.sightly.impl.engine.extension.use.UseRuntimeExtension(311)]
> : The bindUseProvider method has thrown an exception
> java.lang.NullPointerException
> at
> java.base/java.util.concurrent.ConcurrentSkipListMap.put(ConcurrentSkipListMap.java:1345)
> at
> org.apache.sling.scripting.sightly.impl.engine.extension.use.UseRuntimeExtension.bindUseProvider(UseRuntimeExtension.java:91)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.apache.felix.scr.impl.inject.methods.BaseMethod.invokeMethod(BaseMethod.java:228)
> at
> org.apache.felix.scr.impl.inject.methods.BaseMethod.access$500(BaseMethod.java:41)
> at
> org.apache.felix.scr.impl.inject.methods.BaseMethod$Resolved.invoke(BaseMethod.java:664)
> at
> org.apache.felix.scr.impl.inject.methods.BaseMethod.invoke(BaseMethod.java:510)
> at
> org.apache.felix.scr.impl.inject.methods.BindMethod.invoke(BindMethod.java:42)
> at
> org.apache.felix.scr.impl.manager.DependencyManager.doInvokeBindMethod(DependencyManager.java:1813)
> at
> org.apache.felix.scr.impl.manager.DependencyManager.invokeBindMethod(DependencyManager.java:1788)
> at
> org.apache.felix.scr.impl.manager.SingleComponentManager.invokeBindMethod(SingleComponentManager.java:435)
> at
> org.apache.felix.scr.impl.manager.DependencyManager$MultipleDynamicCustomizer.addedService(DependencyManager.java:325)
> at
> org.apache.felix.scr.impl.manager.DependencyManager$MultipleDynamicCustomizer.addedService(DependencyManager.java:294)
> at
> org.apache.felix.scr.impl.manager.ServiceTracker$Tracked.customizerAdded(ServiceTracker.java:1216)
> at
> org.apache.felix.scr.impl.manager.ServiceTracker$Tracked.customizerAdded(ServiceTracker.java:1137)
> at
> org.apache.felix.scr.impl.manager.ServiceTracker$AbstractTracked.trackAdding(ServiceTracker.java:944)
> at
> org.apache.felix.scr.impl.manager.ServiceTracker$AbstractTracked.track(ServiceTracker.java:880)
> at
> org.apache.felix.scr.impl.manager.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:1168)
> at
> org.apache.felix.scr.impl.BundleComponentActivator$ListenerInfo.serviceChanged(BundleComponentActivator.java:125)
> at
> org.apache.felix.framework.EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:990)
> at
> org.apache.felix.framework.EventDispatcher.fireEventImmediately(EventDispatcher.java:838)
> at
> org.apache.felix.framework.EventDispatcher.fireServiceEvent(EventDispatcher.java:545)
> at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:4833)
> at org.apache.felix.framework.Felix.registerService(Felix.java:3804)
> at
> org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:328)
> at
> org.apache.felix.scr.impl.manager.AbstractComponentManager$3.register(AbstractComponentManager.java:906)
> at
> org.apache.felix.scr.impl.manager.AbstractComponentManager$3.register(AbstractComponentManager.java:892)
> at
> org.apache.felix.scr.impl.manager.RegistrationManager.changeRegistration(RegistrationManager.java:128)
> at
> org.apache.felix.scr.impl.manager.AbstractComponentManager.registerService(AbstractComponentManager.java:959)
> at
> org.apache.felix.scr.impl.manager.AbstractComponentManager.activateInternal(AbstractComponentManager.java:732)
> at
>
[jira] [Comment Edited] (SLING-9249) Exception thrown when running the Sling Starter - UseRuntimeException: The bindUseProvider method has thrown an exception
[
https://issues.apache.org/jira/browse/SLING-9249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170905#comment-17170905
]
Robert Munteanu edited comment on SLING-9249 at 8/4/20, 3:46 PM:
-
[~radu] - no, I don't see this error anymore.
was (Author: rombert):
[~radu] - no, I don't this error anymore.
> Exception thrown when running the Sling Starter - UseRuntimeException: The
> bindUseProvider method has thrown an exception
> -
>
> Key: SLING-9249
> URL: https://issues.apache.org/jira/browse/SLING-9249
> Project: Sling
> Issue Type: Bug
> Components: Scripting
>Affects Versions: Scripting HTL Engine 1.3.2-1.4.0
>Reporter: Robert Munteanu
>Assignee: Radu Cotescu
>Priority: Major
> Attachments: log.txt
>
>
> To reproduce: run {{mvn clean verify}} on the current sling starter -
> org.apache.sling.starter-11-77-g85dfd1c.
> I see the following error logged on the console:
> {noformat}ERROR: bundle org.apache.sling.scripting.sightly:1.3.2.0
> (167)[org.apache.sling.scripting.sightly.impl.engine.extension.use.UseRuntimeExtension(311)]
> : The bindUseProvider method has thrown an exception
> java.lang.NullPointerException
> at
> java.base/java.util.concurrent.ConcurrentSkipListMap.put(ConcurrentSkipListMap.java:1345)
> at
> org.apache.sling.scripting.sightly.impl.engine.extension.use.UseRuntimeExtension.bindUseProvider(UseRuntimeExtension.java:91)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.apache.felix.scr.impl.inject.methods.BaseMethod.invokeMethod(BaseMethod.java:228)
> at
> org.apache.felix.scr.impl.inject.methods.BaseMethod.access$500(BaseMethod.java:41)
> at
> org.apache.felix.scr.impl.inject.methods.BaseMethod$Resolved.invoke(BaseMethod.java:664)
> at
> org.apache.felix.scr.impl.inject.methods.BaseMethod.invoke(BaseMethod.java:510)
> at
> org.apache.felix.scr.impl.inject.methods.BindMethod.invoke(BindMethod.java:42)
> at
> org.apache.felix.scr.impl.manager.DependencyManager.doInvokeBindMethod(DependencyManager.java:1813)
> at
> org.apache.felix.scr.impl.manager.DependencyManager.invokeBindMethod(DependencyManager.java:1788)
> at
> org.apache.felix.scr.impl.manager.SingleComponentManager.invokeBindMethod(SingleComponentManager.java:435)
> at
> org.apache.felix.scr.impl.manager.DependencyManager$MultipleDynamicCustomizer.addedService(DependencyManager.java:325)
> at
> org.apache.felix.scr.impl.manager.DependencyManager$MultipleDynamicCustomizer.addedService(DependencyManager.java:294)
> at
> org.apache.felix.scr.impl.manager.ServiceTracker$Tracked.customizerAdded(ServiceTracker.java:1216)
> at
> org.apache.felix.scr.impl.manager.ServiceTracker$Tracked.customizerAdded(ServiceTracker.java:1137)
> at
> org.apache.felix.scr.impl.manager.ServiceTracker$AbstractTracked.trackAdding(ServiceTracker.java:944)
> at
> org.apache.felix.scr.impl.manager.ServiceTracker$AbstractTracked.track(ServiceTracker.java:880)
> at
> org.apache.felix.scr.impl.manager.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:1168)
> at
> org.apache.felix.scr.impl.BundleComponentActivator$ListenerInfo.serviceChanged(BundleComponentActivator.java:125)
> at
> org.apache.felix.framework.EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:990)
> at
> org.apache.felix.framework.EventDispatcher.fireEventImmediately(EventDispatcher.java:838)
> at
> org.apache.felix.framework.EventDispatcher.fireServiceEvent(EventDispatcher.java:545)
> at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:4833)
> at org.apache.felix.framework.Felix.registerService(Felix.java:3804)
> at
> org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:328)
> at
> org.apache.felix.scr.impl.manager.AbstractComponentManager$3.register(AbstractComponentManager.java:906)
> at
> org.apache.felix.scr.impl.manager.AbstractComponentManager$3.register(AbstractComponentManager.java:892)
> at
> org.apache.felix.scr.impl.manager.RegistrationManager.changeRegistration(RegistrationManager.java:128)
> at
> org.apache.felix.scr.impl.manager.AbstractComponentManager.registerService(AbstractComponentManager.java:959)
> at
>
[jira] [Commented] (SLING-9628) Send log messages from subscriber to publisher
[ https://issues.apache.org/jira/browse/SLING-9628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170907#comment-17170907 ] Timothee Maret commented on SLING-9628: --- Do we really need a new message type ? How about adding the error log message in the existing How about adding the log message (error) in the existing DiscoveryMessage ? The DiscoveryMessage message would inform about the error message in addition to the number of retries which is already carried. > Send log messages from subscriber to publisher > -- > > Key: SLING-9628 > URL: https://issues.apache.org/jira/browse/SLING-9628 > Project: Sling > Issue Type: Improvement > Components: Content Distribution >Reporter: Christian Schneider >Assignee: Christian Schneider >Priority: Major > Fix For: Content Distribution Journal Core 0.1.18, Content > Distribution Journal Kafka 0.1.6, Content Distribution Journal Messages 0.1.10 > > > In the content distribution UI we can display a distribution log per agent. > Currently this log only shows that package messages are sent out. > This issue is about also showing successfully imported packages as well as > errors during import on the subscriber side. > The idea is to send a new message type LogMessage on the discovery topic. > These messages are received by the DiscoveryService and added to the > DIstributionLog. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (SLING-9249) Exception thrown when running the Sling Starter - UseRuntimeException: The bindUseProvider method has thrown an exception
[
https://issues.apache.org/jira/browse/SLING-9249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170905#comment-17170905
]
Robert Munteanu commented on SLING-9249:
[~radu] - no, I don't this error anymore.
> Exception thrown when running the Sling Starter - UseRuntimeException: The
> bindUseProvider method has thrown an exception
> -
>
> Key: SLING-9249
> URL: https://issues.apache.org/jira/browse/SLING-9249
> Project: Sling
> Issue Type: Bug
> Components: Scripting
>Affects Versions: Scripting HTL Engine 1.3.2-1.4.0
>Reporter: Robert Munteanu
>Assignee: Radu Cotescu
>Priority: Major
> Attachments: log.txt
>
>
> To reproduce: run {{mvn clean verify}} on the current sling starter -
> org.apache.sling.starter-11-77-g85dfd1c.
> I see the following error logged on the console:
> {noformat}ERROR: bundle org.apache.sling.scripting.sightly:1.3.2.0
> (167)[org.apache.sling.scripting.sightly.impl.engine.extension.use.UseRuntimeExtension(311)]
> : The bindUseProvider method has thrown an exception
> java.lang.NullPointerException
> at
> java.base/java.util.concurrent.ConcurrentSkipListMap.put(ConcurrentSkipListMap.java:1345)
> at
> org.apache.sling.scripting.sightly.impl.engine.extension.use.UseRuntimeExtension.bindUseProvider(UseRuntimeExtension.java:91)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.apache.felix.scr.impl.inject.methods.BaseMethod.invokeMethod(BaseMethod.java:228)
> at
> org.apache.felix.scr.impl.inject.methods.BaseMethod.access$500(BaseMethod.java:41)
> at
> org.apache.felix.scr.impl.inject.methods.BaseMethod$Resolved.invoke(BaseMethod.java:664)
> at
> org.apache.felix.scr.impl.inject.methods.BaseMethod.invoke(BaseMethod.java:510)
> at
> org.apache.felix.scr.impl.inject.methods.BindMethod.invoke(BindMethod.java:42)
> at
> org.apache.felix.scr.impl.manager.DependencyManager.doInvokeBindMethod(DependencyManager.java:1813)
> at
> org.apache.felix.scr.impl.manager.DependencyManager.invokeBindMethod(DependencyManager.java:1788)
> at
> org.apache.felix.scr.impl.manager.SingleComponentManager.invokeBindMethod(SingleComponentManager.java:435)
> at
> org.apache.felix.scr.impl.manager.DependencyManager$MultipleDynamicCustomizer.addedService(DependencyManager.java:325)
> at
> org.apache.felix.scr.impl.manager.DependencyManager$MultipleDynamicCustomizer.addedService(DependencyManager.java:294)
> at
> org.apache.felix.scr.impl.manager.ServiceTracker$Tracked.customizerAdded(ServiceTracker.java:1216)
> at
> org.apache.felix.scr.impl.manager.ServiceTracker$Tracked.customizerAdded(ServiceTracker.java:1137)
> at
> org.apache.felix.scr.impl.manager.ServiceTracker$AbstractTracked.trackAdding(ServiceTracker.java:944)
> at
> org.apache.felix.scr.impl.manager.ServiceTracker$AbstractTracked.track(ServiceTracker.java:880)
> at
> org.apache.felix.scr.impl.manager.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:1168)
> at
> org.apache.felix.scr.impl.BundleComponentActivator$ListenerInfo.serviceChanged(BundleComponentActivator.java:125)
> at
> org.apache.felix.framework.EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:990)
> at
> org.apache.felix.framework.EventDispatcher.fireEventImmediately(EventDispatcher.java:838)
> at
> org.apache.felix.framework.EventDispatcher.fireServiceEvent(EventDispatcher.java:545)
> at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:4833)
> at org.apache.felix.framework.Felix.registerService(Felix.java:3804)
> at
> org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:328)
> at
> org.apache.felix.scr.impl.manager.AbstractComponentManager$3.register(AbstractComponentManager.java:906)
> at
> org.apache.felix.scr.impl.manager.AbstractComponentManager$3.register(AbstractComponentManager.java:892)
> at
> org.apache.felix.scr.impl.manager.RegistrationManager.changeRegistration(RegistrationManager.java:128)
> at
> org.apache.felix.scr.impl.manager.AbstractComponentManager.registerService(AbstractComponentManager.java:959)
> at
> org.apache.felix.scr.impl.manager.AbstractComponentManager.activateInternal(AbstractComponentManager.java:732)
> at
>
[jira] [Commented] (SLING-9249) Exception thrown when running the Sling Starter - UseRuntimeException: The bindUseProvider method has thrown an exception
[
https://issues.apache.org/jira/browse/SLING-9249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170883#comment-17170883
]
Radu Cotescu commented on SLING-9249:
-
I think this issue has been fixed via SLING-9320. I cannot reproduce it on the
latest starter app. [~rombert], could you please confirm?
> Exception thrown when running the Sling Starter - UseRuntimeException: The
> bindUseProvider method has thrown an exception
> -
>
> Key: SLING-9249
> URL: https://issues.apache.org/jira/browse/SLING-9249
> Project: Sling
> Issue Type: Bug
> Components: Scripting
>Affects Versions: Scripting HTL Engine 1.3.2-1.4.0
>Reporter: Robert Munteanu
>Assignee: Radu Cotescu
>Priority: Major
> Attachments: log.txt
>
>
> To reproduce: run {{mvn clean verify}} on the current sling starter -
> org.apache.sling.starter-11-77-g85dfd1c.
> I see the following error logged on the console:
> {noformat}ERROR: bundle org.apache.sling.scripting.sightly:1.3.2.0
> (167)[org.apache.sling.scripting.sightly.impl.engine.extension.use.UseRuntimeExtension(311)]
> : The bindUseProvider method has thrown an exception
> java.lang.NullPointerException
> at
> java.base/java.util.concurrent.ConcurrentSkipListMap.put(ConcurrentSkipListMap.java:1345)
> at
> org.apache.sling.scripting.sightly.impl.engine.extension.use.UseRuntimeExtension.bindUseProvider(UseRuntimeExtension.java:91)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at
> org.apache.felix.scr.impl.inject.methods.BaseMethod.invokeMethod(BaseMethod.java:228)
> at
> org.apache.felix.scr.impl.inject.methods.BaseMethod.access$500(BaseMethod.java:41)
> at
> org.apache.felix.scr.impl.inject.methods.BaseMethod$Resolved.invoke(BaseMethod.java:664)
> at
> org.apache.felix.scr.impl.inject.methods.BaseMethod.invoke(BaseMethod.java:510)
> at
> org.apache.felix.scr.impl.inject.methods.BindMethod.invoke(BindMethod.java:42)
> at
> org.apache.felix.scr.impl.manager.DependencyManager.doInvokeBindMethod(DependencyManager.java:1813)
> at
> org.apache.felix.scr.impl.manager.DependencyManager.invokeBindMethod(DependencyManager.java:1788)
> at
> org.apache.felix.scr.impl.manager.SingleComponentManager.invokeBindMethod(SingleComponentManager.java:435)
> at
> org.apache.felix.scr.impl.manager.DependencyManager$MultipleDynamicCustomizer.addedService(DependencyManager.java:325)
> at
> org.apache.felix.scr.impl.manager.DependencyManager$MultipleDynamicCustomizer.addedService(DependencyManager.java:294)
> at
> org.apache.felix.scr.impl.manager.ServiceTracker$Tracked.customizerAdded(ServiceTracker.java:1216)
> at
> org.apache.felix.scr.impl.manager.ServiceTracker$Tracked.customizerAdded(ServiceTracker.java:1137)
> at
> org.apache.felix.scr.impl.manager.ServiceTracker$AbstractTracked.trackAdding(ServiceTracker.java:944)
> at
> org.apache.felix.scr.impl.manager.ServiceTracker$AbstractTracked.track(ServiceTracker.java:880)
> at
> org.apache.felix.scr.impl.manager.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:1168)
> at
> org.apache.felix.scr.impl.BundleComponentActivator$ListenerInfo.serviceChanged(BundleComponentActivator.java:125)
> at
> org.apache.felix.framework.EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:990)
> at
> org.apache.felix.framework.EventDispatcher.fireEventImmediately(EventDispatcher.java:838)
> at
> org.apache.felix.framework.EventDispatcher.fireServiceEvent(EventDispatcher.java:545)
> at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:4833)
> at org.apache.felix.framework.Felix.registerService(Felix.java:3804)
> at
> org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:328)
> at
> org.apache.felix.scr.impl.manager.AbstractComponentManager$3.register(AbstractComponentManager.java:906)
> at
> org.apache.felix.scr.impl.manager.AbstractComponentManager$3.register(AbstractComponentManager.java:892)
> at
> org.apache.felix.scr.impl.manager.RegistrationManager.changeRegistration(RegistrationManager.java:128)
> at
> org.apache.felix.scr.impl.manager.AbstractComponentManager.registerService(AbstractComponentManager.java:959)
> at
>
Re: [VOTE] Release Apache Sling JCR Base 3.1.4
On Tue, 2020-08-04 at 15:22 +, 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 Base 3.1.4
Hi, We solved 3 issues in this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12348659 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-2314/ You can use this UNIX script to download the release and verify the signatures: https://gitbox.apache.org/repos/asf?p=sling-tooling-release.git;a=blob;f=check_staged_release.sh;hb=HEAD Usage: sh check_staged_release.sh 2314 /tmp/sling-staging Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This majority vote is open for at least 72 hours. Regards, Robert Munteanu
[jira] [Resolved] (SLING-9629) Jackrabbit RMI imports no longer marked as optional
[ https://issues.apache.org/jira/browse/SLING-9629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-9629. Resolution: Fixed Fixed with [sling-org-apache-sling-jcr-base commit 985bb2a|https://github.com/apache/sling-org-apache-sling-jcr-base/commit/985bb2a]. > Jackrabbit RMI imports no longer marked as optional > --- > > Key: SLING-9629 > URL: https://issues.apache.org/jira/browse/SLING-9629 > Project: Sling > Issue Type: Bug > Components: JCR >Reporter: Robert Munteanu >Assignee: Robert Munteanu >Priority: Critical > Fix For: JCR Base 3.1.4 > > > After the fix for SLING-9627 the org.apache.jackrabbit.rmi.client, > org.apache.jackrabbit.rmi.remote imports are no longer marked as optional. > This means the bundle does not resolve on deployments where the RMI bundles > are not present, which is unexpected and undesired. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (SLING-9627) jcr.base: update to parent pom 39 or newer
[ https://issues.apache.org/jira/browse/SLING-9627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-9627: --- Fix Version/s: (was: JCR Base 3.1.2) JCR Base 3.1.4 > jcr.base: update to parent pom 39 or newer > -- > > Key: SLING-9627 > URL: https://issues.apache.org/jira/browse/SLING-9627 > Project: Sling > Issue Type: Sub-task > Components: JCR >Reporter: Robert Munteanu >Assignee: Robert Munteanu >Priority: Major > Fix For: JCR Base 3.1.4 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (SLING-7811) NPE when repository is starting up due to repository manager shutdown
[
https://issues.apache.org/jira/browse/SLING-7811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu updated SLING-7811:
---
Fix Version/s: (was: JCR Base 3.1.2)
JCR Base 3.1.4
> NPE when repository is starting up due to repository manager shutdown
> -
>
> Key: SLING-7811
> URL: https://issues.apache.org/jira/browse/SLING-7811
> Project: Sling
> Issue Type: Bug
> Components: JCR
>Affects Versions: JCR Oak Server 1.1.4, JCR Base 3.0.4
>Reporter: Carsten Ziegeler
>Assignee: Robert Munteanu
>Priority: Major
> Fix For: JCR Base 3.1.4
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> With the latest Sling Starter, the following NPE occurs in the logs. It seems
> to be harmless, nevertheless we should fix it:
> For now I assigned it to both, JCR Base and Oak Server, as it's unclear which
> one it is. Interestingly we've released Oak Server 1.2.0 but are not using it
> in the starter.
> {noformat}
> 06.08.2018 15:45:18.396 *ERROR* [Apache Sling Repository Startup Thread]
> org.apache.sling.jcr.oak.server.internal.OakSlingRepositoryManager start:
> Uncaught Throwable trying to access Repository, calling stopRepository()
> java.lang.NullPointerException: null
> at
> com.google.common.base.Preconditions.checkNotNull(Preconditions.java:192)
> [com.google.guava:15.0.0]
> at org.apache.jackrabbit.oak.jcr.Jcr.with(Jcr.java:296)
> [org.apache.jackrabbit.oak-jcr:1.6.8]
> at
> org.apache.sling.jcr.oak.server.internal.OakSlingRepositoryManager.acquireRepository(OakSlingRepositoryManager.java:161)
> [org.apache.sling.jcr.oak.server:1.1.4]
> at
> org.apache.sling.jcr.base.AbstractSlingRepositoryManager.initializeAndRegisterRepositoryService(AbstractSlingRepositoryManager.java:471)
> [org.apache.sling.jcr.base:3.0.4]
> at
> org.apache.sling.jcr.base.AbstractSlingRepositoryManager.access$300(AbstractSlingRepositoryManager.java:85)
> [org.apache.sling.jcr.base:3.0.4]
> at
> org.apache.sling.jcr.base.AbstractSlingRepositoryManager$4.run(AbstractSlingRepositoryManager.java:455)
> [org.apache.sling.jcr.base:3.0.4]
> {noformat}
> The stack trace points to a null workspace name ( see
> https://github.com/apache/jackrabbit-oak/blob/jackrabbit-oak-1.6.8/oak-jcr/src/main/java/org/apache/jackrabbit/oak/jcr/Jcr.java#L296
> ).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[CANCELLED] [VOTE] Release Apache Sling JCR Base 3.1.2
I am cancelling the vote due to a regression https://issues.apache.org/jira/browse/SLING-9629 Thanks, Robert
[jira] [Created] (SLING-9629) Jackrabbit RMI imports no longer marked as optional
Robert Munteanu created SLING-9629: -- Summary: Jackrabbit RMI imports no longer marked as optional Key: SLING-9629 URL: https://issues.apache.org/jira/browse/SLING-9629 Project: Sling Issue Type: Bug Components: JCR Affects Versions: JCR Base 3.1.2 Reporter: Robert Munteanu Assignee: Robert Munteanu Fix For: JCR Base 3.1.4 After the fix for SLING-9627 the org.apache.jackrabbit.rmi.client, org.apache.jackrabbit.rmi.remote imports are no longer marked as optional. This means the bundle does not resolve on deployments where the RMI bundles are not present, which is unexpected and undesired. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (SLING-9628) Send log messages from subscriber to publisher
Christian Schneider created SLING-9628: -- Summary: Send log messages from subscriber to publisher Key: SLING-9628 URL: https://issues.apache.org/jira/browse/SLING-9628 Project: Sling Issue Type: Improvement Components: Content Distribution Reporter: Christian Schneider Assignee: Christian Schneider Fix For: Content Distribution Journal Core 0.1.18, Content Distribution Journal Kafka 0.1.6, Content Distribution Journal Messages 0.1.10 In the content distribution UI we can display a distribution log per agent. Currently this log only shows that package messages are sent out. This issue is about also showing successfully imported packages as well as errors during import on the subscriber side. The idea is to send a new message type LogMessage on the discovery topic. These messages are received by the DiscoveryService and added to the DIstributionLog. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (SLING-9118) Sling fails to start when database exists but 'sling' directory is missing
[ https://issues.apache.org/jira/browse/SLING-9118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170833#comment-17170833 ] Robert Munteanu commented on SLING-9118: [~carlosmunoz] [~benradey] - I have returned to this issue and created what I think is a definitive fix for SLING-7811. In my tests now the MongoDB-based setup is stable. If you have the time, you could try our jcr.base 3.1.2 release candidate, either pre-built from https://repository.apache.org/content/groups/staging/org/apache/sling/org.apache.sling.jcr.base/3.1.2/ or from source https://github.com/apache/sling-org-apache-sling-jcr-base/tree/org.apache.sling.jcr.base-3.1.2 . > Sling fails to start when database exists but 'sling' directory is missing > -- > > Key: SLING-9118 > URL: https://issues.apache.org/jira/browse/SLING-9118 > Project: Sling > Issue Type: Bug >Reporter: Ben Radey >Assignee: Robert Munteanu >Priority: Major > Attachments: drop-mongo.sh, error.log, fm-launch.zip, karaf.log, > recreateSlingReplicaSet.sh, run-mongo.sh, run-sling-initial.sh, > run-sling-second.sh, sling-startup-error.log.txt > > > # Create a persistent mongodb to use with Sling. > # Start sling using the mongodb. > # Stop sling. > # Remove 'sling' directory. > # Attempt to restart sling. Ultimately, sling fails to start. > > Steps to reproduce with attached scripts: > # Run [^run-mongo.sh] . This creates a MongoDB 3.6 container named > _mongo-sling_ > # Run [^run-sling-initial.sh]. This starts up Sling in the oak_mongo runmode, > shuts it down after it's (probably) started up > # Run [^run-sling-second.sh]. This moves away the sling directory and starts > up a new instance. This always fails > For cleanup, the [^drop-mongo.sh] script stops and removes the _mongo-sling_ > container. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: [VOTE] Release Apache Sling JCR Base 3.1.2
On Tue, 2020-08-04 at 14:23 +, Robert Munteanu wrote: > Please vote to approve this release: +1 Robert
[VOTE] Release Apache Sling JCR Base 3.1.2
Hi, We solved 2 issues in this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12348658 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-2313/ You can use this UNIX script to download the release and verify the signatures: https://gitbox.apache.org/repos/asf?p=sling-tooling-release.git;a=blob;f=check_staged_release.sh;hb=HEAD Usage: sh check_staged_release.sh 2313 /tmp/sling-staging Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This majority vote is open for at least 72 hours. Regards, Robert Munteanu
[jira] [Resolved] (SLING-9627) jcr.base: update to parent pom 39 or newer
[ https://issues.apache.org/jira/browse/SLING-9627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-9627. Resolution: Fixed Fixed with [sling-org-apache-sling-jcr-base commit 0f0898a|https://github.com/apache/sling-org-apache-sling-jcr-base/commit/0f0898a] > jcr.base: update to parent pom 39 or newer > -- > > Key: SLING-9627 > URL: https://issues.apache.org/jira/browse/SLING-9627 > Project: Sling > Issue Type: Sub-task > Components: JCR >Reporter: Robert Munteanu >Assignee: Robert Munteanu >Priority: Major > Fix For: JCR Base 3.1.2 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (SLING-9627) jcr.base: update to parent pom 39 or newer
Robert Munteanu created SLING-9627: -- Summary: jcr.base: update to parent pom 39 or newer Key: SLING-9627 URL: https://issues.apache.org/jira/browse/SLING-9627 Project: Sling Issue Type: Sub-task Components: JCR Reporter: Robert Munteanu Assignee: Robert Munteanu Fix For: JCR Base 3.1.2 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (SLING-7811) NPE when repository is starting up due to repository manager shutdown
[
https://issues.apache.org/jira/browse/SLING-7811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu resolved SLING-7811.
Resolution: Fixed
Fixed with https://github.com/apache/sling-org-apache-sling-jcr-base/pull/2
> NPE when repository is starting up due to repository manager shutdown
> -
>
> Key: SLING-7811
> URL: https://issues.apache.org/jira/browse/SLING-7811
> Project: Sling
> Issue Type: Bug
> Components: JCR
>Affects Versions: JCR Oak Server 1.1.4, JCR Base 3.0.4
>Reporter: Carsten Ziegeler
>Assignee: Robert Munteanu
>Priority: Major
> Fix For: JCR Oak Server 1.2.6
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> With the latest Sling Starter, the following NPE occurs in the logs. It seems
> to be harmless, nevertheless we should fix it:
> For now I assigned it to both, JCR Base and Oak Server, as it's unclear which
> one it is. Interestingly we've released Oak Server 1.2.0 but are not using it
> in the starter.
> {noformat}
> 06.08.2018 15:45:18.396 *ERROR* [Apache Sling Repository Startup Thread]
> org.apache.sling.jcr.oak.server.internal.OakSlingRepositoryManager start:
> Uncaught Throwable trying to access Repository, calling stopRepository()
> java.lang.NullPointerException: null
> at
> com.google.common.base.Preconditions.checkNotNull(Preconditions.java:192)
> [com.google.guava:15.0.0]
> at org.apache.jackrabbit.oak.jcr.Jcr.with(Jcr.java:296)
> [org.apache.jackrabbit.oak-jcr:1.6.8]
> at
> org.apache.sling.jcr.oak.server.internal.OakSlingRepositoryManager.acquireRepository(OakSlingRepositoryManager.java:161)
> [org.apache.sling.jcr.oak.server:1.1.4]
> at
> org.apache.sling.jcr.base.AbstractSlingRepositoryManager.initializeAndRegisterRepositoryService(AbstractSlingRepositoryManager.java:471)
> [org.apache.sling.jcr.base:3.0.4]
> at
> org.apache.sling.jcr.base.AbstractSlingRepositoryManager.access$300(AbstractSlingRepositoryManager.java:85)
> [org.apache.sling.jcr.base:3.0.4]
> at
> org.apache.sling.jcr.base.AbstractSlingRepositoryManager$4.run(AbstractSlingRepositoryManager.java:455)
> [org.apache.sling.jcr.base:3.0.4]
> {noformat}
> The stack trace points to a null workspace name ( see
> https://github.com/apache/jackrabbit-oak/blob/jackrabbit-oak-1.6.8/oak-jcr/src/main/java/org/apache/jackrabbit/oak/jcr/Jcr.java#L296
> ).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (SLING-7811) NPE when repository is starting up due to repository manager shutdown
[
https://issues.apache.org/jira/browse/SLING-7811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu updated SLING-7811:
---
Fix Version/s: (was: JCR Oak Server 1.2.6)
JCR Base 3.1.2
> NPE when repository is starting up due to repository manager shutdown
> -
>
> Key: SLING-7811
> URL: https://issues.apache.org/jira/browse/SLING-7811
> Project: Sling
> Issue Type: Bug
> Components: JCR
>Affects Versions: JCR Oak Server 1.1.4, JCR Base 3.0.4
>Reporter: Carsten Ziegeler
>Assignee: Robert Munteanu
>Priority: Major
> Fix For: JCR Base 3.1.2
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> With the latest Sling Starter, the following NPE occurs in the logs. It seems
> to be harmless, nevertheless we should fix it:
> For now I assigned it to both, JCR Base and Oak Server, as it's unclear which
> one it is. Interestingly we've released Oak Server 1.2.0 but are not using it
> in the starter.
> {noformat}
> 06.08.2018 15:45:18.396 *ERROR* [Apache Sling Repository Startup Thread]
> org.apache.sling.jcr.oak.server.internal.OakSlingRepositoryManager start:
> Uncaught Throwable trying to access Repository, calling stopRepository()
> java.lang.NullPointerException: null
> at
> com.google.common.base.Preconditions.checkNotNull(Preconditions.java:192)
> [com.google.guava:15.0.0]
> at org.apache.jackrabbit.oak.jcr.Jcr.with(Jcr.java:296)
> [org.apache.jackrabbit.oak-jcr:1.6.8]
> at
> org.apache.sling.jcr.oak.server.internal.OakSlingRepositoryManager.acquireRepository(OakSlingRepositoryManager.java:161)
> [org.apache.sling.jcr.oak.server:1.1.4]
> at
> org.apache.sling.jcr.base.AbstractSlingRepositoryManager.initializeAndRegisterRepositoryService(AbstractSlingRepositoryManager.java:471)
> [org.apache.sling.jcr.base:3.0.4]
> at
> org.apache.sling.jcr.base.AbstractSlingRepositoryManager.access$300(AbstractSlingRepositoryManager.java:85)
> [org.apache.sling.jcr.base:3.0.4]
> at
> org.apache.sling.jcr.base.AbstractSlingRepositoryManager$4.run(AbstractSlingRepositoryManager.java:455)
> [org.apache.sling.jcr.base:3.0.4]
> {noformat}
> The stack trace points to a null workspace name ( see
> https://github.com/apache/jackrabbit-oak/blob/jackrabbit-oak-1.6.8/oak-jcr/src/main/java/org/apache/jackrabbit/oak/jcr/Jcr.java#L296
> ).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[GitHub] [sling-org-apache-sling-jcr-base] rombert merged pull request #2: SLING-7811 - NPE when repository is starting up due to repository manager shutdown
rombert merged pull request #2: URL: https://github.com/apache/sling-org-apache-sling-jcr-base/pull/2 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [sling-org-apache-sling-jcr-base] rombert commented on pull request #2: SLING-7811 - NPE when repository is starting up due to repository manager shutdown
rombert commented on pull request #2: URL: https://github.com/apache/sling-org-apache-sling-jcr-base/pull/2#issuecomment-668617494 > 1 Bug This is on a line I altered to add generics, so not related to my change. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [sling-org-apache-sling-jcr-base] sonarcloud[bot] commented on pull request #2: SLING-7811 - NPE when repository is starting up due to repository manager shutdown
sonarcloud[bot] commented on pull request #2: URL: https://github.com/apache/sling-org-apache-sling-jcr-base/pull/2#issuecomment-668611551 SonarCloud Quality Gate failed. [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-base=2=false=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-base=2=false=BUG) [1 Bug](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-base=2=false=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-base=2=false=VULNERABILITY) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-base=2=false=VULNERABILITY) [0 Vulnerabilities](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-base=2=false=VULNERABILITY) (and [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-base=2=false=SECURITY_HOTSPOT) [ 0 Security Hotspots](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-base=2=false=SECURITY_HOTSPOT) to review) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-base=2=false=CODE_SMELL) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-base=2=false=CODE_SMELL) [0 Code Smells](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-base=2=false=CODE_SMELL) [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-jcr-base=2=new_coverage=list) [61.5% Coverage](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-jcr-base=2=new_coverage=list) [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-jcr-base=2=new_duplicated_lines_density=list) [0.0% Duplication](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-jcr-base=2=new_duplicated_lines_density=list) The version of Java (1.8.0_252) you have used to run this analysis is deprecated and we will stop accepting it from October 2020. Please update to at least Java 11. Read more [here](https://sonarcloud.io/documentation/upcoming/) This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [sling-org-apache-sling-jcr-base] rombert opened a new pull request #2: SLING-7811 - NPE when repository is starting up due to repository manager shutdown
rombert opened a new pull request #2: URL: https://github.com/apache/sling-org-apache-sling-jcr-base/pull/2 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Closed] (SLING-9613) java.lang.StackOverflowError in XSSFilterImpl.filter for long URLs
[
https://issues.apache.org/jira/browse/SLING-9613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radu Cotescu closed SLING-9613.
---
> java.lang.StackOverflowError in XSSFilterImpl.filter for long URLs
> --
>
> Key: SLING-9613
> URL: https://issues.apache.org/jira/browse/SLING-9613
> Project: Sling
> Issue Type: Bug
> Components: XSS Protection API
>Affects Versions: XSS Protection API 2.0.8, XSS Protection API 2.1.0, XSS
> Protection API 2.2.0
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: XSS Protection API 2.2.6
>
>
> Attempting to filter the following HTML snippet results in a
> {{StackOverflowError}}:
> {code:html}
> href="https://google.com/t/r/a;>
> Click here to access replay webcast
> {code}
> {code:java}
> java.lang.StackOverflowError
> at
> java.base/java.util.regex.Pattern$CharProperty.match(Pattern.java:3939)
> at java.base/java.util.regex.Pattern$GroupHead.match(Pattern.java:4804)
> at java.base/java.util.regex.Pattern$Branch.match(Pattern.java:4749)
> at java.base/java.util.regex.Pattern$GroupHead.match(Pattern.java:4804)
> at java.base/java.util.regex.Pattern$Loop.match(Pattern.java:4941)
> at java.base/java.util.regex.Pattern$GroupTail.match(Pattern.java:4863)
> at java.base/java.util.regex.Pattern$BranchConn.match(Pattern.java:4713)
> at
> java.base/java.util.regex.Pattern$BmpCharProperty.match(Pattern.java:3964)
> at
> java.base/java.util.regex.Pattern$BmpCharProperty.match(Pattern.java:3964)
> at
> java.base/java.util.regex.Pattern$BmpCharProperty.match(Pattern.java:3964)
> at java.base/java.util.regex.Pattern$Branch.match(Pattern.java:4749)
> at java.base/java.util.regex.Pattern$GroupHead.match(Pattern.java:4804)
> at java.base/java.util.regex.Pattern$Loop.match(Pattern.java:4941)
> at java.base/java.util.regex.Pattern$GroupTail.match(Pattern.java:4863)
> at java.base/java.util.regex.Pattern$BranchConn.match(Pattern.java:4713)
> at java.base/java.util.regex.Pattern$GroupTail.match(Pattern.java:4863)
> at
> java.base/java.util.regex.Pattern$CharPropertyGreedy.match(Pattern.java:4306)
> at
> java.base/java.util.regex.Pattern$CharProperty.match(Pattern.java:3940)
> at java.base/java.util.regex.Pattern$GroupHead.match(Pattern.java:4804)
> at java.base/java.util.regex.Pattern$Branch.match(Pattern.java:4749)
> at java.base/java.util.regex.Pattern$GroupHead.match(Pattern.java:4804)
> ...
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (SLING-9616) Update to latest OWASP AntiSamy and ESAPI Java libraries
[ https://issues.apache.org/jira/browse/SLING-9616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Radu Cotescu closed SLING-9616. --- > Update to latest OWASP AntiSamy and ESAPI Java libraries > > > Key: SLING-9616 > URL: https://issues.apache.org/jira/browse/SLING-9616 > Project: Sling > Issue Type: Improvement > Components: XSS Protection API >Reporter: Radu Cotescu >Assignee: Radu Cotescu >Priority: Major > Fix For: XSS Protection API 2.2.6 > > > OWASP AntiSamy latest release includes some performance improvements, whereas > the latest ESAPI provides several bug fixes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (SLING-9622) Avoid registration of auth requirements for aliases and vanity paths
[ https://issues.apache.org/jira/browse/SLING-9622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170761#comment-17170761 ] Carsten Ziegeler commented on SLING-9622: - A different approach would be to let the auth core bundle do the mapping which is currently required to be performed by the registrar: when a new auth requirement is registered, the auth core bundle will get all mappings for the registered path and internally register the auth requirement with all of them. When the mapping changes, the auth core bundle needs to update the registration. This would avoid the performance penality on every request, but comes with some processing overhead. > Avoid registration of auth requirements for aliases and vanity paths > > > Key: SLING-9622 > URL: https://issues.apache.org/jira/browse/SLING-9622 > Project: Sling > Issue Type: Improvement > Components: Authentication >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler >Priority: Major > > Right now when auth requirements are registered, they need to be registered > for the resource path, as well as all vanity paths and potentially all > combinations of aliases for that path. First of all, this creates potentially > a lot of auth requirements for a single path, but as well requires that the > registrar of the auth requirement to be aware of vanity paths and aliases and > do the right thing and update the auth requirements whenever there are > changes. > We should avoid these additional registrations and processing. > The SlingAuthenticator is currently checking the request path against the > auth requirements. We could change this with checking the resolved path. So > the authenticator could use a service user resolver and resolve the path and > then check the auth requirements. > This avoids all the extra work for the registrar of the auth requirements, > but comes with the additional cost of a resolve call per request -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (SLING-9622) Avoid registration of auth requirements for aliases and vanity paths
[ https://issues.apache.org/jira/browse/SLING-9622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned SLING-9622: --- Assignee: Carsten Ziegeler > Avoid registration of auth requirements for aliases and vanity paths > > > Key: SLING-9622 > URL: https://issues.apache.org/jira/browse/SLING-9622 > Project: Sling > Issue Type: Improvement > Components: Authentication >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler >Priority: Major > > Right now when auth requirements are registered, they need to be registered > for the resource path, as well as all vanity paths and potentially all > combinations of aliases for that path. First of all, this creates potentially > a lot of auth requirements for a single path, but as well requires that the > registrar of the auth requirement to be aware of vanity paths and aliases and > do the right thing and update the auth requirements whenever there are > changes. > We should avoid these additional registrations and processing. > The SlingAuthenticator is currently checking the request path against the > auth requirements. We could change this with checking the resolved path. So > the authenticator could use a service user resolver and resolve the path and > then check the auth requirements. > This avoids all the extra work for the registrar of the auth requirements, > but comes with the additional cost of a resolve call per request -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (SLING-9626) "Writer has already been closed" exception in GraphQLServlet
[
https://issues.apache.org/jira/browse/SLING-9626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz resolved SLING-9626.
Fix Version/s: GraphQL Core 0.0.6
Assignee: Bertrand Delacretaz
Resolution: Fixed
Fixed in commit 91b0817
> "Writer has already been closed" exception in GraphQLServlet
>
>
> Key: SLING-9626
> URL: https://issues.apache.org/jira/browse/SLING-9626
> Project: Sling
> Issue Type: Bug
> Components: GraphQL
>Affects Versions: GraphQL Core 0.0.4
>Reporter: Evgeny Tugarev
>Assignee: Bertrand Delacretaz
>Priority: Major
> Fix For: GraphQL Core 0.0.6
>
>
> The GraphQLServlet shouldn't call {{response.getWriter().flush()}} as the
> {{JsonWriter}} used by the {{JsonSerializer}} implements {{Closeable}} and as
> such [closes the
> Writer|https://github.com/jdereg/json-io/blob/cf849f15460decf10a8a320390de11965bb5996b/src/main/java/com/cedarsoftware/util/io/JsonWriter.java#L2413].
> This causes a "Writer has already been closed" Exception when {{flush()}} is
> called.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (SLING-9622) Avoid registration of auth requirements for aliases and vanity paths
[ https://issues.apache.org/jira/browse/SLING-9622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170694#comment-17170694 ] Carsten Ziegeler commented on SLING-9622: - I have the feeling that it would be better to have a new method on ResourceMapper which handles the path mapping only (resolving vanity path and aliases) > Avoid registration of auth requirements for aliases and vanity paths > > > Key: SLING-9622 > URL: https://issues.apache.org/jira/browse/SLING-9622 > Project: Sling > Issue Type: Improvement > Components: Authentication >Reporter: Carsten Ziegeler >Priority: Major > > Right now when auth requirements are registered, they need to be registered > for the resource path, as well as all vanity paths and potentially all > combinations of aliases for that path. First of all, this creates potentially > a lot of auth requirements for a single path, but as well requires that the > registrar of the auth requirement to be aware of vanity paths and aliases and > do the right thing and update the auth requirements whenever there are > changes. > We should avoid these additional registrations and processing. > The SlingAuthenticator is currently checking the request path against the > auth requirements. We could change this with checking the resolved path. So > the authenticator could use a service user resolver and resolve the path and > then check the auth requirements. > This avoids all the extra work for the registrar of the auth requirements, > but comes with the additional cost of a resolve call per request -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: [VOTE] Release Apache Sling Scripting HTL JS Use Provider 1.2.4
On Tue, 2020-08-04 at 09:36 +, Radu Cotescu wrote: > Please vote to approve this release: +1 Robert signature.asc Description: This is a digitally signed message part
[jira] [Updated] (SLING-9626) "Writer has already been closed" exception in GraphQLServlet
[
https://issues.apache.org/jira/browse/SLING-9626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz updated SLING-9626:
---
Description:
The GraphQLServlet shouldn't call {{response.getWriter().flush()}} as the
{{JsonWriter}} used by the {{JsonSerializer}} implements {{Closeable}} and as
such [closes the
Writer|https://github.com/jdereg/json-io/blob/cf849f15460decf10a8a320390de11965bb5996b/src/main/java/com/cedarsoftware/util/io/JsonWriter.java#L2413].
This causes a "Writer has already been closed" Exception when {{flush()}} is
called.
was:
The GraphQLServlet shouldn't call {{response.getWriter().flush()}} as the
{{JsonWriter}} used by the {{JsonSerializer}} implements {{Closeable}} and as
such [closes the
Writer|https://github.com/apache/sling-org-apache-sling-graphql-core/blob/b22657e5cc435332cec7c60ad30692d2190caff8/src/main/java/org/apache/sling/graphql/core/json/JsonSerializer.java#L53].
This causes a "Writer has already been closed" Exception when {{flush()}} is
called.
> "Writer has already been closed" exception in GraphQLServlet
>
>
> Key: SLING-9626
> URL: https://issues.apache.org/jira/browse/SLING-9626
> Project: Sling
> Issue Type: Bug
> Components: GraphQL
>Affects Versions: GraphQL Core 0.0.4
>Reporter: Evgeny Tugarev
>Priority: Major
>
> The GraphQLServlet shouldn't call {{response.getWriter().flush()}} as the
> {{JsonWriter}} used by the {{JsonSerializer}} implements {{Closeable}} and as
> such [closes the
> Writer|https://github.com/jdereg/json-io/blob/cf849f15460decf10a8a320390de11965bb5996b/src/main/java/com/cedarsoftware/util/io/JsonWriter.java#L2413].
> This causes a "Writer has already been closed" Exception when {{flush()}} is
> called.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (SLING-9626) "Writer has already been closed" exception in GraphQLServlet
[
https://issues.apache.org/jira/browse/SLING-9626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz updated SLING-9626:
---
Description:
The GraphQLServlet shouldn't call {{response.getWriter().flush()}} as the
{{JsonWriter}} used by the {{JsonSerializer}} implements {{Closeable}} and as
such [closes the
Writer|https://github.com/apache/sling-org-apache-sling-graphql-core/blob/b22657e5cc435332cec7c60ad30692d2190caff8/src/main/java/org/apache/sling/graphql/core/json/JsonSerializer.java#L53].
This causes a "Writer has already been closed" Exception when {{flush()}} is
called.
was:
Current implementation closes the output stream which produces an error
org.apache.sling.engine.impl.SlingRequestProcessorImpl Writer has already been
closed.
org.apache.sling.engine.impl.SlingHttpServletResponseImpl$WriterAlreadyClosedException:
null
at
org.apache.sling.engine.impl.SlingHttpServletResponseImpl$1.checkClosed(SlingHttpServletResponseImpl.java:190)
[https://github.com/apache/sling-org-apache-sling-graphql-core/blob/b22657e5cc435332cec7c60ad30692d2190caff8/src/main/java/org/apache/sling/graphql/core/json/JsonSerializer.java#L53]
> "Writer has already been closed" exception in GraphQLServlet
>
>
> Key: SLING-9626
> URL: https://issues.apache.org/jira/browse/SLING-9626
> Project: Sling
> Issue Type: Bug
> Components: GraphQL
>Affects Versions: GraphQL Core 0.0.4
>Reporter: Evgeny Tugarev
>Priority: Major
>
> The GraphQLServlet shouldn't call {{response.getWriter().flush()}} as the
> {{JsonWriter}} used by the {{JsonSerializer}} implements {{Closeable}} and as
> such [closes the
> Writer|https://github.com/apache/sling-org-apache-sling-graphql-core/blob/b22657e5cc435332cec7c60ad30692d2190caff8/src/main/java/org/apache/sling/graphql/core/json/JsonSerializer.java#L53].
> This causes a "Writer has already been closed" Exception when {{flush()}} is
> called.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (SLING-9626) "Writer has already been closed" exception in GraphQLServlet
[ https://issues.apache.org/jira/browse/SLING-9626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz updated SLING-9626: --- Summary: "Writer has already been closed" exception in GraphQLServlet (was: JsonWriter auto closes the output stream) > "Writer has already been closed" exception in GraphQLServlet > > > Key: SLING-9626 > URL: https://issues.apache.org/jira/browse/SLING-9626 > Project: Sling > Issue Type: Bug > Components: GraphQL >Affects Versions: GraphQL Core 0.0.4 >Reporter: Evgeny Tugarev >Priority: Major > > Current implementation closes the output stream which produces an error > org.apache.sling.engine.impl.SlingRequestProcessorImpl Writer has already > been closed. > org.apache.sling.engine.impl.SlingHttpServletResponseImpl$WriterAlreadyClosedException: > null > at > org.apache.sling.engine.impl.SlingHttpServletResponseImpl$1.checkClosed(SlingHttpServletResponseImpl.java:190) > [https://github.com/apache/sling-org-apache-sling-graphql-core/blob/b22657e5cc435332cec7c60ad30692d2190caff8/src/main/java/org/apache/sling/graphql/core/json/JsonSerializer.java#L53] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (SLING-9626) JsonWriter auto closes the output stream
Evgeny Tugarev created SLING-9626: - Summary: JsonWriter auto closes the output stream Key: SLING-9626 URL: https://issues.apache.org/jira/browse/SLING-9626 Project: Sling Issue Type: Bug Components: GraphQL Affects Versions: GraphQL Core 0.0.4 Reporter: Evgeny Tugarev Current implementation closes the output stream which produces an error org.apache.sling.engine.impl.SlingRequestProcessorImpl Writer has already been closed. org.apache.sling.engine.impl.SlingHttpServletResponseImpl$WriterAlreadyClosedException: null at org.apache.sling.engine.impl.SlingHttpServletResponseImpl$1.checkClosed(SlingHttpServletResponseImpl.java:190) [https://github.com/apache/sling-org-apache-sling-graphql-core/blob/b22657e5cc435332cec7c60ad30692d2190caff8/src/main/java/org/apache/sling/graphql/core/json/JsonSerializer.java#L53] -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: [VOTE] Release Apache Sling Scripting HTL JS Use Provider 1.2.4
+1 > On 4 Aug 2020, at 11:36, Radu Cotescu wrote: > > Please vote to approve this release: > > [ ] +1 Approve the release > [ ] 0 Don't care > [ ] -1 Don't release, because ...
[VOTE] Release Apache Sling Scripting HTL JS Use Provider 1.2.4
Hi, We solved 2 issues in this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12348595 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-2312/ You can use this UNIX script to download the release and verify the signatures: https://gitbox.apache.org/repos/asf?p=sling-tooling-release.git;a=blob;f=check_staged_release.sh;hb=HEAD Usage: sh check_staged_release.sh 2312 /tmp/sling-staging Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This majority vote is open for at least 72 hours. Regards, Radu Cotescu
[jira] [Comment Edited] (SLING-9622) Avoid registration of auth requirements for aliases and vanity paths
[ https://issues.apache.org/jira/browse/SLING-9622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170680#comment-17170680 ] Carsten Ziegeler edited comment on SLING-9622 at 8/4/20, 9:31 AM: -- I've created a branch for this issue and applied a potential solution using a service resource resolver there: https://github.com/apache/sling-org-apache-sling-auth-core/tree/SLING-9622 The downside of this approach is that the service resolver is used for each and every public request. The other question is whether a service user session has auto refresh enabled - or do we need to manually refresh the session? was (Author: cziegeler): I've created a branch for this issue and applied a potential solution using a service resource resolver there: https://github.com/apache/sling-org-apache-sling-auth-core/tree/SLING-9622 The downside of this approach is that the service resolver is used for each and every public request > Avoid registration of auth requirements for aliases and vanity paths > > > Key: SLING-9622 > URL: https://issues.apache.org/jira/browse/SLING-9622 > Project: Sling > Issue Type: Improvement > Components: Authentication >Reporter: Carsten Ziegeler >Priority: Major > > Right now when auth requirements are registered, they need to be registered > for the resource path, as well as all vanity paths and potentially all > combinations of aliases for that path. First of all, this creates potentially > a lot of auth requirements for a single path, but as well requires that the > registrar of the auth requirement to be aware of vanity paths and aliases and > do the right thing and update the auth requirements whenever there are > changes. > We should avoid these additional registrations and processing. > The SlingAuthenticator is currently checking the request path against the > auth requirements. We could change this with checking the resolved path. So > the authenticator could use a service user resolver and resolve the path and > then check the auth requirements. > This avoids all the extra work for the registrar of the auth requirements, > but comes with the additional cost of a resolve call per request -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (SLING-9622) Avoid registration of auth requirements for aliases and vanity paths
[ https://issues.apache.org/jira/browse/SLING-9622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170680#comment-17170680 ] Carsten Ziegeler commented on SLING-9622: - I've created a branch for this issue and applied a potential solution using a service resource resolver there: https://github.com/apache/sling-org-apache-sling-auth-core/tree/SLING-9622 The downside of this approach is that the service resolver is used for each and every public request > Avoid registration of auth requirements for aliases and vanity paths > > > Key: SLING-9622 > URL: https://issues.apache.org/jira/browse/SLING-9622 > Project: Sling > Issue Type: Improvement > Components: Authentication >Reporter: Carsten Ziegeler >Priority: Major > > Right now when auth requirements are registered, they need to be registered > for the resource path, as well as all vanity paths and potentially all > combinations of aliases for that path. First of all, this creates potentially > a lot of auth requirements for a single path, but as well requires that the > registrar of the auth requirement to be aware of vanity paths and aliases and > do the right thing and update the auth requirements whenever there are > changes. > We should avoid these additional registrations and processing. > The SlingAuthenticator is currently checking the request path against the > auth requirements. We could change this with checking the resolved path. So > the authenticator could use a service user resolver and resolve the path and > then check the auth requirements. > This avoids all the extra work for the registrar of the auth requirements, > but comes with the additional cost of a resolve call per request -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: [RESULT] [VOTE] Release Apache Sling JCR Jackrabbit User Manager version 2.2.10
On Mon, 2020-08-03 at 10:00 -0700, Eric Norman wrote: > I need someone from the PMC to copy the release to the Sling dist > directory. Done in r40850. Thanks, Robert
