[jira] [Created] (SLING-9182) The Scripting Bundle Tracker should require bundles to provide information about the needed Script Engines

[Radu Cotescu (Jira)]

Radu Cotescu created SLING-9182:
---

 Summary: The Scripting Bundle Tracker should require bundles to 
provide information about the needed Script Engines
 Key: SLING-9182
 URL: https://issues.apache.org/jira/browse/SLING-9182
 Project: Sling
  Issue Type: Bug
  Components: Scripting
Reporter: Radu Cotescu
Assignee: Radu Cotescu
 Fix For: Scripting Bundle Tracker 0.2.0


The Scripting Bundle Tracker cannot determine which Script Engine to use for 
executing a 
{{org.apache.sling.scripting.bundle.tracker.internal.PrecompiledScript}}. Since 
the bundles wired to the tracker provide capabilities to inform about the 
available resource types, these capabilities should also provide the required 
Script Engine name for each resource type as an attribute of the 
{{sling.resourceType}} capability.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (SLING-9181) The Scripting Bundle Tracker should be extended to allow more flexibility for resource type definitions

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-9181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu resolved SLING-9181.
-
Resolution: Fixed

Fixed in [commit 
ee23513|https://github.com/apache/sling-org-apache-sling-scripting-bundle-tracker/commit/ee23513].

> The Scripting Bundle Tracker should be extended to allow more flexibility for 
> resource type definitions
> ---
>
> Key: SLING-9181
> URL: https://issues.apache.org/jira/browse/SLING-9181
> Project: Sling
>  Issue Type: Improvement
>  Components: Scripting
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: Scripting Bundle Tracker 0.2.0
>
>
> Similar to the improvements from SLING-9161, the Scripting Bundle Tracker 
> should be able to work with the following types of resource type definitions:
> # {{a/b/c}} - path-based
> # {{a/b/c/1.0.0}} - path-based, versioned
> # {{a.b.c}} - Java package name
> # {{a.b.c/1.0.0}} - Java package name, versioned
> # {{a}} - flat (sub-set of path-based)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (SLING-9181) The Scripting Bundle Tracker should be extended to allow more flexibility for resource type definitions

[Radu Cotescu (Jira)]

Radu Cotescu created SLING-9181:
---

 Summary: The Scripting Bundle Tracker should be extended to allow 
more flexibility for resource type definitions
 Key: SLING-9181
 URL: https://issues.apache.org/jira/browse/SLING-9181
 Project: Sling
  Issue Type: Improvement
  Components: Scripting
Reporter: Radu Cotescu
Assignee: Radu Cotescu
 Fix For: Scripting Bundle Tracker 0.2.0


Similar to the improvements from SLING-9161, the Scripting Bundle Tracker 
should be able to work with the following types of resource type definitions:
# {{a/b/c}} - path-based
# {{a/b/c/1.0.0}} - path-based, versioned
# {{a.b.c}} - Java package name
# {{a.b.c/1.0.0}} - Java package name, versioned
# {{a}} - flat (sub-set of path-based)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (SLING-9170) Update Sling Testing Sling Mock to enable testing with newer versions of Scripting Core

[Radu Cotescu (Jira)]

[ 
https://issues.apache.org/jira/browse/SLING-9170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17053119#comment-17053119
 ] 

Radu Cotescu commented on SLING-9170:
-

The version of the Sling Engine we're using brings an old 
{{o.a.s.jcr.resource}} version into the classpath. Since it's first, the Sling 
Mocks will use that one, but this old version does not provide the JCR Bindings.

The previous version of Sling Mocks we had didn't know how to work with newer 
versions of {{o.a.s.scripting.core}}, since the {{ScriptEngineManager}} 
implementation was moved into a different package. Anyways, we're good now! :D

> Update Sling Testing Sling Mock to enable testing with newer versions of 
> Scripting Core
> ---
>
> Key: SLING-9170
> URL: https://issues.apache.org/jira/browse/SLING-9170
> Project: Sling
>  Issue Type: Bug
>  Components: Servlets
>Affects Versions: Servlets Resolver 2.6.0
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: Servlets Resolver 2.6.4
>
>
> The Sling Testing Sling Mock dependency should be updated in order to allow 
> the tests to work correctly with newer versions of the Scripting Core module.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (SLING-9161) The Scripting Bundle Maven Plugin should allow more flexible ways for the project structure

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-9161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu resolved SLING-9161.
-
Resolution: Fixed

Fixed in [commit 
d50e074|https://github.com/apache/sling-scriptingbundle-maven-plugin/commit/d50e0742d6a20d6126e0687c90233cf1395a1287].

> The Scripting Bundle Maven Plugin should allow more flexible ways for the 
> project structure
> ---
>
> Key: SLING-9161
> URL: https://issues.apache.org/jira/browse/SLING-9161
> Project: Sling
>  Issue Type: Improvement
>  Components: Tooling
>Affects Versions: Scripting Bundle Maven Plugin 0.1.0
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: Scripting Bundle Maven Plugin 0.2.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> The Scripting Bundle Maven Plugin currently imposes the following restriction 
> for the project structure:
> {noformat}
> ///[.][.][.].
> {noformat}
> In this case the {{}} will be limited to one folder, 
> which means that resource  type namespacing should be done similar to Java 
> package names. While this is not wrong, the plugin should also allow defining 
> the resource types using Sling's already established conventions [0], e.g. 
> resource tree paths relative to a search path. In addition, the {{}} 
> folder should become optional.
> [0] - 
> https://sling.apache.org/documentation/the-sling-engine/url-to-script-resolution.html#scripts-for-get-requests



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (SLING-9170) Update Sling Testing Sling Mock to enable testing with newer versions of Scripting Core

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-9170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu resolved SLING-9170.
-
  Assignee: Radu Cotescu
Resolution: Fixed

Fixed in [commit 
bbb0148|https://github.com/apache/sling-org-apache-sling-servlets-resolver/commit/bbb0148].

> Update Sling Testing Sling Mock to enable testing with newer versions of 
> Scripting Core
> ---
>
> Key: SLING-9170
> URL: https://issues.apache.org/jira/browse/SLING-9170
> Project: Sling
>  Issue Type: Bug
>  Components: Servlets
>Affects Versions: Servlets Resolver 2.6.0
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: Servlets Resolver 2.6.4
>
>
> The Sling Testing Sling Mock dependency should be updated in order to allow 
> the tests to work correctly with newer versions of the Scripting Core module.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (SLING-9170) Update Sling Testing Sling Mock to enable testing with newer versions of Scripting Core

[Radu Cotescu (Jira)]

Radu Cotescu created SLING-9170:
---

 Summary: Update Sling Testing Sling Mock to enable testing with 
newer versions of Scripting Core
 Key: SLING-9170
 URL: https://issues.apache.org/jira/browse/SLING-9170
 Project: Sling
  Issue Type: Bug
  Components: Servlets
Affects Versions: Servlets Resolver 2.6.0
Reporter: Radu Cotescu
 Fix For: Servlets Resolver 2.6.4


The Sling Testing Sling Mock dependency should be updated in order to allow the 
tests to work correctly with newer versions of the Scripting Core module.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (SLING-9164) NPE when resolving servlets for resource types

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-9164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu updated SLING-9164:

Fix Version/s: (was: Servlets Resolver 2.6.2)
   Servlets Resolver 2.6.4

> NPE when resolving servlets for resource types
> --
>
> Key: SLING-9164
> URL: https://issues.apache.org/jira/browse/SLING-9164
> Project: Sling
>  Issue Type: Bug
>  Components: Servlets
>Affects Versions: Servlets Resolver 2.6.0
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: Servlets Resolver 2.6.4
>
>
> The Servlets Resolver 2.6.0 release has introduced changes from SLING-8110, 
> although that issue is not yet complete according to JIRA. However, one of 
> the changes introduced a NPE in the 
> {{org.apache.sling.servlets.resolver.internal.SlingServletResolver#resolveServletInternal(final
>  SlingHttpServletRequest request, final Resource resource, final String 
> scriptNameOrResourceType, final ResourceResolver resolver)}} method which 
> prevents resolving servlets for a certain {{resourceType}} or {{script}}.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (SLING-9165) Correct example usage in plugin documentation

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-9165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu resolved SLING-9165.
-
  Assignee: Radu Cotescu
Resolution: Fixed

Fixed in [commit 
39ba63a|https://github.com/apache/sling-htl-maven-plugin/commit/39ba63a60db7ed6b75052baf807278d57425c23b].

> Correct example usage in plugin documentation
> -
>
> Key: SLING-9165
> URL: https://issues.apache.org/jira/browse/SLING-9165
> Project: Sling
>  Issue Type: Bug
>  Components: Tooling
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: HTL Maven Plugin 1.4.0-1.4.0
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> The "Usage" page of the {{htl-maven-plugin}} provides some pom configuration 
> examples where some tags are not properly closed.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (SLING-9165) Correct example usage in plugin documentation

[Radu Cotescu (Jira)]

Radu Cotescu created SLING-9165:
---

 Summary: Correct example usage in plugin documentation
 Key: SLING-9165
 URL: https://issues.apache.org/jira/browse/SLING-9165
 Project: Sling
  Issue Type: Bug
  Components: Tooling
Reporter: Radu Cotescu
 Fix For: HTL Maven Plugin 1.4.0-1.4.0


The "Usage" page of the {{htl-maven-plugin}} provides some pom configuration 
examples where some tags are not properly closed.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (SLING-9160) OSGi Installer Core seems to have a stale service registration

[Radu Cotescu (Jira)]

[ 
https://issues.apache.org/jira/browse/SLING-9160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17047810#comment-17047810
 ] 

Radu Cotescu commented on SLING-9160:
-

[~kwin], sorry, I didn't have time to test with 3.10.1-SNAPSHOT / 3.10.2, but 
it looks like this issue is duplicating SLING-9139 indeed. Thanks!

> OSGi Installer Core seems to have a stale service registration
> --
>
> Key: SLING-9160
> URL: https://issues.apache.org/jira/browse/SLING-9160
> Project: Sling
>  Issue Type: Bug
>  Components: Installer
>Affects Versions: Installer Core 3.10.0
>Reporter: Radu Cotescu
>Assignee: Konrad Windszus
>Priority: Major
>
> The following stack trace appears in the logs when starting an instance:
> {noformat}
> 27.02.2020 12:09:32.837 *ERROR* [pool-7-thread-1] ERROR: Bundle '2' 
> EventDispatcher: Error during dispatch. (java.lang.IllegalStateException: The 
> service registration is no longer valid.)
> java.lang.IllegalStateException: The service registration is no longer valid.
>   at 
> org.apache.felix.framework.ServiceRegistrationImpl.setProperties(ServiceRegistrationImpl.java:123)
>   at 
> org.apache.sling.installer.core.impl.UpdateHandlerTracker.updateUrlStreamHandler(UpdateHandlerTracker.java:101)
>   at 
> org.apache.sling.installer.core.impl.UpdateHandlerTracker.addOrRemoveService(UpdateHandlerTracker.java:82)
>   at 
> org.apache.sling.installer.core.impl.UpdateHandlerTracker.addingService(UpdateHandlerTracker.java:56)
>   at 
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:943)
>   at 
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:871)
>   at 
> org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:256)
>   at org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:229)
>   at 
> org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:903)
>   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 
> org.apache.felix.scr.impl.manager.DependencyManager$SingleStaticCustomizer.addedService(DependencyManager.java:1045)
>   at 
> org.apache.felix.scr.impl.manager.DependencyManager$SingleStaticCustomizer.addedService(DependencyManager.java:999)
>   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.framework.BundleContextImpl.registerService(BundleContextImpl.java:302)
>   at 
> 

[jira] [Resolved] (SLING-9164) NPE when resolving servlets for resource types

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-9164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu resolved SLING-9164.
-
Resolution: Fixed

Fixed in [commit 
1386d2e|https://github.com/apache/sling-org-apache-sling-servlets-resolver/commit/1386d2e].

> NPE when resolving servlets for resource types
> --
>
> Key: SLING-9164
> URL: https://issues.apache.org/jira/browse/SLING-9164
> Project: Sling
>  Issue Type: Bug
>  Components: Servlets
>Affects Versions: Servlets Resolver 2.6.0
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: Servlets Resolver 2.6.2
>
>
> The Servlets Resolver 2.6.0 release has introduced changes from SLING-8110, 
> although that issue is not yet complete according to JIRA. However, one of 
> the changes introduced a NPE in the 
> {{org.apache.sling.servlets.resolver.internal.SlingServletResolver#resolveServletInternal(final
>  SlingHttpServletRequest request, final Resource resource, final String 
> scriptNameOrResourceType, final ResourceResolver resolver)}} method which 
> prevents resolving servlets for a certain {{resourceType}} or {{script}}.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (SLING-9164) NPE when resolving servlets for resource types

[Radu Cotescu (Jira)]

Radu Cotescu created SLING-9164:
---

 Summary: NPE when resolving servlets for resource types
 Key: SLING-9164
 URL: https://issues.apache.org/jira/browse/SLING-9164
 Project: Sling
  Issue Type: Bug
  Components: Servlets
Affects Versions: Servlets Resolver 2.6.0
Reporter: Radu Cotescu
Assignee: Radu Cotescu
 Fix For: Servlets Resolver 2.6.2


The Servlets Resolver 2.6.0 release has introduced changes from SLING-8110, 
although that issue is not yet complete according to JIRA. However, one of the 
changes introduced a NPE in the 
{{org.apache.sling.servlets.resolver.internal.SlingServletResolver#resolveServletInternal(final
 SlingHttpServletRequest request, final Resource resource, final String 
scriptNameOrResourceType, final ResourceResolver resolver)}} method which 
prevents resolving servlets for a certain {{resourceType}} or {{script}}.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (SLING-9161) The Scripting Bundle Maven Plugin should allow more flexible ways for the project structure

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-9161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu updated SLING-9161:

Description: 
The Scripting Bundle Maven Plugin currently imposes the following restriction 
for the project structure:
{noformat}
///[.][.][.].
{noformat}

In this case the {{}} will be limited to one folder, which 
means that resource  type namespacing should be done similar to Java package 
names. While this is not wrong, the plugin should also allow defining the 
resource types using Sling's already established conventions [0], e.g. resource 
tree paths relative to a search path. In addition, the {{}} folder 
should become optional.

[0] - 
https://sling.apache.org/documentation/the-sling-engine/url-to-script-resolution.html#scripts-for-get-requests

  was:
The Scripting Bundle Maven Plugin currently imposes the following restriction 
for the project structure:
{noformat}
///[.][.][.].
{noformat}

In this case the {{}} will be limited to one folder, which 
means that resource  type namespacing should be done similar to Java package 
names. While this is not wrong, the plugin should also allow defining the 
resource types using Sling's already established conventions, e.g. resource 
tree paths relative to a search path. In addition, the {{}} folder 
should become optional.


> The Scripting Bundle Maven Plugin should allow more flexible ways for the 
> project structure
> ---
>
> Key: SLING-9161
> URL: https://issues.apache.org/jira/browse/SLING-9161
> Project: Sling
>  Issue Type: Improvement
>  Components: Tooling
>Affects Versions: Scripting Bundle Maven Plugin 0.1.0
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: Scripting Bundle Maven Plugin 0.2.0
>
>
> The Scripting Bundle Maven Plugin currently imposes the following restriction 
> for the project structure:
> {noformat}
> ///[.][.][.].
> {noformat}
> In this case the {{}} will be limited to one folder, 
> which means that resource  type namespacing should be done similar to Java 
> package names. While this is not wrong, the plugin should also allow defining 
> the resource types using Sling's already established conventions [0], e.g. 
> resource tree paths relative to a search path. In addition, the {{}} 
> folder should become optional.
> [0] - 
> https://sling.apache.org/documentation/the-sling-engine/url-to-script-resolution.html#scripts-for-get-requests



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (SLING-9161) The Scripting Bundle Maven Plugin should allow more flexible ways for the project structure

[Radu Cotescu (Jira)]

Radu Cotescu created SLING-9161:
---

 Summary: The Scripting Bundle Maven Plugin should allow more 
flexible ways for the project structure
 Key: SLING-9161
 URL: https://issues.apache.org/jira/browse/SLING-9161
 Project: Sling
  Issue Type: Improvement
  Components: Tooling
Affects Versions: Scripting Bundle Maven Plugin 0.1.0
Reporter: Radu Cotescu
Assignee: Radu Cotescu
 Fix For: Scripting Bundle Maven Plugin 0.2.0


The Scripting Bundle Maven Plugin currently imposes the following restriction 
for the project structure:
{noformat}
///[.][.][.].
{noformat}

In this case the {{}} will be limited to one folder, which 
means that resource  type namespacing should be done similar to Java package 
names. While this is not wrong, the plugin should also allow defining the 
resource types using Sling's already established conventions, e.g. resource 
tree paths relative to a search path. In addition, the {{}} folder 
should become optional.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (SLING-9160) OSGi Installer Core seems to have a stale service registration

[Radu Cotescu (Jira)]

[ 
https://issues.apache.org/jira/browse/SLING-9160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17046516#comment-17046516
 ] 

Radu Cotescu commented on SLING-9160:
-

I've just updated the Sling Starter in [commit 
97dc81a|https://github.com/apache/sling-org-apache-sling-starter/commit/97dc81a],
 so you can test with the latest 12-SNAPSHOT.

> OSGi Installer Core seems to have a stale service registration
> --
>
> Key: SLING-9160
> URL: https://issues.apache.org/jira/browse/SLING-9160
> Project: Sling
>  Issue Type: Bug
>  Components: Installer
>Affects Versions: Installer Core 3.10.0
>Reporter: Radu Cotescu
>Priority: Major
>
> The following stack trace appears in the logs when starting an instance:
> {noformat}
> 27.02.2020 12:09:32.837 *ERROR* [pool-7-thread-1] ERROR: Bundle '2' 
> EventDispatcher: Error during dispatch. (java.lang.IllegalStateException: The 
> service registration is no longer valid.)
> java.lang.IllegalStateException: The service registration is no longer valid.
>   at 
> org.apache.felix.framework.ServiceRegistrationImpl.setProperties(ServiceRegistrationImpl.java:123)
>   at 
> org.apache.sling.installer.core.impl.UpdateHandlerTracker.updateUrlStreamHandler(UpdateHandlerTracker.java:101)
>   at 
> org.apache.sling.installer.core.impl.UpdateHandlerTracker.addOrRemoveService(UpdateHandlerTracker.java:82)
>   at 
> org.apache.sling.installer.core.impl.UpdateHandlerTracker.addingService(UpdateHandlerTracker.java:56)
>   at 
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:943)
>   at 
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:871)
>   at 
> org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:256)
>   at org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:229)
>   at 
> org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:903)
>   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 
> org.apache.felix.scr.impl.manager.DependencyManager$SingleStaticCustomizer.addedService(DependencyManager.java:1045)
>   at 
> org.apache.felix.scr.impl.manager.DependencyManager$SingleStaticCustomizer.addedService(DependencyManager.java:999)
>   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.framework.BundleContextImpl.registerService(BundleContextImpl.java:302)
>   at 
> 

[jira] [Assigned] (SLING-9160) OSGi Installer Core seems to have a stale service registration

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-9160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu reassigned SLING-9160:
---

Assignee: (was: Radu Cotescu)

> OSGi Installer Core seems to have a stale service registration
> --
>
> Key: SLING-9160
> URL: https://issues.apache.org/jira/browse/SLING-9160
> Project: Sling
>  Issue Type: Bug
>  Components: Installer
>Affects Versions: Installer Core 3.10.0
>Reporter: Radu Cotescu
>Priority: Major
>
> The following stack trace appears in the logs when starting an instance:
> {noformat}
> 27.02.2020 12:09:32.837 *ERROR* [pool-7-thread-1] ERROR: Bundle '2' 
> EventDispatcher: Error during dispatch. (java.lang.IllegalStateException: The 
> service registration is no longer valid.)
> java.lang.IllegalStateException: The service registration is no longer valid.
>   at 
> org.apache.felix.framework.ServiceRegistrationImpl.setProperties(ServiceRegistrationImpl.java:123)
>   at 
> org.apache.sling.installer.core.impl.UpdateHandlerTracker.updateUrlStreamHandler(UpdateHandlerTracker.java:101)
>   at 
> org.apache.sling.installer.core.impl.UpdateHandlerTracker.addOrRemoveService(UpdateHandlerTracker.java:82)
>   at 
> org.apache.sling.installer.core.impl.UpdateHandlerTracker.addingService(UpdateHandlerTracker.java:56)
>   at 
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:943)
>   at 
> org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:871)
>   at 
> org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:256)
>   at org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:229)
>   at 
> org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:903)
>   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 
> org.apache.felix.scr.impl.manager.DependencyManager$SingleStaticCustomizer.addedService(DependencyManager.java:1045)
>   at 
> org.apache.felix.scr.impl.manager.DependencyManager$SingleStaticCustomizer.addedService(DependencyManager.java:999)
>   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.framework.BundleContextImpl.registerService(BundleContextImpl.java:302)
>   at 
> org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.executeServiceRegistrations(ServiceUserMapperImpl.java:383)
>   at 
> 

[jira] [Created] (SLING-9160) OSGi Installer Core seems to have a stale service registration

[Radu Cotescu (Jira)]

Radu Cotescu created SLING-9160:
---

 Summary: OSGi Installer Core seems to have a stale service 
registration
 Key: SLING-9160
 URL: https://issues.apache.org/jira/browse/SLING-9160
 Project: Sling
  Issue Type: Bug
  Components: Installer
Affects Versions: Installer Core 3.10.0
Reporter: Radu Cotescu
Assignee: Radu Cotescu


The following stack trace appears in the logs when starting an instance:

{noformat}
27.02.2020 12:09:32.837 *ERROR* [pool-7-thread-1] ERROR: Bundle '2' 
EventDispatcher: Error during dispatch. (java.lang.IllegalStateException: The 
service registration is no longer valid.)
java.lang.IllegalStateException: The service registration is no longer valid.
at 
org.apache.felix.framework.ServiceRegistrationImpl.setProperties(ServiceRegistrationImpl.java:123)
at 
org.apache.sling.installer.core.impl.UpdateHandlerTracker.updateUrlStreamHandler(UpdateHandlerTracker.java:101)
at 
org.apache.sling.installer.core.impl.UpdateHandlerTracker.addOrRemoveService(UpdateHandlerTracker.java:82)
at 
org.apache.sling.installer.core.impl.UpdateHandlerTracker.addingService(UpdateHandlerTracker.java:56)
at 
org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:943)
at 
org.osgi.util.tracker.ServiceTracker$Tracked.customizerAdding(ServiceTracker.java:871)
at 
org.osgi.util.tracker.AbstractTracked.trackAdding(AbstractTracked.java:256)
at org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:229)
at 
org.osgi.util.tracker.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:903)
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 
org.apache.felix.scr.impl.manager.DependencyManager$SingleStaticCustomizer.addedService(DependencyManager.java:1045)
at 
org.apache.felix.scr.impl.manager.DependencyManager$SingleStaticCustomizer.addedService(DependencyManager.java:999)
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.framework.BundleContextImpl.registerService(BundleContextImpl.java:302)
at 
org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.executeServiceRegistrations(ServiceUserMapperImpl.java:383)
at 
org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.access$000(ServiceUserMapperImpl.java:63)
at 
org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl$1.run(ServiceUserMapperImpl.java:337)
at 
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at 

[jira] [Resolved] (SLING-9159) Switch to the LazyBindings implementation from org.apache.sling.api

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-9159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu resolved SLING-9159.
-
Resolution: Fixed

Fixed in [commit 
3f9bcad|https://github.com/apache/sling-org-apache-sling-scripting-bundle-tracker/commit/3f9bcad]
 and [commit 
6351612|https://github.com/apache/sling-org-apache-sling-scripting-bundle-tracker-it/commit/6351612].

> Switch to the LazyBindings implementation from org.apache.sling.api
> ---
>
> Key: SLING-9159
> URL: https://issues.apache.org/jira/browse/SLING-9159
> Project: Sling
>  Issue Type: Improvement
>  Components: Scripting
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: Scripting Bundle Tracker 0.2.0
>
>
> An improved {{LazyBindings}} implementation has been made available in 
> {{org.apache.sling.api-2.21.0}}, therefore the local Scripting Bundle Tracker 
> implementation should be removed.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (SLING-9159) Switch to the LazyBindings implementation from org.apache.sling.api

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-9159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu reassigned SLING-9159:
---

Assignee: Radu Cotescu

> Switch to the LazyBindings implementation from org.apache.sling.api
> ---
>
> Key: SLING-9159
> URL: https://issues.apache.org/jira/browse/SLING-9159
> Project: Sling
>  Issue Type: Improvement
>  Components: Scripting
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: Scripting Bundle Tracker 0.2.0
>
>
> An improved {{LazyBindings}} implementation has been made available in 
> {{org.apache.sling.api-2.21.0}}, therefore the local Scripting Bundle Tracker 
> implementation should be removed.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (SLING-9159) Switch to the LazyBindings implementation from org.apache.sling.api

[Radu Cotescu (Jira)]

Radu Cotescu created SLING-9159:
---

 Summary: Switch to the LazyBindings implementation from 
org.apache.sling.api
 Key: SLING-9159
 URL: https://issues.apache.org/jira/browse/SLING-9159
 Project: Sling
  Issue Type: Improvement
  Components: Scripting
Reporter: Radu Cotescu
 Fix For: Scripting Bundle Tracker 0.2.0


An improved {{LazyBindings}} implementation has been made available in 
{{org.apache.sling.api-2.21.0}}, therefore the local Scripting Bundle Tracker 
implementation should be removed.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (SLING-9158) Switch from JavaEscapeUtils to JavaEscapeHelper

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-9158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu resolved SLING-9158.
-
Resolution: Fixed

Fixed in [commit 
3a873fb|https://github.com/apache/sling-org-apache-sling-scripting-bundle-tracker/commit/3a873fb]
 and [commit 
de127fc|https://github.com/apache/sling-org-apache-sling-scripting-bundle-tracker-it/commit/de127fc].

> Switch from JavaEscapeUtils to JavaEscapeHelper
> ---
>
> Key: SLING-9158
> URL: https://issues.apache.org/jira/browse/SLING-9158
> Project: Sling
>  Issue Type: Sub-task
>  Components: Scripting
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: Scripting Bundle Tracker 0.2.0
>
>
> The 
> {{org.apache.sling.scripting.bundle.tracker.internal.BundledScriptFinder}} 
> should switch to the 
> {{org.apache.sling.commons.compiler.source.JavaEscapeHelper}} class provided 
> by the Commons Compiler module for mapping resource types to Java classes.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (SLING-9158) Switch from JavaEscapeUtils to JavaEscapeHelper

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-9158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu updated SLING-9158:

Description: The 
{{org.apache.sling.scripting.bundle.tracker.internal.BundledScriptFinder}} 
should switch to the 
{{org.apache.sling.commons.compiler.source.JavaEscapeHelper}} class provided by 
the Commons Compiler module for mapping resource types to Java classes.  (was: 
Since {{org.apache.sling.scripting.sightly.java.compiler.JavaEscapeUtils}} was 
deprecated, it's better to switch to the 
{{org.apache.sling.commons.compiler.source.JavaEscapeHelper}} class provided by 
the Commons Compiler module.)

> Switch from JavaEscapeUtils to JavaEscapeHelper
> ---
>
> Key: SLING-9158
> URL: https://issues.apache.org/jira/browse/SLING-9158
> Project: Sling
>  Issue Type: Sub-task
>  Components: Scripting
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: Scripting Bundle Tracker 0.2.0
>
>
> The 
> {{org.apache.sling.scripting.bundle.tracker.internal.BundledScriptFinder}} 
> should switch to the 
> {{org.apache.sling.commons.compiler.source.JavaEscapeHelper}} class provided 
> by the Commons Compiler module for mapping resource types to Java classes.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (SLING-9158) Switch from JavaEscapeUtils to JavaEscapeHelper

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-9158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu updated SLING-9158:

Fix Version/s: (was: Scripting HTL Testing 1.0.22-1.4.0)
   (was: Scripting HTL Engine 1.4.0-1.4.0)
   Scripting Bundle Tracker 0.2.0

> Switch from JavaEscapeUtils to JavaEscapeHelper
> ---
>
> Key: SLING-9158
> URL: https://issues.apache.org/jira/browse/SLING-9158
> Project: Sling
>  Issue Type: Sub-task
>  Components: Scripting
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: Scripting Bundle Tracker 0.2.0
>
>
> Since {{org.apache.sling.scripting.sightly.java.compiler.JavaEscapeUtils}} 
> was deprecated, it's better to switch to the 
> {{org.apache.sling.commons.compiler.source.JavaEscapeHelper}} class provided 
> by the Commons Compiler module.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (SLING-9158) Switch from JavaEscapeUtils to JavaEscapeHelper

[Radu Cotescu (Jira)]

Radu Cotescu created SLING-9158:
---

 Summary: Switch from JavaEscapeUtils to JavaEscapeHelper
 Key: SLING-9158
 URL: https://issues.apache.org/jira/browse/SLING-9158
 Project: Sling
  Issue Type: Sub-task
  Components: Scripting
Reporter: Radu Cotescu
Assignee: Radu Cotescu
 Fix For: Scripting HTL Engine 1.4.0-1.4.0, Scripting HTL Testing 
1.0.22-1.4.0


Since {{org.apache.sling.scripting.sightly.java.compiler.JavaEscapeUtils}} was 
deprecated, it's better to switch to the 
{{org.apache.sling.commons.compiler.source.JavaEscapeHelper}} class provided by 
the Commons Compiler module.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (SLING-9154) Update to the latest JSP compiler

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-9154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu resolved SLING-9154.
-
Resolution: Fixed

Fixed in [commit 
5f9c7e3|https://github.com/apache/sling-jspc-maven-plugin/commit/5f9c7e3].

> Update to the latest JSP compiler
> -
>
> Key: SLING-9154
> URL: https://issues.apache.org/jira/browse/SLING-9154
> Project: Sling
>  Issue Type: Improvement
>  Components: Tooling
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: JSPC Maven Plugin 2.2.0
>
>
> With SLING-9150 the JSP compiler uses different conventions for generating 
> and locating Java classes corresponding to JSP files or tag libraries. As 
> such, the JSPC Maven Plugin should be updated to the latest version of the 
> compiler.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (SLING-9154) Update to the latest JSP compiler

[Radu Cotescu (Jira)]

Radu Cotescu created SLING-9154:
---

 Summary: Update to the latest JSP compiler
 Key: SLING-9154
 URL: https://issues.apache.org/jira/browse/SLING-9154
 Project: Sling
  Issue Type: Improvement
  Components: Tooling
Reporter: Radu Cotescu
Assignee: Radu Cotescu
 Fix For: JSPC Maven Plugin 2.2.0


With SLING-9150 the JSP compiler uses different conventions for generating and 
locating Java classes corresponding to JSP files or tag libraries. As such, the 
JSPC Maven Plugin should be updated to the latest version of the compiler.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (SLING-9147) Switch from JavaEscapeUtils to JavaEscapeHelper

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-9147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu updated SLING-9147:

Fix Version/s: Scripting HTL Testing 1.0.22-1.4.0

> Switch from JavaEscapeUtils to JavaEscapeHelper
> ---
>
> Key: SLING-9147
> URL: https://issues.apache.org/jira/browse/SLING-9147
> Project: Sling
>  Issue Type: Sub-task
>  Components: Scripting
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: Scripting HTL Engine 1.3.4-1.4.0, Scripting HTL Testing 
> 1.0.22-1.4.0
>
>
> Since {{org.apache.sling.scripting.sightly.java.compiler.JavaEscapeUtils}} 
> was deprecated, it's better to switch to the 
> {{org.apache.sling.commons.compiler.source.JavaEscapeHelper}} class provided 
> by the Commons Compiler module.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (SLING-9142) Deprecate JavaEscapeUtils and switch to JavaEscapeHelper

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-9142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu updated SLING-9142:

Fix Version/s: Scripting HTL Testing 1.0.22-1.4.0

> Deprecate JavaEscapeUtils and switch to JavaEscapeHelper
> 
>
> Key: SLING-9142
> URL: https://issues.apache.org/jira/browse/SLING-9142
> Project: Sling
>  Issue Type: Sub-task
>  Components: Scripting
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: Scripting HTL Java Compiler 1.1.6-1.4.0, Scripting HTL 
> Testing 1.0.22-1.4.0
>
>
> With {{org.apache.sling.commons.compiler.source.JavaEscapeHelper}} extracted 
> to the {{org.apache.sling.commons.compiler}}, the  
> {{org.apache.sling.scripting.sightly.java.compiler.JavaEscapeUtils}} should 
> be deprecated and its usage removed from the HTL Java Compiler.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (SLING-8867) Enhance the pageContext with the values provided by the SlingBindings

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-8867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu updated SLING-8867:

Fix Version/s: (was: Scripting JSP 2.4.0)
   Scripting JSP 2.4.2

> Enhance the pageContext with the values provided by the SlingBindings
> -
>
> Key: SLING-8867
> URL: https://issues.apache.org/jira/browse/SLING-8867
> Project: Sling
>  Issue Type: Improvement
>  Components: Scripting
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: Scripting JSP 2.4.2
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> SLING-8737 brought support for using lazily evaluated bindings. The JSP 
> script engine, however, although sets the {{SlingBindings}} as a request 
> attribute, does not do anything else to facilitate the access to the 
> bindings' values. Instead, this is delegated partially to the 
> {{}} tag. However, this tag has the potential of 
> expanding all values which are provided lazily, irrespective of what values 
> the JSP script being evaluated needs.
> While modifying the {{}} tag is out of the question, 
> for backwards-compatibility reasons, the JSP engine could make the values 
> provided by the {{SlingBindings}} available in the {{pageContext}}, if the 
> context hasn't already defined identical attributes.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Closed] (SLING-8867) Enhance the pageContext with the values provided by the SlingBindings

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-8867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu closed SLING-8867.
---

> Enhance the pageContext with the values provided by the SlingBindings
> -
>
> Key: SLING-8867
> URL: https://issues.apache.org/jira/browse/SLING-8867
> Project: Sling
>  Issue Type: Improvement
>  Components: Scripting
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: Scripting JSP 2.4.2
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> SLING-8737 brought support for using lazily evaluated bindings. The JSP 
> script engine, however, although sets the {{SlingBindings}} as a request 
> attribute, does not do anything else to facilitate the access to the 
> bindings' values. Instead, this is delegated partially to the 
> {{}} tag. However, this tag has the potential of 
> expanding all values which are provided lazily, irrespective of what values 
> the JSP script being evaluated needs.
> While modifying the {{}} tag is out of the question, 
> for backwards-compatibility reasons, the JSP engine could make the values 
> provided by the {{SlingBindings}} available in the {{pageContext}}, if the 
> context hasn't already defined identical attributes.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (SLING-9150) Replace similar methods from JspUtil with calls to JavaEscapeHelper

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-9150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu resolved SLING-9150.
-
Resolution: Fixed

Fixed in [commit 
b5573a9|https://github.com/apache/sling-org-apache-sling-scripting-jsp/commit/b5573a9].

> Replace similar methods from JspUtil with calls to JavaEscapeHelper
> ---
>
> Key: SLING-9150
> URL: https://issues.apache.org/jira/browse/SLING-9150
> Project: Sling
>  Issue Type: Sub-task
>  Components: Scripting
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: Scripting JSP 2.4.4
>
>
> Some of the {{org.apache.sling.scripting.jsp.jasper.compiler.JspUtil}} 
> methods should be removed and replaced with their equivalents from 
> {{org.apache.sling.commons.compiler.source.JavaEscapeHelper}}.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (SLING-9142) Deprecate JavaEscapeUtils and switch to JavaEscapeHelper

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-9142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu updated SLING-9142:

Description: With 
{{org.apache.sling.commons.compiler.source.JavaEscapeHelper}} extracted to the 
{{org.apache.sling.commons.compiler}}, the  
{{org.apache.sling.scripting.sightly.java.compiler.JavaEscapeUtils}} should be 
deprecated and its usage removed from the HTL Java Compiler.  (was: With 
{{org.apache.sling.commons.compiler.source.JavaEscapeHelper}} extracted to the 
{{org.apache.sling.commons.compiler}}, the  
{{org.apache.sling.scripting.sightly.java.compiler.JavaEscapeUtils }} should be 
deprecated and its usage removed from the HTL Java Compiler.)

> Deprecate JavaEscapeUtils and switch to JavaEscapeHelper
> 
>
> Key: SLING-9142
> URL: https://issues.apache.org/jira/browse/SLING-9142
> Project: Sling
>  Issue Type: Sub-task
>  Components: Scripting
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: Scripting HTL Java Compiler 1.1.6-1.4.0
>
>
> With {{org.apache.sling.commons.compiler.source.JavaEscapeHelper}} extracted 
> to the {{org.apache.sling.commons.compiler}}, the  
> {{org.apache.sling.scripting.sightly.java.compiler.JavaEscapeUtils}} should 
> be deprecated and its usage removed from the HTL Java Compiler.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (SLING-9150) Replace similar methods from JspUtil with calls to JavaEscapeHelper

[Radu Cotescu (Jira)]

Radu Cotescu created SLING-9150:
---

 Summary: Replace similar methods from JspUtil with calls to 
JavaEscapeHelper
 Key: SLING-9150
 URL: https://issues.apache.org/jira/browse/SLING-9150
 Project: Sling
  Issue Type: Sub-task
  Components: Scripting
Reporter: Radu Cotescu
Assignee: Radu Cotescu
 Fix For: Scripting JSP 2.4.4


Some of the {{org.apache.sling.scripting.jsp.jasper.compiler.JspUtil}} methods 
should be removed and replaced with their equivalents from 
{{org.apache.sling.commons.compiler.source.JavaEscapeHelper}}.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (SLING-9149) Switch from JavaEscapeUtils to JavaEscapeHelper

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-9149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu resolved SLING-9149.
-
Resolution: Fixed

Fixed in [commit 
ccf1ec0|https://github.com/apache/sling-htl-maven-plugin/commit/ccf1ec0].

> Switch from JavaEscapeUtils to JavaEscapeHelper
> ---
>
> Key: SLING-9149
> URL: https://issues.apache.org/jira/browse/SLING-9149
> Project: Sling
>  Issue Type: Sub-task
>  Components: Tooling
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: HTL Maven Plugin 1.3.6-1.4.0
>
>
> Since {{org.apache.sling.scripting.sightly.java.compiler.JavaEscapeUtils}} 
> was deprecated, it's better to switch to the 
> {{org.apache.sling.commons.compiler.source.JavaEscapeHelper}} class provided 
> by the Commons Compiler module.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (SLING-9149) Switch from JavaEscapeUtils to JavaEscapeHelper

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-9149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu updated SLING-9149:

Component/s: (was: Scripting)
 Tooling

> Switch from JavaEscapeUtils to JavaEscapeHelper
> ---
>
> Key: SLING-9149
> URL: https://issues.apache.org/jira/browse/SLING-9149
> Project: Sling
>  Issue Type: Sub-task
>  Components: Tooling
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: HTL Maven Plugin 1.3.6-1.4.0
>
>
> Since {{org.apache.sling.scripting.sightly.java.compiler.JavaEscapeUtils}} 
> was deprecated, it's better to switch to the 
> {{org.apache.sling.commons.compiler.source.JavaEscapeHelper}} class provided 
> by the Commons Compiler module.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (SLING-9149) Switch from JavaEscapeUtils to JavaEscapeHelper

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-9149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu updated SLING-9149:

Fix Version/s: (was: Scripting HTL Engine 1.3.4-1.4.0)
   HTL Maven Plugin 1.3.6-1.4.0

> Switch from JavaEscapeUtils to JavaEscapeHelper
> ---
>
> Key: SLING-9149
> URL: https://issues.apache.org/jira/browse/SLING-9149
> Project: Sling
>  Issue Type: Sub-task
>  Components: Scripting
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: HTL Maven Plugin 1.3.6-1.4.0
>
>
> Since {{org.apache.sling.scripting.sightly.java.compiler.JavaEscapeUtils}} 
> was deprecated, it's better to switch to the 
> {{org.apache.sling.commons.compiler.source.JavaEscapeHelper}} class provided 
> by the Commons Compiler module.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (SLING-9149) Switch from JavaEscapeUtils to JavaEscapeHelper

[Radu Cotescu (Jira)]

Radu Cotescu created SLING-9149:
---

 Summary: Switch from JavaEscapeUtils to JavaEscapeHelper
 Key: SLING-9149
 URL: https://issues.apache.org/jira/browse/SLING-9149
 Project: Sling
  Issue Type: Sub-task
  Components: Scripting
Reporter: Radu Cotescu
Assignee: Radu Cotescu
 Fix For: Scripting HTL Engine 1.3.4-1.4.0


Since {{org.apache.sling.scripting.sightly.java.compiler.JavaEscapeUtils}} was 
deprecated, it's better to switch to the 
{{org.apache.sling.commons.compiler.source.JavaEscapeHelper}} class provided by 
the Commons Compiler module.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (SLING-9147) Switch from JavaEscapeUtils to JavaEscapeHelper

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-9147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu updated SLING-9147:

Description: Since 
{{org.apache.sling.scripting.sightly.java.compiler.JavaEscapeUtils}} was 
deprecated, it's better to switch to the 
{{org.apache.sling.commons.compiler.source.JavaEscapeHelper}} class provided by 
the Commons Compiler module.  (was: Since 
{{org.apache.sling.commons.compiler.source.JavaEscapeHelper}} and 
{{org.apache.sling.scripting.sightly.java.compiler.JavaEscapeUtils}} was 
deprecated, it's better to switch to the class provided by the Commons Compiler 
module.)

> Switch from JavaEscapeUtils to JavaEscapeHelper
> ---
>
> Key: SLING-9147
> URL: https://issues.apache.org/jira/browse/SLING-9147
> Project: Sling
>  Issue Type: Sub-task
>  Components: Scripting
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: Scripting HTL Engine 1.3.4-1.4.0
>
>
> Since {{org.apache.sling.scripting.sightly.java.compiler.JavaEscapeUtils}} 
> was deprecated, it's better to switch to the 
> {{org.apache.sling.commons.compiler.source.JavaEscapeHelper}} class provided 
> by the Commons Compiler module.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (SLING-9147) Switch from JavaEscapeUtils to JavaEscapeHelper

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-9147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu resolved SLING-9147.
-
Resolution: Fixed

Fixed in [commit 
bde6c8d|https://github.com/apache/sling-org-apache-sling-scripting-sightly/commit/bde6c8d].

> Switch from JavaEscapeUtils to JavaEscapeHelper
> ---
>
> Key: SLING-9147
> URL: https://issues.apache.org/jira/browse/SLING-9147
> Project: Sling
>  Issue Type: Sub-task
>  Components: Scripting
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: Scripting HTL Engine 1.3.4-1.4.0
>
>
> Since {{org.apache.sling.commons.compiler.source.JavaEscapeHelper}} and 
> {{org.apache.sling.scripting.sightly.java.compiler.JavaEscapeUtils}} was 
> deprecated, it's better to switch to the class provided by the Commons 
> Compiler module.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (SLING-9147) Switch from JavaEscapeUtils to JavaEscapeHelper

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-9147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu reassigned SLING-9147:
---

Assignee: Radu Cotescu

> Switch from JavaEscapeUtils to JavaEscapeHelper
> ---
>
> Key: SLING-9147
> URL: https://issues.apache.org/jira/browse/SLING-9147
> Project: Sling
>  Issue Type: Sub-task
>  Components: Scripting
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: Scripting HTL Engine 1.3.4-1.4.0
>
>
> Since {{org.apache.sling.commons.compiler.source.JavaEscapeHelper}} and 
> {{org.apache.sling.scripting.sightly.java.compiler.JavaEscapeUtils}} was 
> deprecated, it's better to switch to the class provided by the Commons 
> Compiler module.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (SLING-9147) Switch from JavaEscapeUtils to JavaEscapeHelper

[Radu Cotescu (Jira)]

Radu Cotescu created SLING-9147:
---

 Summary: Switch from JavaEscapeUtils to JavaEscapeHelper
 Key: SLING-9147
 URL: https://issues.apache.org/jira/browse/SLING-9147
 Project: Sling
  Issue Type: Sub-task
  Components: Scripting
Reporter: Radu Cotescu
 Fix For: Scripting HTL Engine 1.3.4-1.4.0


Since {{org.apache.sling.commons.compiler.source.JavaEscapeHelper}} and 
{{org.apache.sling.scripting.sightly.java.compiler.JavaEscapeUtils}} was 
deprecated, it's better to switch to the class provided by the Commons Compiler 
module.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (SLING-9145) Upgrade to parent pom 38

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-9145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu resolved SLING-9145.
-
Resolution: Fixed

Fixed in [commit 
550a100|https://github.com/apache/sling-org-apache-sling-commons-compiler/commit/550a100].

> Upgrade to parent pom 38
> 
>
> Key: SLING-9145
> URL: https://issues.apache.org/jira/browse/SLING-9145
> Project: Sling
>  Issue Type: Sub-task
>  Components: Commons
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: Commons Compiler 2.4.0
>
>
> The {{org.apache.sling.commons.compiler}} project uses Sling parent version 
> 30. By upgrading to {{sling-bundle-parent}} 38 we could remove a lot of 
> redundant information provided in the {{org.apache.sling.commons.compiler}}'s 
> pom and we would also allow building this module with Java 11.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (SLING-9146) Make the Bundle-DocURL use https

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-9146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu resolved SLING-9146.
-
Resolution: Fixed

Fixed in [commit 129ae7a|https://github.com/apache/sling-parent/commit/129ae7a].

> Make the Bundle-DocURL use https
> 
>
> Key: SLING-9146
> URL: https://issues.apache.org/jira/browse/SLING-9146
> Project: Sling
>  Issue Type: Bug
>Affects Versions: Bundle Parent 36
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: Bundle Parent 39
>
>
> SLING-8538 hardcoded the {{Bundle-DocURL}} header to 
> {{http://sling.apache.org}}. We should switch this URL to {{https}}.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (SLING-9146) Make the Bundle-DocURL use https

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-9146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu reassigned SLING-9146:
---

Assignee: Radu Cotescu

> Make the Bundle-DocURL use https
> 
>
> Key: SLING-9146
> URL: https://issues.apache.org/jira/browse/SLING-9146
> Project: Sling
>  Issue Type: Bug
>Affects Versions: Bundle Parent 36
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: Bundle Parent 39
>
>
> SLING-8538 hardcoded the {{Bundle-DocURL}} header to 
> {{http://sling.apache.org}}. We should switch this URL to {{https}}.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (SLING-9146) Make the Bundle-DocURL use https

[Radu Cotescu (Jira)]

Radu Cotescu created SLING-9146:
---

 Summary: Make the Bundle-DocURL use https
 Key: SLING-9146
 URL: https://issues.apache.org/jira/browse/SLING-9146
 Project: Sling
  Issue Type: Bug
Affects Versions: Bundle Parent 36
Reporter: Radu Cotescu
 Fix For: Bundle Parent 39


SLING-8538 hardcoded the {{Bundle-DocURL}} header to 
{{http://sling.apache.org}}. We should switch this URL to {{https}}.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (SLING-9145) Upgrade to parent pom 38

[Radu Cotescu (Jira)]

Radu Cotescu created SLING-9145:
---

 Summary: Upgrade to parent pom 38
 Key: SLING-9145
 URL: https://issues.apache.org/jira/browse/SLING-9145
 Project: Sling
  Issue Type: Sub-task
  Components: Commons
Reporter: Radu Cotescu
Assignee: Radu Cotescu
 Fix For: Commons Compiler 2.4.0


The {{org.apache.sling.commons.compiler}} project uses Sling parent version 30. 
By upgrading to {{sling-bundle-parent}} 38 we could remove a lot of redundant 
information provided in the {{org.apache.sling.commons.compiler}}'s pom and we 
would also allow building this module with Java 11.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (SLING-9144) Replace unmaintained findbugs plugin with spotbugs

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-9144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu resolved SLING-9144.
-
Resolution: Fixed

Fixed in [commit 
e7fa488|https://github.com/apache/sling-org-apache-sling-scripting-sightly-compiler-java/commit/e7fa488].

> Replace unmaintained findbugs plugin with spotbugs
> --
>
> Key: SLING-9144
> URL: https://issues.apache.org/jira/browse/SLING-9144
> Project: Sling
>  Issue Type: Improvement
>  Components: Scripting
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: Scripting HTL Java Compiler 1.1.6-1.4.0
>
>
> The {{findbugs-maven-plugin}} is unmaintained, but a replacement is 
> available: {{spotbugs-maven-plugin}}. Since Spotbugs has better support for 
> Java 11 it's recommended to switch to the newer plugin.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (SLING-9144) Replace unmaintained findbugs plugin with spotbugs

[Radu Cotescu (Jira)]

Radu Cotescu created SLING-9144:
---

 Summary: Replace unmaintained findbugs plugin with spotbugs
 Key: SLING-9144
 URL: https://issues.apache.org/jira/browse/SLING-9144
 Project: Sling
  Issue Type: Improvement
  Components: Scripting
Reporter: Radu Cotescu
Assignee: Radu Cotescu
 Fix For: Scripting HTL Java Compiler 1.1.6-1.4.0


The {{findbugs-maven-plugin}} is unmaintained, but a replacement is available: 
{{spotbugs-maven-plugin}}. Since Spotbugs has better support for Java 11 it's 
recommended to switch to the newer plugin.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (SLING-9142) Deprecate JavaEscapeUtils and switch to JavaEscapeHelper

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-9142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu resolved SLING-9142.
-
Resolution: Fixed

Fixed in [commit 
7476e0e|https://github.com/apache/sling-org-apache-sling-scripting-sightly-compiler-java/commit/7476e0e].

> Deprecate JavaEscapeUtils and switch to JavaEscapeHelper
> 
>
> Key: SLING-9142
> URL: https://issues.apache.org/jira/browse/SLING-9142
> Project: Sling
>  Issue Type: Sub-task
>  Components: Scripting
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: Scripting HTL Java Compiler 1.1.6-1.4.0
>
>
> With {{org.apache.sling.commons.compiler.source.JavaEscapeHelper}} extracted 
> to the {{org.apache.sling.commons.compiler}}, the  
> {{org.apache.sling.scripting.sightly.java.compiler.JavaEscapeUtils }} should 
> be deprecated and its usage removed from the HTL Java Compiler.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (SLING-9142) Deprecate JavaEscapeUtils and switch to JavaEscapeHelper

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-9142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu updated SLING-9142:

Fix Version/s: (was: Scripting HTL Java Compiler 1.2.0-1.4.0)

> Deprecate JavaEscapeUtils and switch to JavaEscapeHelper
> 
>
> Key: SLING-9142
> URL: https://issues.apache.org/jira/browse/SLING-9142
> Project: Sling
>  Issue Type: Sub-task
>  Components: Scripting
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: Scripting HTL Java Compiler 1.1.6-1.4.0
>
>
> With {{org.apache.sling.commons.compiler.source.JavaEscapeHelper}} extracted 
> to the {{org.apache.sling.commons.compiler}}, the  
> {{org.apache.sling.scripting.sightly.java.compiler.JavaEscapeUtils }} should 
> be deprecated and its usage removed from the HTL Java Compiler.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (SLING-9142) Deprecate JavaEscapeUtils and switch to JavaEscapeHelper

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-9142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu updated SLING-9142:

Fix Version/s: Scripting HTL Java Compiler 1.1.6-1.4.0

> Deprecate JavaEscapeUtils and switch to JavaEscapeHelper
> 
>
> Key: SLING-9142
> URL: https://issues.apache.org/jira/browse/SLING-9142
> Project: Sling
>  Issue Type: Sub-task
>  Components: Scripting
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: Scripting HTL Java Compiler 1.2.0-1.4.0, Scripting HTL 
> Java Compiler 1.1.6-1.4.0
>
>
> With {{org.apache.sling.commons.compiler.source.JavaEscapeHelper}} extracted 
> to the {{org.apache.sling.commons.compiler}}, the  
> {{org.apache.sling.scripting.sightly.java.compiler.JavaEscapeUtils }} should 
> be deprecated and its usage removed from the HTL Java Compiler.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (SLING-9142) Deprecate JavaEscapeUtils and switch to JavaEscapeHelper

[Radu Cotescu (Jira)]

Radu Cotescu created SLING-9142:
---

 Summary: Deprecate JavaEscapeUtils and switch to JavaEscapeHelper
 Key: SLING-9142
 URL: https://issues.apache.org/jira/browse/SLING-9142
 Project: Sling
  Issue Type: Sub-task
  Components: Scripting
Reporter: Radu Cotescu
Assignee: Radu Cotescu
 Fix For: Scripting HTL Java Compiler 1.2.0-1.4.0


With {{org.apache.sling.commons.compiler.source.JavaEscapeHelper}} extracted to 
the {{org.apache.sling.commons.compiler}}, the  
{{org.apache.sling.scripting.sightly.java.compiler.JavaEscapeUtils }} should be 
deprecated and its usage removed from the HTL Java Compiler.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (SLING-9141) Refactor modules generating Java code to use the org.apache.sling.commons.compiler.source.JavaEscapeHelper utility

[Radu Cotescu (Jira)]

Radu Cotescu created SLING-9141:
---

 Summary: Refactor modules generating Java code to use the 
org.apache.sling.commons.compiler.source.JavaEscapeHelper utility
 Key: SLING-9141
 URL: https://issues.apache.org/jira/browse/SLING-9141
 Project: Sling
  Issue Type: Task
  Components: Scripting, Tooling
Reporter: Radu Cotescu
Assignee: Radu Cotescu


Several Sling modules generate Java code (e.g. HTL compilers, JSP script 
engine, JSPC Maven Plugin, HTL Maven Plugin), but each has its own strategy / 
classes for generating valid Java code / classes. Since the 
{{org.apache.sling.commons.compiler.source.JavaEscapeHelper}} is an easy to 
reuse class, it would be better to refactor modules to rely on this helper, in 
order to generate code / classes using the same naming patterns.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (SLING-9135) Move org.apache.sling.scripting.sightly.java.compiler.JavaEscapeUtils into org.apache.sling.commons.compiler

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-9135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu resolved SLING-9135.
-
Resolution: Fixed

Fixed in [commit 
0d8f738|https://github.com/apache/sling-org-apache-sling-commons-compiler/commit/0d8f738].

> Move org.apache.sling.scripting.sightly.java.compiler.JavaEscapeUtils into 
> org.apache.sling.commons.compiler
> 
>
> Key: SLING-9135
> URL: https://issues.apache.org/jira/browse/SLING-9135
> Project: Sling
>  Issue Type: Improvement
>  Components: Commons
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: Commons Compiler 2.4.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> The {{org.apache.sling.scripting.sightly.java.compiler.JavaEscapeUtils}} 
> class, which borrows some methods from 
> {{org.apache.sling.scripting.jsp.jasper.compiler.JspUtil}}, should be 
> extracted into a more lightweight bundle, like 
> {{org.apache.sling.commons.compiler}}, to improve its reuse potential.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (SLING-9140) fallback valuemap

[Radu Cotescu (Jira)]

[ 
https://issues.apache.org/jira/browse/SLING-9140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17044327#comment-17044327
 ] 

Radu Cotescu commented on SLING-9140:
-

[~npeltier], I think you pasted a wrong link in the description. Please create 
a PR at https://github.com/apache/sling-org-apache-sling-api for discussing the 
API change.

> fallback valuemap
> -
>
> Key: SLING-9140
> URL: https://issues.apache.org/jira/browse/SLING-9140
> Project: Sling
>  Issue Type: Improvement
>  Components: API
>Reporter: Nicolas Peltier
>Assignee: Nicolas Peltier
>Priority: Major
>
> utility class to provide a simple way to have a fallback valuemap
> discussed here 
> [https://codecov.io/github/npeltier/example-java/commit/6a13059166decf92abc0bdc1b9c44f1ab7d77ec0]
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Closed] (SLING-9085) Integration tests fail to download from Maven Central, https required

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-9085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu closed SLING-9085.
---

> Integration tests fail to download from Maven Central, https required
> -
>
> Key: SLING-9085
> URL: https://issues.apache.org/jira/browse/SLING-9085
> Project: Sling
>  Issue Type: Bug
>  Components: Repoinit
>Affects Versions: Repoinit JCR 1.1.18
>Reporter: Bertrand Delacretaz
>Assignee: Bertrand Delacretaz
>Priority: Minor
> Fix For: Repoinit JCR 1.1.20
>
> Attachments: sling-org-apache-sling-jcr-repoinit.patch
>
>
> The JCR repoinit integration tests fail if they need to download anything 
> from Maven Central, this needs to be fixed, for example in a similar way to 
> [1].
> The workaround is to download the missing dependencies to the local Maven 
> repository before running the tests, like
> {code}
> mvn dependency:get -DgroupId=org.apache.sling 
> -DartifactId=org.apache.sling.scripting.core -Dversion=2.0.56
> {code}
> [1] 
> https://github.com/apache/sling-org-apache-sling-servlets-resolver/blob/master/src/test/java/org/apache/sling/servlets/resolver/it/ServletResolverTestSupport.java



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Closed] (SLING-9091) Principal-based AC-setup fails for transient service users

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-9091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu closed SLING-9091.
---

> Principal-based AC-setup fails for transient service users
> --
>
> Key: SLING-9091
> URL: https://issues.apache.org/jira/browse/SLING-9091
> Project: Sling
>  Issue Type: Bug
>  Components: Repoinit
>Reporter: Angela Schreiber
>Assignee: Angela Schreiber
>Priority: Major
> Fix For: Repoinit JCR 1.1.20
>
>  Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> while conducting additional tests with repo-init i noticed that 
> {{TestUtil.parseAndExecute}} always persists a given operation, which doesn't 
> entirely seem to reflect that nature of the {{RepositoryInitializer}} which 
> will only call {{Session.save}} after the processing of a list of operations. 
> While each create-path operation is already following by a save-call to 
> prevent issues with the resource-based access control setup, the 
> principal-based ac-setup will currently fail if the service user principal 
> has not been persisted.
> Proposed fix: if the principal-lookup returns {{null}} during principal-based 
> ac setup -> retry after saving pending changes. That's at least consistent 
> with the current behaviour in the resource-based setup.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (SLING-9135) Move org.apache.sling.scripting.sightly.java.compiler.JavaEscapeUtils into org.apache.sling.commons.compiler

[Radu Cotescu (Jira)]

Radu Cotescu created SLING-9135:
---

 Summary: Move 
org.apache.sling.scripting.sightly.java.compiler.JavaEscapeUtils into 
org.apache.sling.commons.compiler
 Key: SLING-9135
 URL: https://issues.apache.org/jira/browse/SLING-9135
 Project: Sling
  Issue Type: Improvement
  Components: Commons
Reporter: Radu Cotescu
Assignee: Radu Cotescu
 Fix For: Commons Compiler 2.4.0


The {{org.apache.sling.scripting.sightly.java.compiler.JavaEscapeUtils}} class, 
which borrows some methods from 
{{org.apache.sling.scripting.jsp.jasper.compiler.JspUtil}}, should be extracted 
into a more lightweight bundle, to improve its reuse potential.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (SLING-9135) Move org.apache.sling.scripting.sightly.java.compiler.JavaEscapeUtils into org.apache.sling.commons.compiler

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-9135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu updated SLING-9135:

Description: The 
{{org.apache.sling.scripting.sightly.java.compiler.JavaEscapeUtils}} class, 
which borrows some methods from 
{{org.apache.sling.scripting.jsp.jasper.compiler.JspUtil}}, should be extracted 
into a more lightweight bundle, like {{org.apache.sling.commons.compiler}}, to 
improve its reuse potential.  (was: The 
{{org.apache.sling.scripting.sightly.java.compiler.JavaEscapeUtils}} class, 
which borrows some methods from 
{{org.apache.sling.scripting.jsp.jasper.compiler.JspUtil}}, should be extracted 
into a more lightweight bundle, to improve its reuse potential.)

> Move org.apache.sling.scripting.sightly.java.compiler.JavaEscapeUtils into 
> org.apache.sling.commons.compiler
> 
>
> Key: SLING-9135
> URL: https://issues.apache.org/jira/browse/SLING-9135
> Project: Sling
>  Issue Type: Improvement
>  Components: Commons
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: Commons Compiler 2.4.0
>
>
> The {{org.apache.sling.scripting.sightly.java.compiler.JavaEscapeUtils}} 
> class, which borrows some methods from 
> {{org.apache.sling.scripting.jsp.jasper.compiler.JspUtil}}, should be 
> extracted into a more lightweight bundle, like 
> {{org.apache.sling.commons.compiler}}, to improve its reuse potential.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (SLING-9083) Add support for authenticated requests when checking a release's build status

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-9083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu updated SLING-9083:

Description: 
The {{org.apache.sling.cli.impl.ci.CIStatusValidator}} checks if a release's 
build status is valid, when verifying a release. Depending on the network from 
which the requests originate, GitHub might enforce its API rate limiting, 
leading to a failure in the validator - the {{success}} JSON key is missing 
from the response. On one hand, the validator's JSON parsing could be improved 
to not fail if this key is missing. However, if a request is authenticated 
(usually with a GitHub access token), the rate limiting is not enforced (or 
better said the limit is so high that it should not be reached).

This issue should implement both suggestions from above:
# make the JSON parsing more resilient
# optionally use a GitHub access token, if provided in the environment, top 
perform authenticated requests against the GitHub API

  was:
The {{org.apache.sling.cli.impl.ci.CIStatusValidator}} checks if a release's 
build status is valid, when verifying a release. Depending on the network from 
which the requests originate, GitHub might enforce its API rate limiting, 
leading to a failure in the validator - the {{success}} JSON key is missing 
from the response. On one hand, the validator's JSON parsing could be improved 
to not fail if this key is missing. However if a request is authenticated 
(usually with a GitHub access token), the rate limiting is not enforced (or 
better said the limit is so high that it should not be reached).

This issue should implement both suggestions from above:
# make the JSON parsing more resilient
# optionally use a GitHub access token, if provided in the environment, top 
perform authenticated requests against the GitHub API


> Add support for authenticated requests when checking a release's build status
> -
>
> Key: SLING-9083
> URL: https://issues.apache.org/jira/browse/SLING-9083
> Project: Sling
>  Issue Type: Improvement
>  Components: Tooling
>Reporter: Radu Cotescu
>Priority: Major
> Fix For: Committer CLI 1.0.0
>
>
> The {{org.apache.sling.cli.impl.ci.CIStatusValidator}} checks if a release's 
> build status is valid, when verifying a release. Depending on the network 
> from which the requests originate, GitHub might enforce its API rate 
> limiting, leading to a failure in the validator - the {{success}} JSON key is 
> missing from the response. On one hand, the validator's JSON parsing could be 
> improved to not fail if this key is missing. However, if a request is 
> authenticated (usually with a GitHub access token), the rate limiting is not 
> enforced (or better said the limit is so high that it should not be reached).
> This issue should implement both suggestions from above:
> # make the JSON parsing more resilient
> # optionally use a GitHub access token, if provided in the environment, top 
> perform authenticated requests against the GitHub API



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (SLING-9083) Add support for authenticated requests when checking a release's build status

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-9083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu updated SLING-9083:

Description: 
The {{org.apache.sling.cli.impl.ci.CIStatusValidator}} checks if a release's 
build status is valid, when verifying a release. Depending on the network from 
which the requests originate, GitHub might enforce its API rate limiting, 
leading to a failure in the validator - the {{success}} JSON key is missing 
from the response. On one hand, the validator's JSON parsing could be improved 
to not fail if this key is missing. However if a request is authenticated 
(usually with a GitHub access token), the rate limiting is not enforced (or 
better said the limit is so high that it should not be reached).

This issue should implement both suggestions from above:
# make the JSON parsing more resilient
# optionally use a GitHub access token, if provided in the environment, top 
perform authenticated requests against the GitHub API

  was:
The {{CIValidator}} checks if a release's build status is valid, when verifying 
a release. Depending on the network from which the requests originate, GitHub 
might enforce its API rate limiting, leading to a failure in the validator - 
the {{success}} JSON key is missing from the response. On one hand, the 
validator's JSON parsing could be improved to not fail if this key is missing. 
However if a request is authenticated (usually with a GitHub access token), the 
rate limiting is not enforced (or better said the limit is so high that it 
should not be reached).

This issue should implement both suggestions from above:
# make the JSON parsing more resilient
# optionally use a GitHub access token, if provided in the environment, top 
perform authenticated requests against the GitHub API


> Add support for authenticated requests when checking a release's build status
> -
>
> Key: SLING-9083
> URL: https://issues.apache.org/jira/browse/SLING-9083
> Project: Sling
>  Issue Type: Improvement
>  Components: Tooling
>Reporter: Radu Cotescu
>Priority: Major
> Fix For: Committer CLI 1.0.0
>
>
> The {{org.apache.sling.cli.impl.ci.CIStatusValidator}} checks if a release's 
> build status is valid, when verifying a release. Depending on the network 
> from which the requests originate, GitHub might enforce its API rate 
> limiting, leading to a failure in the validator - the {{success}} JSON key is 
> missing from the response. On one hand, the validator's JSON parsing could be 
> improved to not fail if this key is missing. However if a request is 
> authenticated (usually with a GitHub access token), the rate limiting is not 
> enforced (or better said the limit is so high that it should not be reached).
> This issue should implement both suggestions from above:
> # make the JSON parsing more resilient
> # optionally use a GitHub access token, if provided in the environment, top 
> perform authenticated requests against the GitHub API



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (SLING-9083) Add support for authenticated requests when checking a release's build status

[Radu Cotescu (Jira)]

Radu Cotescu created SLING-9083:
---

 Summary: Add support for authenticated requests when checking a 
release's build status
 Key: SLING-9083
 URL: https://issues.apache.org/jira/browse/SLING-9083
 Project: Sling
  Issue Type: Improvement
  Components: Tooling
Reporter: Radu Cotescu
 Fix For: Committer CLI 1.0.0


The {{CIValidator}} checks if a release's build status is valid, when verifying 
a release. Depending on the network from which the requests originate, GitHub 
might enforce its API rate limiting, leading to a failure in the validator - 
the {{success}} JSON key is missing from the response. On one hand, the 
validator's JSON parsing could be improved to not fail if this key is missing. 
However if a request is authenticated (usually with a GitHub access token), the 
rate limiting is not enforced (or better said the limit is so high that it 
should not be reached).

This issue should implement both suggestions from above:
# make the JSON parsing more resilient
# optionally use a GitHub access token, if provided in the environment, top 
perform authenticated requests against the GitHub API



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (SLING-9048) The HTL engine does not specify the correct io.sightly.runtime requirement version range

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-9048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu resolved SLING-9048.
-
Resolution: Fixed

Fixed in [commit 
a584639|https://github.com/apache/sling-org-apache-sling-scripting-sightly/commit/a584639].

> The HTL engine does not specify the correct io.sightly.runtime requirement 
> version range
> 
>
> Key: SLING-9048
> URL: https://issues.apache.org/jira/browse/SLING-9048
> Project: Sling
>  Issue Type: Bug
>  Components: Scripting
>Affects Versions: Scripting HTL Engine 1.2.0-1.4.0
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Minor
> Fix For: Scripting HTL Engine 1.3.4-1.4.0
>
>
> When SLING-8471 was implemented, the transition from the 
> {{maven-bundle-plugin}} to the {{bnd-maven-plugin}} introduced the error of 
> defining the {{io.sightly.runtime}} requirement as:
> {code:java}
> Require-Capability: io.sightly.runtime; 
> filter:="(&(version<=1.0)(!(version>=2.0)))"
> {code}
> instead of:
> {code:java}
> Require-Capability: io.sightly.runtime; 
> filter:="(&(version>=1.0)(!(version>=2.0)))"
> {code}
> While in practice this doesn't affect a regular Sling setup, it should be 
> corrected.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (SLING-9048) The HTL engine does not specify the correct io.sightly.runtime requirement version range

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-9048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu reassigned SLING-9048:
---

Assignee: Radu Cotescu

> The HTL engine does not specify the correct io.sightly.runtime requirement 
> version range
> 
>
> Key: SLING-9048
> URL: https://issues.apache.org/jira/browse/SLING-9048
> Project: Sling
>  Issue Type: Bug
>  Components: Scripting
>Affects Versions: Scripting HTL Engine 1.2.0-1.4.0
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Minor
> Fix For: Scripting HTL Engine 1.3.4-1.4.0
>
>
> When SLING-8471 was implemented, the transition from the 
> {{maven-bundle-plugin}} to the {{bnd-maven-plugin}} introduced the error of 
> defining the {{io.sightly.runtime}} requirement as:
> {code:java}
> Require-Capability: io.sightly.runtime; 
> filter:="(&(version<=1.0)(!(version>=2.0)))"
> {code}
> instead of:
> {code:java}
> Require-Capability: io.sightly.runtime; 
> filter:="(&(version>=1.0)(!(version>=2.0)))"
> {code}
> While in practice this doesn't affect a regular Sling setup, it should be 
> corrected.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (SLING-9048) The HTL engine does not specify the correct io.sightly.runtime requirement version range

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-9048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu updated SLING-9048:

Priority: Minor  (was: Major)

> The HTL engine does not specify the correct io.sightly.runtime requirement 
> version range
> 
>
> Key: SLING-9048
> URL: https://issues.apache.org/jira/browse/SLING-9048
> Project: Sling
>  Issue Type: Bug
>  Components: Scripting
>Affects Versions: Scripting HTL Engine 1.2.0-1.4.0
>Reporter: Radu Cotescu
>Priority: Minor
> Fix For: Scripting HTL Engine 1.3.4-1.4.0
>
>
> When SLING-8471 was implemented, the transition from the 
> {{maven-bundle-plugin}} to the {{bnd-maven-plugin}} introduced the error of 
> defining the {{io.sightly.runtime}} requirement as:
> {code:java}
> Require-Capability: io.sightly.runtime; 
> filter:="(&(version<=1.0)(!(version>=2.0)))"
> {code}
> instead of:
> {code:java}
> Require-Capability: io.sightly.runtime; 
> filter:="(&(version>=1.0)(!(version>=2.0)))"
> {code}
> While in practice this doesn't affect a regular Sling setup, it should be 
> corrected.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (SLING-9048) The HTL engine does not specify the correct io.sightly.runtime requirement version range

[Radu Cotescu (Jira)]

Radu Cotescu created SLING-9048:
---

 Summary: The HTL engine does not specify the correct 
io.sightly.runtime requirement version range
 Key: SLING-9048
 URL: https://issues.apache.org/jira/browse/SLING-9048
 Project: Sling
  Issue Type: Bug
  Components: Scripting
Affects Versions: Scripting HTL Engine 1.2.0-1.4.0
Reporter: Radu Cotescu
 Fix For: Scripting HTL Engine 1.3.4-1.4.0


When SLING-8471 was implemented, the transition from the 
{{maven-bundle-plugin}} to the {{bnd-maven-plugin}} introduced the error of 
defining the {{io.sightly.runtime}} requirement as:
{code:java}
Require-Capability: io.sightly.runtime; 
filter:="(&(version<=1.0)(!(version>=2.0)))"
{code}
instead of:
{code:java}
Require-Capability: io.sightly.runtime; 
filter:="(&(version>=1.0)(!(version>=2.0)))"
{code}

While in practice this doesn't affect a regular Sling setup, it should be 
corrected.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (SLING-9047) The CIStatusValidator cannot verify multi-module releases

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-9047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu resolved SLING-9047.
-
Resolution: Fixed

Fixed in [commit 
646b413|https://github.com/apache/sling-org-apache-sling-committer-cli/commit/646b413].

> The CIStatusValidator cannot verify multi-module releases
> -
>
> Key: SLING-9047
> URL: https://issues.apache.org/jira/browse/SLING-9047
> Project: Sling
>  Issue Type: Bug
>  Components: Tooling
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: Committer CLI 1.0.0
>
>
> The {{CIStatusValidator}} cannot verify multi-module releases, since the 
> current algorithm for detecting the GitHub endpoint for retrieving the build 
> status [0] relies on the artifact name + version for the reference. This 
> works for regular single-module releases, since the tag corresponds to the 
> artifact name + version. However, in the case of multi-module releases the 
> validator fails. The reliable way of validating releases is by just using the 
> tag name, which in the case of a release available in the pom.
> [0] - 
> https://developer.github.com/v3/repos/statuses/#get-the-combined-status-for-a-specific-ref



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (SLING-9047) The CIStatusValidator cannot verify multi-module releases

[Radu Cotescu (Jira)]

Radu Cotescu created SLING-9047:
---

 Summary: The CIStatusValidator cannot verify multi-module releases
 Key: SLING-9047
 URL: https://issues.apache.org/jira/browse/SLING-9047
 Project: Sling
  Issue Type: Bug
  Components: Tooling
Reporter: Radu Cotescu
 Fix For: Committer CLI 1.0.0


The {{CIStatusValidator}} cannot verify multi-module releases, since the 
current algorithm for detecting the GitHub endpoint for retrieving the build 
status [0] relies on the artifact name + version for the reference. This works 
for regular single-module releases, since the tag corresponds to the artifact 
name + version. However, in the case of multi-module releases the validator 
fails. The reliable way of validating releases is by just using the tag name, 
which in the case of a release available in the pom.

[0] - 
https://developer.github.com/v3/repos/statuses/#get-the-combined-status-for-a-specific-ref



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (SLING-9047) The CIStatusValidator cannot verify multi-module releases

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-9047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu reassigned SLING-9047:
---

Assignee: Radu Cotescu

> The CIStatusValidator cannot verify multi-module releases
> -
>
> Key: SLING-9047
> URL: https://issues.apache.org/jira/browse/SLING-9047
> Project: Sling
>  Issue Type: Bug
>  Components: Tooling
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: Committer CLI 1.0.0
>
>
> The {{CIStatusValidator}} cannot verify multi-module releases, since the 
> current algorithm for detecting the GitHub endpoint for retrieving the build 
> status [0] relies on the artifact name + version for the reference. This 
> works for regular single-module releases, since the tag corresponds to the 
> artifact name + version. However, in the case of multi-module releases the 
> validator fails. The reliable way of validating releases is by just using the 
> tag name, which in the case of a release available in the pom.
> [0] - 
> https://developer.github.com/v3/repos/statuses/#get-the-combined-status-for-a-specific-ref



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Closed] (SLING-9035) The XSSProtectionAPIWebConsolePlugin fails to load resources when deployed under a custom context path

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-9035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu closed SLING-9035.
---

> The XSSProtectionAPIWebConsolePlugin fails to load resources when deployed 
> under a custom context path
> --
>
> Key: SLING-9035
> URL: https://issues.apache.org/jira/browse/SLING-9035
> Project: Sling
>  Issue Type: Bug
>  Components: XSS Protection API
>Affects Versions: XSS Protection API 2.2.0
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: XSS Protection API 2.2.2
>
>
> The XSSProtectionAPIWebConsolePlugin fails to load CSS / JS resources when 
> deployed under a custom context path.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (SLING-9046) Provide analyser that checks bundles for embedded bundles

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-9046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu updated SLING-9046:

Summary: Provide analyser that checks bundles for embedded bundles  (was: 
Provide analyses that checks bundles for embedded bundles)

> Provide analyser that checks bundles for embedded bundles
> -
>
> Key: SLING-9046
> URL: https://issues.apache.org/jira/browse/SLING-9046
> Project: Sling
>  Issue Type: Improvement
>  Components: Feature Model Analyser
>Reporter: Radu Cotescu
>Priority: Major
> Fix For: Feature Model Analyser 1.2.6
>
>
> When using the feature model, a bundle should not embed other bundles. The 
> feature launcher and the framework should manage bundle lifecycles, not 
> bundles.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (SLING-9046) Provide analyses that checks bundles for embedded bundles

[Radu Cotescu (Jira)]

Radu Cotescu created SLING-9046:
---

 Summary: Provide analyses that checks bundles for embedded bundles
 Key: SLING-9046
 URL: https://issues.apache.org/jira/browse/SLING-9046
 Project: Sling
  Issue Type: Improvement
  Components: Feature Model Analyser
Reporter: Radu Cotescu
 Fix For: Feature Model Analyser 1.2.6


When using the feature model, a bundle should not embed other bundles. The 
feature launcher and the framework should manage bundle lifecycles, not bundles.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (SLING-9035) The XSSProtectionAPIWebConsolePlugin fails to load resources when deployed under a custom context path

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-9035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu resolved SLING-9035.
-
Resolution: Fixed

Fixed in [commit 
08aac0f|https://github.com/apache/sling-org-apache-sling-xss/commit/08aac0f].

> The XSSProtectionAPIWebConsolePlugin fails to load resources when deployed 
> under a custom context path
> --
>
> Key: SLING-9035
> URL: https://issues.apache.org/jira/browse/SLING-9035
> Project: Sling
>  Issue Type: Bug
>  Components: XSS Protection API
>Affects Versions: XSS Protection API 2.2.0
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: XSS Protection API 2.2.2
>
>
> The XSSProtectionAPIWebConsolePlugin fails to load CSS / JS resources when 
> deployed under a custom context path.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (SLING-9035) The XSSProtectionAPIWebConsolePlugin fails to load resources when deployed under a custom context path

[Radu Cotescu (Jira)]

Radu Cotescu created SLING-9035:
---

 Summary: The XSSProtectionAPIWebConsolePlugin fails to load 
resources when deployed under a custom context path
 Key: SLING-9035
 URL: https://issues.apache.org/jira/browse/SLING-9035
 Project: Sling
  Issue Type: Bug
  Components: XSS Protection API
Affects Versions: XSS Protection API 2.2.0
Reporter: Radu Cotescu
Assignee: Radu Cotescu
 Fix For: XSS Protection API 2.2.2


The XSSProtectionAPIWebConsolePlugin fails to load CSS / JS resources when 
deployed under a custom context path.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (SLING-9034) The MemebersFinder service throws a NPE if the name is missing from an email address

[Radu Cotescu (Jira)]

Radu Cotescu created SLING-9034:
---

 Summary: The MemebersFinder service throws a NPE if the name is 
missing from an email address
 Key: SLING-9034
 URL: https://issues.apache.org/jira/browse/SLING-9034
 Project: Sling
  Issue Type: Bug
  Components: Tooling
Reporter: Radu Cotescu
Assignee: Radu Cotescu
 Fix For: Committer CLI 1.0.0


The {{MemebersFinder}} service throws a NPE if the name is missing from an 
email address.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (SLING-9034) The MemebersFinder service throws a NPE if the name is missing from an email address

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-9034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu resolved SLING-9034.
-
Resolution: Fixed

Fixed in [commit 
ea8c0ab|https://github.com/apache/sling-org-apache-sling-committer-cli/commit/ea8c0ab].

> The MemebersFinder service throws a NPE if the name is missing from an email 
> address
> 
>
> Key: SLING-9034
> URL: https://issues.apache.org/jira/browse/SLING-9034
> Project: Sling
>  Issue Type: Bug
>  Components: Tooling
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: Committer CLI 1.0.0
>
>
> The {{MemebersFinder}} service throws a NPE if the name is missing from an 
> email address.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (SLING-5720) ScriptEngineManagerFactory is not updating ScriptEngineFactory's cached service properties on modification

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-5720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu updated SLING-5720:

Fix Version/s: Servlets Resolver 2.5.10

> ScriptEngineManagerFactory is not updating ScriptEngineFactory's cached 
> service properties on modification
> --
>
> Key: SLING-5720
> URL: https://issues.apache.org/jira/browse/SLING-5720
> Project: Sling
>  Issue Type: Bug
>  Components: Scripting
>Affects Versions: Scripting Core 2.0.36
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
>Priority: Major
> Fix For: API 2.22.0, Scripting Core 2.1.2, Servlets Resolver 
> 2.5.10
>
>
> {{ScriptEngineManagerFactory}} should handle modified services. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Comment Edited] (SLING-5720) ScriptEngineManagerFactory is not updating ScriptEngineFactory's cached service properties on modification

[Radu Cotescu (Jira)]

[ 
https://issues.apache.org/jira/browse/SLING-5720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17024538#comment-17024538
 ] 

Radu Cotescu edited comment on SLING-5720 at 1/27/20 6:09 PM:
--

Scripting Core would still need to be released - I accidentally closed this 
issue when I released API 2.22.0.

Due to the fact that {{org.apache.sling.servlets.resolver}} imports the 
{{org.apache.sling.api.scripting}} package, the Servlets Resolver bundle also 
needs a new release. 


was (Author: radu.cotescu):
Scripting Core would still need to be released - I accidentally closed this 
issue when I released API 2.22.0.

> ScriptEngineManagerFactory is not updating ScriptEngineFactory's cached 
> service properties on modification
> --
>
> Key: SLING-5720
> URL: https://issues.apache.org/jira/browse/SLING-5720
> Project: Sling
>  Issue Type: Bug
>  Components: Scripting
>Affects Versions: Scripting Core 2.0.36
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
>Priority: Major
> Fix For: API 2.22.0, Scripting Core 2.1.2
>
>
> {{ScriptEngineManagerFactory}} should handle modified services. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (SLING-5720) ScriptEngineManagerFactory is not updating ScriptEngineFactory's cached service properties on modification

[Radu Cotescu (Jira)]

[ 
https://issues.apache.org/jira/browse/SLING-5720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17024538#comment-17024538
 ] 

Radu Cotescu commented on SLING-5720:
-

Scripting Core would still need to be released - I accidentally closed this 
issue when I released API 2.22.0.

> ScriptEngineManagerFactory is not updating ScriptEngineFactory's cached 
> service properties on modification
> --
>
> Key: SLING-5720
> URL: https://issues.apache.org/jira/browse/SLING-5720
> Project: Sling
>  Issue Type: Bug
>  Components: Scripting
>Affects Versions: Scripting Core 2.0.36
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
>Priority: Major
> Fix For: API 2.22.0, Scripting Core 2.1.2
>
>
> {{ScriptEngineManagerFactory}} should handle modified services. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Closed] (SLING-9025) The MetricsService keeps stale metrics after bundles that have registered metrics are removed

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-9025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu closed SLING-9025.
---

> The MetricsService keeps stale metrics after bundles that have registered 
> metrics are removed
> -
>
> Key: SLING-9025
> URL: https://issues.apache.org/jira/browse/SLING-9025
> Project: Sling
>  Issue Type: Bug
>Affects Versions: Commons Metrics 1.0.0
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: Commons Metrics 1.2.8
>
>
> The {{MetricsService}} keeps stale metrics after bundles that have registered 
> metrics are removed. Although the respective metrics are removed from the 
> {{MetricsRegistry}}, the {{MetricsService}} internally caches the metrics and 
> does not remove them once metric mappings are removed.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Closed] (SLING-8506) Make testing compliant with Java 9 and higher

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-8506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu closed SLING-8506.
---

> Make testing compliant with Java 9 and higher
> -
>
> Key: SLING-8506
> URL: https://issues.apache.org/jira/browse/SLING-8506
> Project: Sling
>  Issue Type: Task
>  Components: Commons
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
>Priority: Major
> Fix For: Commons Metrics 1.2.8
>
>
> * Use Sling Bundle Parent 35
> * Update Pax Exam to 4.13.1
> * Update Testing PaxExam to 3.0.0
> * Update Felix Framework to 6.0.3



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Closed] (SLING-9019) The XSSFilter will mark URLs containing both escaped characters and HTML entities as invalid

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-9019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu closed SLING-9019.
---

> The XSSFilter will mark URLs containing both escaped characters and HTML 
> entities as invalid
> 
>
> Key: SLING-9019
> URL: https://issues.apache.org/jira/browse/SLING-9019
> Project: Sling
>  Issue Type: Bug
>  Components: XSS Protection API
>Affects Versions: XSS Protection API 2.0.4
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: XSS Protection API 2.2.0
>
>
> A URL similar to {{http://localhost/?q=a+br=1}} will be marked as 
> invalid by the {{XSSFilterImpl}} implementation. However, the URL provided is 
> valid and should not be filtered.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Closed] (SLING-8866) Add reporting info in the XSS Protection API bundle

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-8866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu closed SLING-8866.
---

> Add reporting info in the XSS Protection API bundle
> ---
>
> Key: SLING-8866
> URL: https://issues.apache.org/jira/browse/SLING-8866
> Project: Sling
>  Issue Type: Improvement
>  Components: XSS Protection API
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: XSS Protection API 2.2.0
>
>  Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> The XSS Protection API should be enhanced to provide some reporting about 
> invalid URLs in order to allow operators of a Sling instance to monitor the 
> state of the system (e.g. incorrect AntiSamy configurations, attacks, DOS 
> attempts, etc.).
> The following ideas should be taken into consideration:
> # add last X blocked expressions to the Sling XSS Web Console page
> # generate blocked metrics, based on configurable paths, e.g. {{/libs}}, 
> {{/apps}}, {{/content}}.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Closed] (SLING-9022) Update to latest OWASP AntiSamy, ESAPI, encoder Java libraries

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-9022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu closed SLING-9022.
---

> Update to latest OWASP AntiSamy, ESAPI, encoder Java libraries
> --
>
> Key: SLING-9022
> URL: https://issues.apache.org/jira/browse/SLING-9022
> Project: Sling
>  Issue Type: Improvement
>  Components: XSS Protection API
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: XSS Protection API 2.2.0
>
>
> The XSS Protection API is one release behind for both ESAPI and the AntiSamy 
> libraries.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Closed] (SLING-9023) Switch from legacy commons collections 3 to commons collections 4

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-9023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu closed SLING-9023.
---

> Switch from legacy commons collections 3 to commons collections 4
> -
>
> Key: SLING-9023
> URL: https://issues.apache.org/jira/browse/SLING-9023
> Project: Sling
>  Issue Type: Improvement
>  Components: XSS Protection API
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: XSS Protection API 2.2.0
>
>
> {{org.apache.sling.xss}} still uses the legacy commons collections 3 version. 
> It should be updated to use commons collections 4.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (SLING-5418) Display description about Metrics being collected in WebConsole Plugin

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-5418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu updated SLING-5418:

Fix Version/s: (was: Commons Metrics 1.2.8)
   Commons Metrics 1.2.10

> Display description about Metrics being collected in WebConsole Plugin
> --
>
> Key: SLING-5418
> URL: https://issues.apache.org/jira/browse/SLING-5418
> Project: Sling
>  Issue Type: Improvement
>  Components: Commons
>Reporter: Chetan Mehrotra
>Assignee: Chetan Mehrotra
>Priority: Minor
> Fix For: Commons Metrics 1.2.10
>
>
> Metrics webconsole plugin currently displays all metrics in tabular format. 
> It would be helpful if it can display some details about what metric data is 
> all about



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (SLING-9025) The MetricsService keeps stale metrics after bundles that have registered metrics are removed

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-9025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu resolved SLING-9025.
-
Resolution: Fixed

Fixed in [commit 
cf8b6bc|https://github.com/apache/sling-org-apache-sling-commons-metrics/commit/cf8b6bc].

> The MetricsService keeps stale metrics after bundles that have registered 
> metrics are removed
> -
>
> Key: SLING-9025
> URL: https://issues.apache.org/jira/browse/SLING-9025
> Project: Sling
>  Issue Type: Bug
>Affects Versions: Commons Metrics 1.0.0
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: Commons Metrics 1.2.8
>
>
> The {{MetricsService}} keeps stale metrics after bundles that have registered 
> metrics are removed. Although the respective metrics are removed from the 
> {{MetricsRegistry}}, the {{MetricsService}} internally caches the metrics and 
> does not remove them once metric mappings are removed.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (SLING-9025) The MetricsService keeps stale metrics after bundles that have registered metrics are removed

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-9025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu reassigned SLING-9025:
---

Assignee: Radu Cotescu

> The MetricsService keeps stale metrics after bundles that have registered 
> metrics are removed
> -
>
> Key: SLING-9025
> URL: https://issues.apache.org/jira/browse/SLING-9025
> Project: Sling
>  Issue Type: Bug
>Affects Versions: Commons Metrics 1.0.0
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: Commons Metrics 1.2.8
>
>
> The {{MetricsService}} keeps stale metrics after bundles that have registered 
> metrics are removed. Although the respective metrics are removed from the 
> {{MetricsRegistry}}, the {{MetricsService}} internally caches the metrics and 
> does not remove them once metric mappings are removed.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (SLING-9025) The MetricsService keeps stale metrics after bundles that have registered metrics are removed

[Radu Cotescu (Jira)]

Radu Cotescu created SLING-9025:
---

 Summary: The MetricsService keeps stale metrics after bundles that 
have registered metrics are removed
 Key: SLING-9025
 URL: https://issues.apache.org/jira/browse/SLING-9025
 Project: Sling
  Issue Type: Bug
Affects Versions: Commons Metrics 1.0.0
Reporter: Radu Cotescu
 Fix For: Commons Metrics 1.2.8


The {{MetricsService}} keeps stale metrics after bundles that have registered 
metrics are removed. Although the respective metrics are removed from the 
{{MetricsRegistry}}, the {{MetricsService}} internally caches the metrics and 
does not remove them once metric mappings are removed.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (SLING-7954) Switch from legacy commons collections 3 to commons collections 4

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-7954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu updated SLING-7954:

Description: 
The following bundles still use the legacy commons collections 3 version
 They should be updated to use commons collections 4
 com.composum.core.commons 
 org.apache.jackrabbit.jackrabbit-spi-commons 
 org.apache.jackrabbit.vault 
 org.apache.sling.models.jacksonexporter

  was:
The following bundles still use the legacy commons collections 3 version
They should be updated to use commons collections 4
com.composum.core.commons 
org.apache.jackrabbit.jackrabbit-spi-commons 
org.apache.jackrabbit.vault 
org.apache.sling.models.jacksonexporter
org.apache.sling.scripting.javascript 
org.apache.sling.xss 


> Switch from legacy commons collections 3 to commons collections 4
> -
>
> Key: SLING-7954
> URL: https://issues.apache.org/jira/browse/SLING-7954
> Project: Sling
>  Issue Type: Improvement
>Reporter: Carsten Ziegeler
>Priority: Major
> Fix For: Sling Models Jackson Exporter 1.0.10
>
>
> The following bundles still use the legacy commons collections 3 version
>  They should be updated to use commons collections 4
>  com.composum.core.commons 
>  org.apache.jackrabbit.jackrabbit-spi-commons 
>  org.apache.jackrabbit.vault 
>  org.apache.sling.models.jacksonexporter



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (SLING-7954) Switch from legacy commons collections 3 to commons collections 4

[Radu Cotescu (Jira)]

[ 
https://issues.apache.org/jira/browse/SLING-7954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17022045#comment-17022045
 ] 

Radu Cotescu commented on SLING-7954:
-

I've also created SLING-9023 for {{org.apache.sling.xss}} and linked it here.

> Switch from legacy commons collections 3 to commons collections 4
> -
>
> Key: SLING-7954
> URL: https://issues.apache.org/jira/browse/SLING-7954
> Project: Sling
>  Issue Type: Improvement
>Reporter: Carsten Ziegeler
>Priority: Major
> Fix For: Sling Models Jackson Exporter 1.0.10
>
>
> The following bundles still use the legacy commons collections 3 version
> They should be updated to use commons collections 4
> com.composum.core.commons 
> org.apache.jackrabbit.jackrabbit-spi-commons 
> org.apache.jackrabbit.vault 
> org.apache.sling.models.jacksonexporter
> org.apache.sling.scripting.javascript 
> org.apache.sling.xss 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (SLING-7954) Switch from legacy commons collections 3 to commons collections 4

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-7954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu updated SLING-7954:

Fix Version/s: (was: XSS Protection API 2.2.0)

> Switch from legacy commons collections 3 to commons collections 4
> -
>
> Key: SLING-7954
> URL: https://issues.apache.org/jira/browse/SLING-7954
> Project: Sling
>  Issue Type: Improvement
>Reporter: Carsten Ziegeler
>Priority: Major
> Fix For: Sling Models Jackson Exporter 1.0.10
>
>
> The following bundles still use the legacy commons collections 3 version
> They should be updated to use commons collections 4
> com.composum.core.commons 
> org.apache.jackrabbit.jackrabbit-spi-commons 
> org.apache.jackrabbit.vault 
> org.apache.sling.models.jacksonexporter
> org.apache.sling.scripting.javascript 
> org.apache.sling.xss 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (SLING-9022) Update to latest OWASP AntiSamy, ESAPI, encoder Java libraries

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-9022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu resolved SLING-9022.
-
Resolution: Fixed

Fixed in [commit 
d276bfd|https://github.com/apache/sling-org-apache-sling-xss/commit/d276bfd].

> Update to latest OWASP AntiSamy, ESAPI, encoder Java libraries
> --
>
> Key: SLING-9022
> URL: https://issues.apache.org/jira/browse/SLING-9022
> Project: Sling
>  Issue Type: Improvement
>  Components: XSS Protection API
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: XSS Protection API 2.2.0
>
>
> The XSS Protection API is one release behind for both ESAPI and the AntiSamy 
> libraries.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (SLING-9023) Switch from legacy commons collections 3 to commons collections 4

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-9023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu resolved SLING-9023.
-
Resolution: Fixed

Fixed in [commit 
8472d94|https://github.com/apache/sling-org-apache-sling-xss/commit/8472d94].

> Switch from legacy commons collections 3 to commons collections 4
> -
>
> Key: SLING-9023
> URL: https://issues.apache.org/jira/browse/SLING-9023
> Project: Sling
>  Issue Type: Improvement
>  Components: XSS Protection API
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: XSS Protection API 2.2.0
>
>
> {{org.apache.sling.xss}} still uses the legacy commons collections 3 version. 
> It should be updated to use commons collections 4.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (SLING-9023) Switch from legacy commons collections 3 to commons collections 4

[Radu Cotescu (Jira)]

Radu Cotescu created SLING-9023:
---

 Summary: Switch from legacy commons collections 3 to commons 
collections 4
 Key: SLING-9023
 URL: https://issues.apache.org/jira/browse/SLING-9023
 Project: Sling
  Issue Type: Improvement
  Components: XSS Protection API
Reporter: Radu Cotescu
Assignee: Radu Cotescu
 Fix For: XSS Protection API 2.2.0


{{org.apache.sling.xss}} still uses the legacy commons collections 3 version. 
It should be updated to use commons collections 4.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (SLING-9022) Update to latest OWASP AntiSamy, ESAPI, encoder Java libraries

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-9022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu updated SLING-9022:

Summary: Update to latest OWASP AntiSamy, ESAPI, encoder Java libraries  
(was: Update to latest OWASP AntiSamy and ESAPI Java libraries)

> Update to latest OWASP AntiSamy, ESAPI, encoder Java libraries
> --
>
> Key: SLING-9022
> URL: https://issues.apache.org/jira/browse/SLING-9022
> Project: Sling
>  Issue Type: Improvement
>  Components: XSS Protection API
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: XSS Protection API 2.2.0
>
>
> The XSS Protection API is one release behind for both ESAPI and the AntiSamy 
> libraries.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (SLING-9022) Update to latest OWASP AntiSamy and ESAPI Java libraries

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-9022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu reassigned SLING-9022:
---

Assignee: Radu Cotescu

> Update to latest OWASP AntiSamy and ESAPI Java libraries
> 
>
> Key: SLING-9022
> URL: https://issues.apache.org/jira/browse/SLING-9022
> Project: Sling
>  Issue Type: Improvement
>  Components: XSS Protection API
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: XSS Protection API 2.2.0
>
>
> The XSS Protection API is one release behind for both ESAPI and the AntiSamy 
> libraries.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (SLING-9022) Update to latest OWASP AntiSamy and ESAPI Java libraries

[Radu Cotescu (Jira)]

Radu Cotescu created SLING-9022:
---

 Summary: Update to latest OWASP AntiSamy and ESAPI Java libraries
 Key: SLING-9022
 URL: https://issues.apache.org/jira/browse/SLING-9022
 Project: Sling
  Issue Type: Improvement
  Components: XSS Protection API
Reporter: Radu Cotescu
 Fix For: XSS Protection API 2.2.0


The XSS Protection API is one release behind for both ESAPI and the AntiSamy 
libraries.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (SLING-9019) The XSSFilter will mark URLs containing both escaped characters and HTML entities as invalid

[Radu Cotescu (Jira)]

 [ 
https://issues.apache.org/jira/browse/SLING-9019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu resolved SLING-9019.
-
Resolution: Fixed

Fixed in [commit 
f8f046b|https://github.com/apache/sling-org-apache-sling-xss/commit/f8f046b].

> The XSSFilter will mark URLs containing both escaped characters and HTML 
> entities as invalid
> 
>
> Key: SLING-9019
> URL: https://issues.apache.org/jira/browse/SLING-9019
> Project: Sling
>  Issue Type: Bug
>  Components: XSS Protection API
>Affects Versions: XSS Protection API 2.0.4
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Major
> Fix For: XSS Protection API 2.2.0
>
>
> A URL similar to {{http://localhost/?q=a+br=1}} will be marked as 
> invalid by the {{XSSFilterImpl}} implementation. However, the URL provided is 
> valid and should not be filtered.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)