[jira] [Created] (SLING-12179) Make i18n optional
Karl Pauls created SLING-12179: -- Summary: Make i18n optional Key: SLING-12179 URL: https://issues.apache.org/jira/browse/SLING-12179 Project: Sling Issue Type: Improvement Components: Scripting Affects Versions: Scripting HTL Engine 1.4.22-1.4.0 Reporter: Karl Pauls Assignee: Karl Pauls Fix For: Scripting HTL Engine 1.4.24-1.4.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (SLING-12178) Make commons metrics optional in xss bundle
[ https://issues.apache.org/jira/browse/SLING-12178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls resolved SLING-12178. Resolution: Fixed Done in https://github.com/apache/sling-org-apache-sling-xss/pull/41 > Make commons metrics optional in xss bundle > --- > > Key: SLING-12178 > URL: https://issues.apache.org/jira/browse/SLING-12178 > Project: Sling > Issue Type: Improvement > Components: XSS Protection API >Affects Versions: XSS Protection API 2.4.0 >Reporter: Karl Pauls >Assignee: Karl Pauls >Priority: Major > Fix For: XSS Protection API 2.4.2 > > > Following the pattern we use in the other bundles, it would be good if the > sling metrics would be optional for the xss bundle. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (SLING-12178) Make commons metrics optional in xss bundle
Karl Pauls created SLING-12178: -- Summary: Make commons metrics optional in xss bundle Key: SLING-12178 URL: https://issues.apache.org/jira/browse/SLING-12178 Project: Sling Issue Type: Improvement Components: XSS Protection API Affects Versions: XSS Protection API 2.4.0 Reporter: Karl Pauls Assignee: Karl Pauls Fix For: XSS Protection API 2.4.2 Following the pattern we use in the other bundles, it would be good if the sling metrics would be optional for the xss bundle. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (SLING-12057) Replace commons.threads with Executor
[ https://issues.apache.org/jira/browse/SLING-12057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls resolved SLING-12057. Resolution: Fixed > Replace commons.threads with Executor > - > > Key: SLING-12057 > URL: https://issues.apache.org/jira/browse/SLING-12057 > Project: Sling > Issue Type: Improvement > Components: Scripting >Affects Versions: Scripting Core 2.4.8 >Reporter: Carsten Ziegeler >Assignee: Karl Pauls >Priority: Major > Fix For: Scripting Core 2.4.10 > > > In order to minimize dependencies for core Sling, we could replace usage of > the commons.threads (which is not used in any other core bundle) with > Executor api > [~radu] WDYT? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (SLING-12057) Replace commons.threads with Executor
[ https://issues.apache.org/jira/browse/SLING-12057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls reassigned SLING-12057: -- Assignee: Karl Pauls > Replace commons.threads with Executor > - > > Key: SLING-12057 > URL: https://issues.apache.org/jira/browse/SLING-12057 > Project: Sling > Issue Type: Improvement > Components: Scripting >Affects Versions: Scripting Core 2.4.8 >Reporter: Carsten Ziegeler >Assignee: Karl Pauls >Priority: Major > Fix For: Scripting Core 2.4.10 > > > In order to minimize dependencies for core Sling, we could replace usage of > the commons.threads (which is not used in any other core bundle) with > Executor api > [~radu] WDYT? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (SLING-11630) Feature model IOUtils should not use caches for jar files from jar url connection
[ https://issues.apache.org/jira/browse/SLING-11630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls resolved SLING-11630. Resolution: Fixed Done in https://github.com/apache/sling-org-apache-sling-feature/pull/31 > Feature model IOUtils should not use caches for jar files from jar url > connection > - > > Key: SLING-11630 > URL: https://issues.apache.org/jira/browse/SLING-11630 > Project: Sling > Issue Type: Bug > Components: Feature Model >Affects Versions: Feature Model 1.2.30 >Reporter: Karl Pauls >Assignee: Karl Pauls >Priority: Major > Fix For: Feature Model 1.3.0 > > > The JarUrlConnection is set to use caches for JarFiles by default. That is a > problem because if there is more than one connection for the same JarFile and > the connection is going away, it will close the JarFile - potentially causing > the users of the JarFile from the other (still open) connection with a closed > JarFile. > To work around this problem, the IOUtils should set use caches to false on > the connections it creates. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (SLING-11630) Feature model IOUtils should not use caches for jar files from jar url connection
Karl Pauls created SLING-11630: -- Summary: Feature model IOUtils should not use caches for jar files from jar url connection Key: SLING-11630 URL: https://issues.apache.org/jira/browse/SLING-11630 Project: Sling Issue Type: Bug Components: Feature Model Affects Versions: Feature Model 1.2.30 Reporter: Karl Pauls Assignee: Karl Pauls Fix For: Feature Model 1.3.0 The JarUrlConnection is set to use caches for JarFiles by default. That is a problem because if there is more than one connection for the same JarFile and the connection is going away, it will close the JarFile - potentially causing the users of the JarFile from the other (still open) connection with a closed JarFile. To work around this problem, the IOUtils should set use caches to false on the connections it creates. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (SLING-11373) The MergingServletResourceProvider does not wrap resources correctly
[
https://issues.apache.org/jira/browse/SLING-11373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Pauls resolved SLING-11373.
Resolution: Fixed
> The MergingServletResourceProvider does not wrap resources correctly
>
>
> Key: SLING-11373
> URL: https://issues.apache.org/jira/browse/SLING-11373
> Project: Sling
> Issue Type: Bug
> Components: Servlets
>Affects Versions: Servlets Resolver 2.7.0
>Reporter: Radu Cotescu
>Assignee: Karl Pauls
>Priority: Major
> Fix For: Servlets Resolver 2.9.8
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> The {{MergingServletResourceProvider}} does not wrap resources correctly,
> forcing script engines that need to solve dependencies via this provider to
> call {{ResourceResolver#resolve(String)}}. Unfortunately, there is a case
> when the call to {{resolve}} fails:
> {noformat}
> /apps/components/a/
> a.html
> helper.something.html
> helper/ [backed by JCR]
> partial.html
> /apps/components/b [sling:resourceSuperType=components/a]
> b.html -> tries to resolve helper.something.html
> {noformat}
> In the case above, {{b.html}} will get the {{helper}} folder when trying to
> resolve {{helper.something.html}}.
> If the {{MergingServletResourceProvider}} would correctly wrap resources (and
> decorate them accordingly), the script engines could switch to using
> {{ResourceResolver#getResource(String)}}, which would not exhibit the same
> behaviour.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (SLING-11373) The MergingServletResourceProvider does not wrap resources correctly
[
https://issues.apache.org/jira/browse/SLING-11373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17566744#comment-17566744
]
Karl Pauls commented on SLING-11373:
With the new passthrough mode from [~cziegeler] (many thanks), it seems like
the best option to just use that one.
I added a {{mountPathProviders}} option in [0] which overrides the
{{mountProviders}} option if enabled. That should fix the issue the right way
and we can eventually deprecated the {{mountProviders}} option altogether.
[0] https://github.com/apache/sling-org-apache-sling-servlets-resolver/pull/30
> The MergingServletResourceProvider does not wrap resources correctly
>
>
> Key: SLING-11373
> URL: https://issues.apache.org/jira/browse/SLING-11373
> Project: Sling
> Issue Type: Bug
> Components: Servlets
>Affects Versions: Servlets Resolver 2.7.0
>Reporter: Radu Cotescu
>Assignee: Karl Pauls
>Priority: Major
> Fix For: Servlets Resolver 2.9.8
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> The {{MergingServletResourceProvider}} does not wrap resources correctly,
> forcing script engines that need to solve dependencies via this provider to
> call {{ResourceResolver#resolve(String)}}. Unfortunately, there is a case
> when the call to {{resolve}} fails:
> {noformat}
> /apps/components/a/
> a.html
> helper.something.html
> helper/ [backed by JCR]
> partial.html
> /apps/components/b [sling:resourceSuperType=components/a]
> b.html -> tries to resolve helper.something.html
> {noformat}
> In the case above, {{b.html}} will get the {{helper}} folder when trying to
> resolve {{helper.something.html}}.
> If the {{MergingServletResourceProvider}} would correctly wrap resources (and
> decorate them accordingly), the script engines could switch to using
> {{ResourceResolver#getResource(String)}}, which would not exhibit the same
> behaviour.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (SLING-11438) Resource path consisting of %7D with multiple dots leads to path traversal
[ https://issues.apache.org/jira/browse/SLING-11438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls updated SLING-11438: --- Fix Version/s: Engine 2.9.2 > Resource path consisting of %7D with multiple dots leads to path traversal > -- > > Key: SLING-11438 > URL: https://issues.apache.org/jira/browse/SLING-11438 > Project: Sling > Issue Type: Bug > Components: Engine >Affects Versions: Engine 2.9.0 >Reporter: Sagar Miglani >Assignee: Karl Pauls >Priority: Major > Fix For: Engine 2.9.2 > > Time Spent: 2h 10m > Remaining Estimate: 0h > > With changes of SLING-10225, sling-engine started considering requests > consisting of resource path with %5B ([) and multiple dots as "Invalid", as > it could lead to path traversal and exposure of repository content. > But same could happen with %7D (}) with multiple dots in the request resource > path. > e.g: > http://:/content/we-retail/us/en/experience.html/.%7D./.%7D./.1.json > would lead to exposure of repository content stored at /content/we-retail/us -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (SLING-11438) Resource path consisting of %7D with multiple dots leads to path traversal
[ https://issues.apache.org/jira/browse/SLING-11438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls reassigned SLING-11438: -- Assignee: Karl Pauls > Resource path consisting of %7D with multiple dots leads to path traversal > -- > > Key: SLING-11438 > URL: https://issues.apache.org/jira/browse/SLING-11438 > Project: Sling > Issue Type: Bug > Components: Engine >Affects Versions: Engine 2.9.0 >Reporter: Sagar Miglani >Assignee: Karl Pauls >Priority: Major > Time Spent: 2h 10m > Remaining Estimate: 0h > > With changes of SLING-10225, sling-engine started considering requests > consisting of resource path with %5B ([) and multiple dots as "Invalid", as > it could lead to path traversal and exposure of repository content. > But same could happen with %7D (}) with multiple dots in the request resource > path. > e.g: > http://:/content/we-retail/us/en/experience.html/.%7D./.%7D./.1.json > would lead to exposure of repository content stored at /content/we-retail/us -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (SLING-11438) Resource path consisting of %7D with multiple dots leads to path traversal
[ https://issues.apache.org/jira/browse/SLING-11438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls resolved SLING-11438. Resolution: Fixed Thanks a lot [~sagarmiglani], I merged your PR. > Resource path consisting of %7D with multiple dots leads to path traversal > -- > > Key: SLING-11438 > URL: https://issues.apache.org/jira/browse/SLING-11438 > Project: Sling > Issue Type: Bug > Components: Engine >Affects Versions: Engine 2.9.0 >Reporter: Sagar Miglani >Assignee: Karl Pauls >Priority: Major > Time Spent: 2h 10m > Remaining Estimate: 0h > > With changes of SLING-10225, sling-engine started considering requests > consisting of resource path with %5B ([) and multiple dots as "Invalid", as > it could lead to path traversal and exposure of repository content. > But same could happen with %7D (}) with multiple dots in the request resource > path. > e.g: > http://:/content/we-retail/us/en/experience.html/.%7D./.%7D./.1.json > would lead to exposure of repository content stored at /content/we-retail/us -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (SLING-11158) The starter's "Start Sling" instructions don't work with feature launcher v1.1.28 or later
[
https://issues.apache.org/jira/browse/SLING-11158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17508871#comment-17508871
]
Karl Pauls commented on SLING-11158:
Yeah, the additional problem is that it gets worse with more than one extension
because they might have their own dependencies. For a while, we tried to work
with embedding and shading everything but that becomes a mess so we gave up and
just have to manage the class path of the launcher - at which point it is
better if it brings its dependencies as well.
> The starter's "Start Sling" instructions don't work with feature launcher
> v1.1.28 or later
> --
>
> Key: SLING-11158
> URL: https://issues.apache.org/jira/browse/SLING-11158
> Project: Sling
> Issue Type: Bug
>Affects Versions: Feature Model Launcher 1.1.28, Feature Model Launcher
> 1.2.0
>Reporter: Eric Norman
>Priority: Major
> Fix For: Feature Launcher Maven Plugin 0.1.4, Starter 13
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> After the SLING-10956 changes, launching the Starter with the README provided
> instructions while using the v1.1.28 or later feature launcher does not work
> anymore.
> For example,
> {noformat}
> $ java -jar target/dependency/org.apache.sling.feature.launcher.jar -f
> target/slingfeature-tmp/feature-oak_tar.json
> Error: Unable to initialize main class
> org.apache.sling.feature.launcher.impl.Main
> Caused by: java.lang.NoClassDefFoundError:
> org/apache/commons/cli/ParseException{noformat}
>
> Also, the start goal of the feature-launcher-maven-plugin fails with the same
> exception when paired with a featureLauncherVersion of 1.1.28 or later.
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Closed] (SLING-10858) Incorrect API Regions generated in features
[
https://issues.apache.org/jira/browse/SLING-10858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Pauls closed SLING-10858.
--
> Incorrect API Regions generated in features
> ---
>
> Key: SLING-10858
> URL: https://issues.apache.org/jira/browse/SLING-10858
> Project: Sling
> Issue Type: Bug
> Components: Content-Package to Feature Model Converter
>Affects Versions: Content-Package to Feature Model Converter 1.1.6
>Reporter: A. J. David Bosschaert
>Assignee: Karl Pauls
>Priority: Major
> Fix For: Content-Package to Feature Model Converter 1.1.12
>
>
> In some cases the cpconverter generates an {{api-regions}} section with
> {{global}} exports for packages, where the bundles providing those packages
> are not actually listed in the feature. I have seen features with _no_
> bundles (just some configuration) and an {{api-regions}} section with lots of
> exports, which clearly couldn't be satisfied by the feature as it did not
> have any bundles at all.
> I believe that this might be caused by the fact that the
> DefaultFeaturesManager has the an apiRegionsExports field
> https://github.com/apache/sling-org-apache-sling-feature-cpconverter/blob/master/src/main/java/org/apache/sling/feature/cpconverter/features/DefaultFeaturesManager.java#L101
> which is not cleared between features being processed, and as such the
> api-regions exports are bleeding between generated features.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Closed] (SLING-10921) Converter creates dependencies for extracted content that are wrong when the provider is around in more than one run mode
[ https://issues.apache.org/jira/browse/SLING-10921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls closed SLING-10921. -- > Converter creates dependencies for extracted content that are wrong when the > provider is around in more than one run mode > - > > Key: SLING-10921 > URL: https://issues.apache.org/jira/browse/SLING-10921 > Project: Sling > Issue Type: Bug > Components: Content-Package to Feature Model Converter >Affects Versions: Content-Package to Feature Model Converter 1.1.10 >Reporter: Karl Pauls >Assignee: Karl Pauls >Priority: Major > Fix For: Content-Package to Feature Model Converter 1.1.12 > > > When the converter extracts content from bundles it does that again every > time it hits the bundle (assuming it is present in different > locations/runmodes/packages). That is a problem as this way, only the last > location will be added as a dependency to the package - causing it to fail to > install if it was used from one of the other locations. > We should just not generate a dependency, like we do with contain packages. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-10920) Converter doesn't reset the aclManager after first pass and rejects too much after resets
[ https://issues.apache.org/jira/browse/SLING-10920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls closed SLING-10920. -- > Converter doesn't reset the aclManager after first pass and rejects too much > after resets > - > > Key: SLING-10920 > URL: https://issues.apache.org/jira/browse/SLING-10920 > Project: Sling > Issue Type: Bug > Components: Content-Package to Feature Model Converter >Affects Versions: Content-Package to Feature Model Converter 1.1.10 >Reporter: Karl Pauls >Assignee: Karl Pauls >Priority: Major > Fix For: Content-Package to Feature Model Converter 1.1.12 > > > The converter doesn't reset the acl manager after the first pass. That makes > it so that the service users are collected and put into the all feature. > Furthermore, if it resets, it is loosing the acls that have matching service > users but that come too later in the contenpackage. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-10929) CPConverter - error messages can be obfuscated
[ https://issues.apache.org/jira/browse/SLING-10929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls closed SLING-10929. -- > CPConverter - error messages can be obfuscated > -- > > Key: SLING-10929 > URL: https://issues.apache.org/jira/browse/SLING-10929 > Project: Sling > Issue Type: Improvement > Components: Content-Package to Feature Model Converter >Affects Versions: Content-Package to Feature Model Converter 1.1.10 >Reporter: Niek Raaijmakers >Assignee: Niek Raaijmakers >Priority: Minor > Fix For: Content-Package to Feature Model Converter 1.1.12 > > > Currently, when performing a CPConversion, if the customer has wrong code, > sometimes the exception can be very obfuscated. > This gives the customer no chance to fix their error easily: > In this example a xml file is empty: > [ERROR] Unable to convert content-package > [/tmp/packages/???.ui.content-1.28.0-SNAPSHOT.zip, > /tmp/packages/???.ui.apps-1.28.0-SNAPSHOT.zip]: Premature end of file. > We would like a path to be provided in the exception so the customer can take > a look there. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-10933) Content package converter should use QUOTE_TICK option when parsing json
[ https://issues.apache.org/jira/browse/SLING-10933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls closed SLING-10933. -- > Content package converter should use QUOTE_TICK option when parsing json > > > Key: SLING-10933 > URL: https://issues.apache.org/jira/browse/SLING-10933 > Project: Sling > Issue Type: Improvement > Components: Content-Package to Feature Model Converter >Affects Versions: Content-Package to Feature Model Converter 1.1.10 >Reporter: Karl Pauls >Assignee: Karl Pauls >Priority: Major > Fix For: Content-Package to Feature Model Converter 1.1.12 > > > The converter should use the QUOTE_TICK options when parsing json to force > UTF-8 charset and allow for slightly malformed json files (where quote ticks > are used instead of string quotes). -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-11152) Use official OSGi Converter Implementation
[ https://issues.apache.org/jira/browse/SLING-11152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls closed SLING-11152. -- > Use official OSGi Converter Implementation > -- > > Key: SLING-11152 > URL: https://issues.apache.org/jira/browse/SLING-11152 > Project: Sling > Issue Type: Improvement > Components: Feature Model >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler >Priority: Major > Fix For: Content Distribution Journal Core 0.1.24, Feature Model > Converter 1.0.16, Slingstart Maven Plugin 1.9.14, Settings 1.4.2, > Content-Package to Feature Model Converter 1.1.12, Models Implementation > 1.5.2, Feature Model Launcher 1.2.2, Feature Model Analyser 1.6.2, Adapter > 2.2.2, Feature Model 1.3.0, slingfeature-maven-plugin 1.6.2 > > > The Apache Felix implementation of the OSGi Converter has been retired in > favour of the one provided by OSGi. We should update to the latest version -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-11058) CPConverter - sling initial content - check illegal xml chars
[ https://issues.apache.org/jira/browse/SLING-11058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls closed SLING-11058. -- > CPConverter - sling initial content - check illegal xml chars > - > > Key: SLING-11058 > URL: https://issues.apache.org/jira/browse/SLING-11058 > Project: Sling > Issue Type: Bug > Components: Content-Package to Feature Model Converter >Affects Versions: Content-Package to Feature Model Converter 1.1.10 >Reporter: Niek Raaijmakers >Assignee: Niek Raaijmakers >Priority: Major > Fix For: Content-Package to Feature Model Converter 1.1.12 > > > We have to make sure that in the case of XML illegal characters being used in > JSON descriptor files for sling initial contrent, such as <, >, " and ', > these do not break the build in the cpconverter. > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-11059) CPConverter - sling initial content - XSLT support
[ https://issues.apache.org/jira/browse/SLING-11059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls closed SLING-11059. -- > CPConverter - sling initial content - XSLT support > -- > > Key: SLING-11059 > URL: https://issues.apache.org/jira/browse/SLING-11059 > Project: Sling > Issue Type: Bug > Components: Content-Package to Feature Model Converter >Affects Versions: Content-Package to Feature Model Converter 1.1.10 >Reporter: Niek Raaijmakers >Assignee: Niek Raaijmakers >Priority: Major > Fix For: Content-Package to Feature Model Converter 1.1.12 > > > In the sling initial content specs, XLST is supported: > [https://sling.apache.org/documentation/bundles/content-loading-jcr-contentloader.html#using-a-custom-xml-format] > Currently in the CPConverter, this is not supported yet, so we need to > implement this. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-10822) Avoid duplicate parsing of configuration pid
[ https://issues.apache.org/jira/browse/SLING-10822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls closed SLING-10822. -- > Avoid duplicate parsing of configuration pid > > > Key: SLING-10822 > URL: https://issues.apache.org/jira/browse/SLING-10822 > Project: Sling > Issue Type: Improvement > Components: Content-Package to Feature Model Converter >Affects Versions: Content-Package to Feature Model Converter 1.1.10 >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler >Priority: Major > Fix For: Content-Package to Feature Model Converter 1.1.12 > > > There is some duplicated logic to detect whether a configuration pid is a > factory pid. This can be reduced to a single place -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-10823) Pass in repoinit as a single text
[ https://issues.apache.org/jira/browse/SLING-10823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls closed SLING-10823. -- > Pass in repoinit as a single text > - > > Key: SLING-10823 > URL: https://issues.apache.org/jira/browse/SLING-10823 > Project: Sling > Issue Type: Improvement > Components: Content-Package to Feature Model Converter >Affects Versions: Content-Package to Feature Model Converter 1.1.10 >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler >Priority: Major > Fix For: Content-Package to Feature Model Converter 1.1.12 > > > When an OSGi configuration contains repoinit, each value of the scripts array > is handled separated. However sometimes a whole script is not passed in as a > single value in the array but as an array of strings. > So it is better to first append all values from the string array and handle > them as a single script -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-10917) Exclude filters in converted content packages can have a trailing slash
[ https://issues.apache.org/jira/browse/SLING-10917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls closed SLING-10917. -- > Exclude filters in converted content packages can have a trailing slash > --- > > Key: SLING-10917 > URL: https://issues.apache.org/jira/browse/SLING-10917 > Project: Sling > Issue Type: Bug > Components: Content-Package to Feature Model Converter >Affects Versions: Content-Package to Feature Model Converter 1.1.10 >Reporter: Karl Pauls >Assignee: Karl Pauls >Priority: Major > Fix For: Content-Package to Feature Model Converter 1.1.12 > > > The filter excludes we generate can have an extra slash at the end that is > not correct. This is effectively just and off by one in case a content.xml > has been removed and should be excluded. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-11191) Update repo-init parser dependency to 1.6.14
[ https://issues.apache.org/jira/browse/SLING-11191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls closed SLING-11191. -- > Update repo-init parser dependency to 1.6.14 > > > Key: SLING-11191 > URL: https://issues.apache.org/jira/browse/SLING-11191 > Project: Sling > Issue Type: Task > Components: Content-Package to Feature Model Converter >Affects Versions: Content-Package to Feature Model Converter 1.1.10 >Reporter: Angela Schreiber >Assignee: Angela Schreiber >Priority: Major > Fix For: Content-Package to Feature Model Converter 1.1.12 > > > [~kpauls], as discussed we also need to update the cp-2-fm-converter to use > the latest repoinit parser 1.6.14. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-11075) Maven id for bundles that don't have a GAV can end up not being well formed
[ https://issues.apache.org/jira/browse/SLING-11075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls closed SLING-11075. -- > Maven id for bundles that don't have a GAV can end up not being well formed > --- > > Key: SLING-11075 > URL: https://issues.apache.org/jira/browse/SLING-11075 > Project: Sling > Issue Type: Bug > Components: Feature Model >Affects Versions: Content-Package to Feature Model Converter 1.1.10 >Reporter: Karl Pauls >Assignee: Karl Pauls >Priority: Major > Fix For: Content-Package to Feature Model Converter 1.1.12 > > > When the converter finds a bundle, it tries to determine the maven > coordinates for it by looking at the embedded maven info. If there is none, > it tries to guess it from the maven info path. If that fails, it takes the > bsn and derives the info from it. > That works, however, in the case of a bsn, it doesn't strip attributes which > can cause an invalid mvn id in the end (e.g., if the bsn has a > ;singelton:=true) -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-10770) JcrNamespaceRegistry.registerCnd throws NPE
[
https://issues.apache.org/jira/browse/SLING-10770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Pauls closed SLING-10770.
--
> JcrNamespaceRegistry.registerCnd throws NPE
> ---
>
> Key: SLING-10770
> URL: https://issues.apache.org/jira/browse/SLING-10770
> Project: Sling
> Issue Type: Bug
> Components: Content-Package to Feature Model Converter
>Reporter: Angela Schreiber
>Assignee: Niek Raaijmakers
>Priority: Major
> Fix For: Content-Package to Feature Model Converter 1.1.12
>
>
> [~karlpauls], while trying to fix some sonar findings in the converter I came
> across a warning about a null {{NodeTypeManager}} being passed to
> {{CndImporter.registerNodeTypes}} in the following new method introduced with
> SLING-10243:
> {code}
> public void registerCnd(Reader reader, String systemId) throws
> ParseException, RepositoryException, IOException {
> NodeTypeManager ntManager = null;
> ValueFactory valueFactory = null;
> CndImporter.registerNodeTypes(reader, systemId, ntManager, this,
> valueFactory, false);
> registeredCndSystemIds.add(systemId);
> }
> {code}
> a simple test shows that the method always fails with NPE.
> so, unless i am missing something that code calling this method doesn't work
> at all. according to
> https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-feature-cpconverter=uncovered_conditions=apache_sling-org-apache-sling-feature-cpconverter%3Asrc%2Fmain%2Fjava%2Forg%2Fapache%2Fsling%2Ffeature%2Fcpconverter%2Fvltpkg%2FJcrNamespaceRegistry.java=list
> the method isn't covered with any tests either so that might explain why
> it has not been spotted before.
> what would be the best approach to get this fixed? should we revert changes
> made with SLING-10243? There is most probably no instance of JCR
> {{NodeTypeManager}} available if there is no JCR repository available at the
> stage the converter is being executed and I don't think mocking it at this
> stage is sensible.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Closed] (SLING-11072) Introduce command line argument for CPConverter to toggle the use of source package type for package type calculation.
[ https://issues.apache.org/jira/browse/SLING-11072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls closed SLING-11072. -- > Introduce command line argument for CPConverter to toggle the use of source > package type for package type calculation. > -- > > Key: SLING-11072 > URL: https://issues.apache.org/jira/browse/SLING-11072 > Project: Sling > Issue Type: Bug > Components: Content-Package to Feature Model Converter >Affects Versions: Content-Package to Feature Model Converter 1.1.10 >Reporter: Niek Raaijmakers >Assignee: Niek Raaijmakers >Priority: Minor > Fix For: Content-Package to Feature Model Converter 1.1.12 > > > We need to introduce a command line argument in the CPConverter. > The toggle should enables us to use the source package type when determining > package types of generated content packages. It should be on by default. > > We can then disable / overrule this by passing in false from the command line. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-10931) CPConverter - Sling initial content - json files should be converted to folders with a content xml in any case to avoid conflicts
[ https://issues.apache.org/jira/browse/SLING-10931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls closed SLING-10931. -- > CPConverter - Sling initial content - json files should be converted to > folders with a content xml in any case to avoid conflicts > - > > Key: SLING-10931 > URL: https://issues.apache.org/jira/browse/SLING-10931 > Project: Sling > Issue Type: Bug > Components: Content-Package to Feature Model Converter >Affects Versions: Content-Package to Feature Model Converter 1.1.10 >Reporter: Niek Raaijmakers >Assignee: Niek Raaijmakers >Priority: Major > Fix For: Content-Package to Feature Model Converter 1.1.12 > > > In case of converting sling initial content containing JSON files over to > xml, currently the cpconverter simply creates a xml file in the same level. > The problem is when there are other files in a directory with the same name > to go along the resourceType. > For example we have: > > * page.json > * page/body.html > * page/footer.html > > The result will be: > * page.xml > * page/body.html > * page/footer.html > > Vault doesn't like this approach so much, resulting in stuff like: > * page.dir > * page.xml > * page/.content.xml (with resourceType nt:folder) > * page/body.html > * page/footer.html > The solution lies in simply redirecting the output to .content.xml in a new > folder: > * page/.content.xml > * page/body.html > * page/footer.html > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-10818) Add origin information to repoinit
[ https://issues.apache.org/jira/browse/SLING-10818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls closed SLING-10818. -- > Add origin information to repoinit > -- > > Key: SLING-10818 > URL: https://issues.apache.org/jira/browse/SLING-10818 > Project: Sling > Issue Type: Improvement > Components: Content-Package to Feature Model Converter >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler >Priority: Major > Fix For: Content-Package to Feature Model Converter 1.1.12 > > > OSGi configurations are converted to repoinit instructions, resulting in a > single long repoinit text - if there is any error in those instructions like > a syntax error, later on it is hard to find the origin of that faulty > repoinit. > The converter could add a comment above every repoinit it appends containing > the origin information (package id and config id) -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-10859) runmode.mapping file does not contain all needed values
[
https://issues.apache.org/jira/browse/SLING-10859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Pauls closed SLING-10859.
--
> runmode.mapping file does not contain all needed values
> ---
>
> Key: SLING-10859
> URL: https://issues.apache.org/jira/browse/SLING-10859
> Project: Sling
> Issue Type: Bug
> Components: Content-Package to Feature Model Converter
>Affects Versions: Content-Package to Feature Model Converter 1.1.6
>Reporter: A. J. David Bosschaert
>Assignee: Carsten Ziegeler
>Priority: Major
> Fix For: Content-Package to Feature Model Converter 1.1.12
>
>
> In some cases the {{runmode.mapping}} file generated by the cpconverter does
> not contain all the required file (feature model) references.
> This can happen when certain filenames that need to be referenced are a
> substring of other file names.
> It centers around this code:
> https://github.com/apache/sling-org-apache-sling-feature-cpconverter/blob/master/src/main/java/org/apache/sling/feature/cpconverter/features/RunmodeMapper.java#L63-L67
> Assume that {{properties}} contains an entry
> {{(default)=>my-webapp-all.json}}. Then next a feature file named
> {{all.json}} is processed. As the name of it is a substring of the
> pre-existing value it will not append. In fact it will replace the previous
> value with the new value and as such remove it.
> The logic there should be fixed to not use substrings, but rather compare
> entire names. Possibly a better idea would be to keep a Set
> internally and convert that to a comma-separated list only once the
> Properties are persisted in the {{save(()}} call.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (SLING-11134) Extract Oak index definitions and package them as an additional file
[ https://issues.apache.org/jira/browse/SLING-11134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls updated SLING-11134: --- Fix Version/s: Content-Package to Feature Model Converter 1.1.14 Content-Package to Feature Model Converter 1.1.14 (was: Content-Package to Feature Model Converter 1.1.12) > Extract Oak index definitions and package them as an additional file > > > Key: SLING-11134 > URL: https://issues.apache.org/jira/browse/SLING-11134 > Project: Sling > Issue Type: New Feature > Components: Content-Package to Feature Model Converter >Reporter: Robert Munteanu >Assignee: Robert Munteanu >Priority: Major > Fix For: Content-Package to Feature Model Converter 1.1.14 > > > It is sometimes useful to read the Oak index definitions from the content > package and package them as an additional file ( in JSON format? ) so they > can be more easily consumed by downstream tools that need to know the index > definitions. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (SLING-10774) Fix sonar findings in content-package to feature model converter
[ https://issues.apache.org/jira/browse/SLING-10774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls updated SLING-10774: --- Fix Version/s: Content-Package to Feature Model Converter 1.1.14 Content-Package to Feature Model Converter 1.1.14 (was: Content-Package to Feature Model Converter 1.1.12) > Fix sonar findings in content-package to feature model converter > > > Key: SLING-10774 > URL: https://issues.apache.org/jira/browse/SLING-10774 > Project: Sling > Issue Type: Improvement > Components: Content-Package to Feature Model Converter >Reporter: Angela Schreiber >Priority: Major > Fix For: Content-Package to Feature Model Converter 1.1.14 > > > sonar reports quite some findings for the content-package to feature model > converter bundle that are easy to fix preventing broken window syndrome i > would suggest to keep fixing as much as possible. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (SLING-10861) Subpackages are missing dependency on their container
[ https://issues.apache.org/jira/browse/SLING-10861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls updated SLING-10861: --- Fix Version/s: Content-Package to Feature Model Converter 1.1.14 Content-Package to Feature Model Converter 1.1.14 (was: Content-Package to Feature Model Converter 1.1.12) > Subpackages are missing dependency on their container > - > > Key: SLING-10861 > URL: https://issues.apache.org/jira/browse/SLING-10861 > Project: Sling > Issue Type: Bug > Components: Content-Package to Feature Model Converter >Affects Versions: Content-Package to Feature Model Converter 1.1.10 >Reporter: Karl Pauls >Priority: Major > Fix For: Content-Package to Feature Model Converter 1.1.14 > > > When the converter is extracting sub packages it is not adding a dependency > to their containing package to them. It does for embedded packages but not > for subpackages. It should add a dependency in both cases. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (SLING-10779) ContentPackage2FeatureModelConverter.getAclManager should never return null
[
https://issues.apache.org/jira/browse/SLING-10779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Pauls updated SLING-10779:
---
Fix Version/s: Content-Package to Feature Model Converter 1.1.14
Content-Package to Feature Model Converter 1.1.14
(was: Content-Package to Feature Model Converter 1.1.12)
> ContentPackage2FeatureModelConverter.getAclManager should never return null
> ---
>
> Key: SLING-10779
> URL: https://issues.apache.org/jira/browse/SLING-10779
> Project: Sling
> Issue Type: Improvement
> Components: Content-Package to Feature Model Converter
>Reporter: Angela Schreiber
>Priority: Minor
> Fix For: Content-Package to Feature Model Converter 1.1.14
>
>
> {{ContentPackage2FeatureModelConverter.getAclManager}} is used across the
> converter code base and always expected to be not-null. so, instead of
> defining it as 'nullable' we should find ways to make sure it is always
> present on the converter. this would allow to get rid of
> Objects.requireNotNull and the warnings about potential NPE where the check
> is missing.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (SLING-10571) Hardcoded application paths in VaultPackageUtils.detectPackageType
[
https://issues.apache.org/jira/browse/SLING-10571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Pauls updated SLING-10571:
---
Fix Version/s: Content-Package to Feature Model Converter 1.1.14
Content-Package to Feature Model Converter 1.1.14
(was: Content-Package to Feature Model Converter 1.1.12)
> Hardcoded application paths in VaultPackageUtils.detectPackageType
> --
>
> Key: SLING-10571
> URL: https://issues.apache.org/jira/browse/SLING-10571
> Project: Sling
> Issue Type: Bug
> Components: Content-Package to Feature Model Converter
>Reporter: Angela Schreiber
>Priority: Minor
> Labels: technical_debt
> Fix For: Content-Package to Feature Model Converter 1.1.14
>
>
> while investigating SLING-10467 i noticed hardcoded paths for what should be
> considered application content in {{VaultPackageUtils.detectPackageType}}.
> the method looks as follows:
> {code}
> public static @NotNull PackageType detectPackageType(String path) {
> if ("/apps".equals(path)
> || path.startsWith("/apps/")
> || "/libs".equals(path)
> || path.startsWith("/libs/")) {
> return PackageType.APPLICATION;
> } else {
> return PackageType.CONTENT;
> }
> }
> {code}
> instead of hardcoding /apps and /libs which are details of Adobe AEM, these
> paths should be configured with the converter-launcher. in particular since
> the list looks a bit arbitrary as there are other paths that IMHO should be
> considered application content like nodetype registry, namespace registry,
> privilege registry, service users etc.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (SLING-10768) AbstractJcrNodeParser and subclasses ignore namespace mappings
[
https://issues.apache.org/jira/browse/SLING-10768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Pauls updated SLING-10768:
---
Fix Version/s: Content-Package to Feature Model Converter 1.1.14
Content-Package to Feature Model Converter 1.1.14
(was: Content-Package to Feature Model Converter 1.1.12)
> AbstractJcrNodeParser and subclasses ignore namespace mappings
> --
>
> Key: SLING-10768
> URL: https://issues.apache.org/jira/browse/SLING-10768
> Project: Sling
> Issue Type: Improvement
> Components: Content-Package to Feature Model Converter
>Reporter: Angela Schreiber
>Priority: Minor
> Fix For: Content-Package to Feature Model Converter 1.1.14
>
>
> The {{AbstractJcrNodeParser}} has a constant defined for "jcr:root". It would
> be better if it (and subclasses) would not rely on the default namespace
> mappings.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (SLING-10784) BundleEntryHandler - sonar findings
[ https://issues.apache.org/jira/browse/SLING-10784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls updated SLING-10784: --- Fix Version/s: Content-Package to Feature Model Converter 1.1.14 Content-Package to Feature Model Converter 1.1.14 (was: Content-Package to Feature Model Converter 1.1.12) > BundleEntryHandler - sonar findings > --- > > Key: SLING-10784 > URL: https://issues.apache.org/jira/browse/SLING-10784 > Project: Sling > Issue Type: Sub-task > Components: Content-Package to Feature Model Converter >Reporter: Angela Schreiber >Priority: Major > Fix For: Content-Package to Feature Model Converter 1.1.14 > > > https://sonarcloud.io/code?id=apache_sling-org-apache-sling-feature-cpconverter=apache_sling-org-apache-sling-feature-cpconverter%3Asrc%2Fmain%2Fjava%2Forg%2Fapache%2Fsling%2Ffeature%2Fcpconverter%2Fhandlers%2FBundleEntryHandler.java -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (SLING-11060) CPConverter - sling initial content - ACL support
[
https://issues.apache.org/jira/browse/SLING-11060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Pauls updated SLING-11060:
---
Fix Version/s: Content-Package to Feature Model Converter 1.1.14
Content-Package to Feature Model Converter 1.1.14
(was: Content-Package to Feature Model Converter 1.1.12)
> CPConverter - sling initial content - ACL support
> -
>
> Key: SLING-11060
> URL: https://issues.apache.org/jira/browse/SLING-11060
> Project: Sling
> Issue Type: Bug
> Components: Content-Package to Feature Model Converter
>Affects Versions: Content-Package to Feature Model Converter 1.1.10
>Reporter: Niek Raaijmakers
>Assignee: Niek Raaijmakers
>Priority: Major
> Fix For: Content-Package to Feature Model Converter 1.1.14
>
>
> Currently, we do not implement the ACL support for Sling Initial Content as
> specified :
> [https://sling.apache.org/documentation/bundles/repository-initialization.html]
> We need the following methods
> (org.apache.sling.feature.cpconverter.handlers.slinginitialcontent.VaultContentXMLContentCreator)
> implemented or another workaround found:
>
> {code:java}
> @Override
> public boolean switchCurrentNode(String subPath, String newNodeType) throws
> RepositoryException {
> throw new UnsupportedOperationException();
> }
> @Override
> public void createUser(String name, String password, Map
> extraProperties) throws RepositoryException {
> throw new UnsupportedOperationException();
> }
> @Override
> public void createGroup(String name, String[] members, Map
> extraProperties) throws RepositoryException {
> throw new UnsupportedOperationException();
> }
> @Override
> public void createAce(String principal, String[] grantedPrivileges, String[]
> deniedPrivileges, String order) throws RepositoryException {
> throw new UnsupportedOperationException();
> }
> @Override
> public void createAce(String principalId, String[] grantedPrivilegeNames,
> String[] deniedPrivilegeNames,
> String order, Map restrictions, Map
> mvRestrictions,
> Set removedRestrictionNames) throws RepositoryException {
> throw new UnsupportedOperationException();
> }{code}
>
> Stashed code is on branch: SLING-10931
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (SLING-10790) BundleEntryHandler.extractArtifactId may use wrong GAV
[
https://issues.apache.org/jira/browse/SLING-10790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Pauls updated SLING-10790:
---
Fix Version/s: Content-Package to Feature Model Converter 1.1.14
Content-Package to Feature Model Converter 1.1.14
(was: Content-Package to Feature Model Converter 1.1.12)
> BundleEntryHandler.extractArtifactId may use wrong GAV
> --
>
> Key: SLING-10790
> URL: https://issues.apache.org/jira/browse/SLING-10790
> Project: Sling
> Issue Type: Bug
> Components: Content-Package to Feature Model Converter
>Reporter: Angela Schreiber
>Priority: Minor
> Fix For: Content-Package to Feature Model Converter 1.1.14
>
>
> [~kpauls], if my reading of {{BundleEntryHandler.extractArtifactId}} is
> correct it the method might be ending up using the wrong
> groupId/artifactId/version.
> the code will loop over jar-entries and stop if the extracted GAV matches the
> bundle name. however, groupId/artifactId/version are not reset to {{null}} in
> case they were successfully extracted but didn't end up matching the bundle
> name i.e. {quote}it was the pom.properties we were looking for{quote}.
> i can't tell how big of an issue that is (and how likely). but given the fact
> that there is some extra effort to verify that the parsed pom is actually the
> right one, it might actually be relevant. the relies on a compliant content
> package that does contain a matching pom, which may or may not be the case...
> logging a warning or throwing a ConverterException in case of violation might
> help spotting troublesome content packages instead of getting some sort of
> side effect if another pom was spotted.
> a heavily simplified copy of the method:
> {code}
> String artifactId = null;
> String version = null;
> String groupId = null;
> String classifier = null;
> for (Enumeration e = jarFile.entries();
> e.hasMoreElements();) {
> [...]
> // extract groupId/artifactId/version
> [...]
>
> if (groupId != null && artifactId != null && version != null) {
> // bundleName is now the bare name without extension
> String synthesized = artifactId + "-" + version;
> // it was the pom.properties we were looking for
> if (bundleName.startsWith(synthesized) ||
> bundleName.equals(artifactId)) {
> [...]
>
> // no need to iterate further
> break;
> }
> }
> }
>
> if (groupId == null) {
> [...]
> }
> return new ArtifactId(groupId, artifactId, version, classifier,
> JAR_TYPE);
> {code}
> feel free to resolve as not a problem in case my reading of the code is all
> wrong.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (SLING-10781) ContentPackage2FeatureModelConverterLauncher - sonar findings
[ https://issues.apache.org/jira/browse/SLING-10781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls updated SLING-10781: --- Fix Version/s: Content-Package to Feature Model Converter 1.1.14 Content-Package to Feature Model Converter 1.1.14 (was: Content-Package to Feature Model Converter 1.1.12) > ContentPackage2FeatureModelConverterLauncher - sonar findings > - > > Key: SLING-10781 > URL: https://issues.apache.org/jira/browse/SLING-10781 > Project: Sling > Issue Type: Sub-task > Components: Content-Package to Feature Model Converter >Reporter: Angela Schreiber >Priority: Major > Fix For: Content-Package to Feature Model Converter 1.1.14 > > > see > https://sonarcloud.io/code?id=apache_sling-org-apache-sling-feature-cpconverter=apache_sling-org-apache-sling-feature-cpconverter%3Asrc%2Fmain%2Fjava%2Forg%2Fapache%2Fsling%2Ffeature%2Fcpconverter%2Fcli%2FContentPackage2FeatureModelConverterLauncher.java -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (SLING-10787) BundleEntryHandler.extractArtifactId prone to IllegalArgumentException
[
https://issues.apache.org/jira/browse/SLING-10787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Pauls updated SLING-10787:
---
Fix Version/s: Content-Package to Feature Model Converter 1.1.14
Content-Package to Feature Model Converter 1.1.14
(was: Content-Package to Feature Model Converter 1.1.12)
> BundleEntryHandler.extractArtifactId prone to IllegalArgumentException
> --
>
> Key: SLING-10787
> URL: https://issues.apache.org/jira/browse/SLING-10787
> Project: Sling
> Issue Type: Bug
> Components: Content-Package to Feature Model Converter
>Reporter: Angela Schreiber
>Priority: Major
> Fix For: Content-Package to Feature Model Converter 1.1.14
>
>
> trying to address sonar findings for {{BundleEntryHandler}} (see SLING-10784)
> i noticed that there is no guarantee that 'artifactId' and 'version' are not
> left null after all the processing completed. if any of the two is null
> constructing a new {{ArtifactId}} object from the given strings will fail
> will {{IllegalArgumentException}}.
> it might be as simple as extracting the following statements out of the
> previous block that handles the {{groupId == null}} case:
> {code}
> if (artifactId == null || artifactId.isEmpty()) {
> artifactId = groupId;
> }
>
> if (version == null) {
> Version osgiVersion =
> Version.parseVersion(getCheckedProperty(jarFile.getManifest(),
> Constants.BUNDLE_VERSION));
> version = osgiVersion.getMajor() + "." + osgiVersion.getMinor() +
> "." + osgiVersion.getMicro() + (osgiVersion.getQualifier().isEmpty() ? "" :
> "-" + osgiVersion.getQualifier());
> }
> {code}
> but i am not totally sure there is a reason the method
> {{BundleEntryHandler.extractArtifactId}} gets called out by sonar :)
> note: on line 472 of the same method {{IllegalArgumentException}} is
> caught so i assume the code doesn't expect this method to fail upon
> building the {{ArtifactId}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (SLING-10914) CpConverter - package type calculation should take filters into account
[ https://issues.apache.org/jira/browse/SLING-10914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls updated SLING-10914: --- Fix Version/s: Content-Package to Feature Model Converter 1.1.14 Content-Package to Feature Model Converter 1.1.14 (was: Content-Package to Feature Model Converter 1.1.12) > CpConverter - package type calculation should take filters into account > --- > > Key: SLING-10914 > URL: https://issues.apache.org/jira/browse/SLING-10914 > Project: Sling > Issue Type: Bug > Components: Content-Package to Feature Model Converter >Affects Versions: Content-Package to Feature Model Converter 1.1.10 >Reporter: Niek Raaijmakers >Assignee: Niek Raaijmakers >Priority: Minor > Fix For: Content-Package to Feature Model Converter 1.1.14 > > > The converter does attempt to (re-)calculate the package type (application, > content, mixed) as part of creating the converted packages. However, it > doesn't take the targets of the filters into account when determining the > type. As such, it is possible that e.g. a package containing a filter > targeting apps would end up being classified as being of type content. > Furthermore, it when looking into the content, it doesn't take into account > if the content is covered by filters - ie., it doesn't really check if the > content would be ignored by vault. > Given that it is hard to know what vault will install or not, it might not be > possible to fix the second issue - however, it should be possible to at least > look at the filters and take their targets into account (as pathes) when > (re-)calculating the package type. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (SLING-10760) Converter ignores access control content and users/groups in .content.xml files
[
https://issues.apache.org/jira/browse/SLING-10760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Pauls updated SLING-10760:
---
Fix Version/s: Content-Package to Feature Model Converter 1.1.14
(was: Content-Package to Feature Model Converter 1.1.12)
> Converter ignores access control content and users/groups in .content.xml
> files
> ---
>
> Key: SLING-10760
> URL: https://issues.apache.org/jira/browse/SLING-10760
> Project: Sling
> Issue Type: Bug
> Components: Content-Package to Feature Model Converter
>Reporter: Angela Schreiber
>Priority: Critical
> Fix For: Content-Package to Feature Model Converter 1.1.14
>
> Attachments: subtree_in_contentxml_policy.png,
> subtree_in_contentxml_sibling.png
>
>
> [~kpauls], while trying to find more edge cases that could cause SLING-10754,
> i noticed that not only sibling nodes but also access control content (like
> e.g. _rep:policy_ nodes) contained in a _.content.xml_ get installed by
> Jackrabbit Filevault even if those nodes are not covered by the corresponding
> {{WorkspaceFilter}}.
> It also seems that these package 'entries' are not spotted by the converter
> and thus the dedicated {{EntryHandler}} implementations that are intended to
> analyze and convert special content like e.g. access control (but probably
> not limited to that) are not triggered.
> In other words: content hidden in _.content.xml_ will not be properly
> converted but will be installed even if not covered by _filter.xml_
> associated with the content package. I don't know if that actually intended
> behavior of Jackrabbit FileVault (the documentation clearly stating that
> everything should be covered by filter rules [0], section 'Usage for
> Import/Installation'), but if it is correct it might in the worse case
> require the converter to parse all _.content.xml_ files and delegate to the
> proper handler implementations.
> [~kwin], I would appreciate your input on the FileVault related question of
> this ticket. In particular: is it correct and intended that subnodes defined
> in _.content.xml_ get installed even if not covered by any filter rule?
> [0] https://jackrabbit.apache.org/filevault/filter.html
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Resolved] (SLING-10921) Converter creates dependencies for extracted content that are wrong when the provider is around in more than one run mode
[ https://issues.apache.org/jira/browse/SLING-10921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls resolved SLING-10921. Resolution: Fixed > Converter creates dependencies for extracted content that are wrong when the > provider is around in more than one run mode > - > > Key: SLING-10921 > URL: https://issues.apache.org/jira/browse/SLING-10921 > Project: Sling > Issue Type: Bug > Components: Content-Package to Feature Model Converter >Affects Versions: Content-Package to Feature Model Converter 1.1.10 >Reporter: Karl Pauls >Assignee: Karl Pauls >Priority: Major > Fix For: Content-Package to Feature Model Converter 1.1.12 > > > When the converter extracts content from bundles it does that again every > time it hits the bundle (assuming it is present in different > locations/runmodes/packages). That is a problem as this way, only the last > location will be added as a dependency to the package - causing it to fail to > install if it was used from one of the other locations. > We should just not generate a dependency, like we do with contain packages. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (SLING-9624) Get rid of custom "org.osgi.framework.system.packages"
[ https://issues.apache.org/jira/browse/SLING-9624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500733#comment-17500733 ] Karl Pauls commented on SLING-9624: --- right, but the versions are the versions sling had since a long time. I don't know why they where like they where. > Get rid of custom "org.osgi.framework.system.packages" > -- > > Key: SLING-9624 > URL: https://issues.apache.org/jira/browse/SLING-9624 > Project: Sling > Issue Type: Improvement > Components: Starter >Reporter: Konrad Windszus >Priority: Major > Fix For: Starter 13 > > Time Spent: 10m > Remaining Estimate: 0h > > Instead of using a Sling specific "org.osgi.framework.system.packages" > property > (https://github.com/apache/sling-org-apache-sling-starter/blob/5f44b7f6c6b75e4cfd5574fb701c3e7eca8405ef/src/main/provisioning/launchpad.txt#L26) > we should just rely on the Felix default > (https://github.com/apache/felix-dev/blob/master/framework/src/main/resources/default.properties) > to not miss to export all relevant packages for the different JREs > compare with > https://lists.apache.org/thread.html/r0aa3c02c38b5026e24684a00de3c6c8506e166334e77892ac2ee0ab3%40%3Cdev.sling.apache.org%3E. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (SLING-11173) Wrong version of org.osgi.framework exported (OSGi R7 instead of OSGi R8)
[ https://issues.apache.org/jira/browse/SLING-11173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500715#comment-17500715 ] Karl Pauls commented on SLING-11173: [~kwin], I guess you just have to adjust the exports to match, no? Unless you wanted to go with SLING-9624 - the problem there is that if you want to use the modules/classpath then we have bundles that assume that the versions are different. The correct list for the current felix osgi exports is here: https://github.com/apache/felix-dev/blob/master/framework/src/main/resources/default.properties#L108 > Wrong version of org.osgi.framework exported (OSGi R7 instead of OSGi R8) > - > > Key: SLING-11173 > URL: https://issues.apache.org/jira/browse/SLING-11173 > Project: Sling > Issue Type: Bug > Components: Starter >Reporter: Konrad Windszus >Priority: Blocker > Fix For: Starter 12 > > > Although Felix was updated in SLING-10409 to Felix 7 (OSGi R8 compliant) the > package exports are still only for OSGi R7 in > https://github.com/apache/sling-org-apache-sling-starter/blob/150e60df97a6d8911e938b76903f64d54f1201df/src/main/features/boot.json#L151. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (SLING-9624) Get rid of custom "org.osgi.framework.system.packages"
[ https://issues.apache.org/jira/browse/SLING-9624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500713#comment-17500713 ] Karl Pauls commented on SLING-9624: --- Right, that was the issue - we had bundles that have imports with version ranges that assume the old package versioning sling did. Thats why I did massage the exports of the system bundle to work with that and still pick up the modules from the jvm where possible. > Get rid of custom "org.osgi.framework.system.packages" > -- > > Key: SLING-9624 > URL: https://issues.apache.org/jira/browse/SLING-9624 > Project: Sling > Issue Type: Improvement > Components: Starter >Reporter: Konrad Windszus >Priority: Major > Fix For: Starter 13 > > > Instead of using a Sling specific "org.osgi.framework.system.packages" > property > (https://github.com/apache/sling-org-apache-sling-starter/blob/5f44b7f6c6b75e4cfd5574fb701c3e7eca8405ef/src/main/provisioning/launchpad.txt#L26) > we should just rely on the Felix default > (https://github.com/apache/felix-dev/blob/master/framework/src/main/resources/default.properties) > to not miss to export all relevant packages for the different JREs > compare with > https://lists.apache.org/thread.html/r0aa3c02c38b5026e24684a00de3c6c8506e166334e77892ac2ee0ab3%40%3Cdev.sling.apache.org%3E. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (SLING-11166) Launcher bootstrap should have a way to run it without doing a System.exit on error
[ https://issues.apache.org/jira/browse/SLING-11166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls resolved SLING-11166. Resolution: Fixed > Launcher bootstrap should have a way to run it without doing a System.exit on > error > --- > > Key: SLING-11166 > URL: https://issues.apache.org/jira/browse/SLING-11166 > Project: Sling > Issue Type: Improvement > Components: Feature Model >Affects Versions: Feature Model Launcher 1.2.0 >Reporter: Karl Pauls >Assignee: Karl Pauls >Priority: Major > Fix For: Feature Model Launcher 1.2.2 > > > The Bootstrap in the launcher is there to make it easy to use it in different > use-cases - however, the run method currently does System.exit on errors > which might not be what one expects in different use-cases. We should add > another method that doesn't System.exit. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (SLING-11166) Launcher bootstrap should have a way to run it without doing a System.exit on error
Karl Pauls created SLING-11166: -- Summary: Launcher bootstrap should have a way to run it without doing a System.exit on error Key: SLING-11166 URL: https://issues.apache.org/jira/browse/SLING-11166 Project: Sling Issue Type: Improvement Components: Feature Model Affects Versions: Feature Model Launcher 1.2.0 Reporter: Karl Pauls Assignee: Karl Pauls Fix For: Feature Model Launcher 1.2.2 The Bootstrap in the launcher is there to make it easy to use it in different use-cases - however, the run method currently does System.exit on errors which might not be what one expects in different use-cases. We should add another method that doesn't System.exit. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (SLING-11164) Configuration API feature to region cache can lose mappings on feature merge
[ https://issues.apache.org/jira/browse/SLING-11164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls resolved SLING-11164. Resolution: Fixed > Configuration API feature to region cache can lose mappings on feature merge > > > Key: SLING-11164 > URL: https://issues.apache.org/jira/browse/SLING-11164 > Project: Sling > Issue Type: Bug > Components: Feature Model Analyser >Affects Versions: Feature Model API Regions Extension 1.5.0 >Reporter: Karl Pauls >Assignee: Karl Pauls >Priority: Major > Fix For: Feature Model API Regions Extension 1.5.2 > > > When merging two features which both have entries in the feature to region > cache of their api region, one of them will be lost. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (SLING-11164) Configuration API feature to region cache can lose mappings on feature merge
Karl Pauls created SLING-11164: -- Summary: Configuration API feature to region cache can lose mappings on feature merge Key: SLING-11164 URL: https://issues.apache.org/jira/browse/SLING-11164 Project: Sling Issue Type: Bug Components: Feature Model Analyser Affects Versions: Feature Model API Regions Extension 1.5.0 Reporter: Karl Pauls Assignee: Karl Pauls Fix For: Feature Model API Regions Extension 1.5.2 When merging two features which both have entries in the feature to region cache of their api region, one of them will be lost. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (SLING-11155) Bundled scripts should be registered by path for the main script when overriding
[ https://issues.apache.org/jira/browse/SLING-11155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls resolved SLING-11155. Resolution: Fixed > Bundled scripts should be registered by path for the main script when > overriding > > > Key: SLING-11155 > URL: https://issues.apache.org/jira/browse/SLING-11155 > Project: Sling > Issue Type: Bug > Components: Scripting, Servlets >Affects Versions: Servlets Resolver 2.9.2 >Reporter: Karl Pauls >Assignee: Karl Pauls >Priority: Major > Fix For: Servlets Resolver 2.9.4 > > Time Spent: 20m > Remaining Estimate: 0h > > When a bundled script is provided without a real script but a resource super > type, it gets a capability for the resource type and will be registered for > that resource type (with the resource super type set). That is done to proxy > the resource super type. > The problem is that the resolver will register a GET/HEAD servlet > automatically for resource types that have no other properties set. > Consequently, this setup ends up handling all GET requests while it should > only handle requests for the default extension (i.e. it overrides requests > for .json which would normally be handled by the default GET servlet). > The fix is for the resolver to not register these proxies as resource types > servlets but bind them by path instead. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (SLING-11155) Bundled scripts should be registered by path for the main script when overriding
Karl Pauls created SLING-11155: -- Summary: Bundled scripts should be registered by path for the main script when overriding Key: SLING-11155 URL: https://issues.apache.org/jira/browse/SLING-11155 Project: Sling Issue Type: Bug Components: Scripting, Servlets Affects Versions: Servlets Resolver 2.9.2 Reporter: Karl Pauls Assignee: Karl Pauls Fix For: Servlets Resolver 2.9.4 When a bundled script is provided without a real script but a resource super type, it gets a capability for the resource type and will be registered for that resource type (with the resource super type set). That is done to proxy the resource super type. The problem is that the resolver will register a GET/HEAD servlet automatically for resource types that have no other properties set. Consequently, this setup ends up handling all GET requests while it should only handle requests for the default extension (i.e. it overrides requests for .json which would normally be handled by the default GET servlet). The fix is for the resolver to not register these proxies as resource types servlets but bind them by path instead. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (SLING-11148) Feature launcher should look up configadmin service with all service lookup
[ https://issues.apache.org/jira/browse/SLING-11148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls resolved SLING-11148. Resolution: Fixed Done in https://github.com/apache/sling-org-apache-sling-feature-launcher/pull/38 > Feature launcher should look up configadmin service with all service lookup > --- > > Key: SLING-11148 > URL: https://issues.apache.org/jira/browse/SLING-11148 > Project: Sling > Issue Type: Bug > Components: Feature Model >Affects Versions: Feature Model Launcher 1.2.0 >Reporter: Karl Pauls >Assignee: Karl Pauls >Priority: Major > Fix For: Feature Model Launcher 1.2.2 > > > The feature model launcher looks up config admins inside the launched > features using a service tracker without setting the all services boolean to > true. That can cause it to miss config admins if the config admin interface > is available on the outside. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (SLING-11148) Feature launcher should look up configadmin service with all service lookup
Karl Pauls created SLING-11148: -- Summary: Feature launcher should look up configadmin service with all service lookup Key: SLING-11148 URL: https://issues.apache.org/jira/browse/SLING-11148 Project: Sling Issue Type: Bug Components: Feature Model Affects Versions: Feature Model Launcher 1.2.0 Reporter: Karl Pauls Assignee: Karl Pauls Fix For: Feature Model Launcher 1.2.2 The feature model launcher looks up config admins inside the launched features using a service tracker without setting the all services boolean to true. That can cause it to miss config admins if the config admin interface is available on the outside. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (SLING-11144) Compiler does not create classfiles if compilation of unrelated compilation unit fails
[ https://issues.apache.org/jira/browse/SLING-11144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls resolved SLING-11144. Resolution: Fixed > Compiler does not create classfiles if compilation of unrelated compilation > unit fails > -- > > Key: SLING-11144 > URL: https://issues.apache.org/jira/browse/SLING-11144 > Project: Sling > Issue Type: Bug > Components: Commons >Affects Versions: Commons Compiler 2.4.0 >Reporter: Karl Pauls >Assignee: Karl Pauls >Priority: Major > Fix For: Commons Compiler 2.5.0 > > Time Spent: 20m > Remaining Estimate: 0h > > SLING-7111 made it so that we (correctly) don't write out classfiles > resulting from failing compilations - however, it was too aggressive in that > it just stops to write classfiles altogether. That is fine if there was only > a single compilation unit to begin with. Otherwise, it is a mistake as now, > assuming multiple compilation units, it depends on when the failing > compilation unit gets processed. > We should only not write the classfiles for the compilation unit that failed > and proceed for the other compilation units. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (SLING-11144) Compiler does not create classfiles if compilation of unrelated compilation unit fails
Karl Pauls created SLING-11144: -- Summary: Compiler does not create classfiles if compilation of unrelated compilation unit fails Key: SLING-11144 URL: https://issues.apache.org/jira/browse/SLING-11144 Project: Sling Issue Type: Bug Components: Commons Affects Versions: Commons Compiler 2.4.0 Reporter: Karl Pauls Assignee: Karl Pauls Fix For: Commons Compiler 2.5.0 SLING-7111 made it so that we (correctly) don't write out classfiles resulting from failing compilations - however, it was too aggressive in that it just stops to write classfiles altogether. That is fine if there was only a single compilation unit to begin with. Otherwise, it is a mistake as now, assuming multiple compilation units, it depends on when the failing compilation unit gets processed. We should only not write the classfiles for the compilation unit that failed and proceed for the other compilation units. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (SLING-11099) JSPC plugin missing critical dependencies by default
[
https://issues.apache.org/jira/browse/SLING-11099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Pauls resolved SLING-11099.
Resolution: Fixed
Done in https://github.com/apache/sling-jspc-maven-plugin/pull/7
> JSPC plugin missing critical dependencies by default
>
>
> Key: SLING-11099
> URL: https://issues.apache.org/jira/browse/SLING-11099
> Project: Sling
> Issue Type: Bug
> Components: Maven Plugins and Archetypes
>Affects Versions: JSPC Maven Plugin 2.3.2
>Reporter: Donal Fellows
>Assignee: Karl Pauls
>Priority: Major
> Fix For: JSPC Maven Plugin 2.3.4
>
>
> The JSPC Maven Plugin, version 2.3.2, fails to work when used as an ordinary
> Maven plugin. The first two lines of relevance (there's a _lot_ more stack
> trace, but it is really not very informative) from the build logs are:
> {{{}[WARNING] Error injecting: org.apache.sling.maven.jspc.JspcMojo
> {}}}{{{}java.lang.NoClassDefFoundError:
> org/apache/sling/feature/ArtifactId{}}}
> The problem appears to be that the _{{org.apache.sling.feature}}_ dependency
> (and, by transitive closure, the _{{org.osgi.framework}}_ dependency as well)
> is marked as {_}provided{_}. Adding the following two as explicit plugin
> dependencies is a workaround (and allows at least my builds to work).
> However, I do not believe that ordinary Maven users should have to do such a
> workaround.
> {{ }}
> {{ org.apache.sling}}
> {{ org.apache.sling.feature}}
> {{ 1.2.30}}
> {{ }}
> {{ }}
> {{ org.osgi}}
> {{ org.osgi.framework}}
> {{ 1.10.0}}
> {{ }}
> Note that 2.3.0 worked correctly.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (SLING-11099) JSPC plugin missing critical dependencies by default
[
https://issues.apache.org/jira/browse/SLING-11099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Pauls updated SLING-11099:
---
Fix Version/s: JSPC Maven Plugin 2.2.4
> JSPC plugin missing critical dependencies by default
>
>
> Key: SLING-11099
> URL: https://issues.apache.org/jira/browse/SLING-11099
> Project: Sling
> Issue Type: Bug
> Components: Maven Plugins and Archetypes
>Affects Versions: JSPC Maven Plugin 2.3.2
>Reporter: Donal Fellows
>Assignee: Karl Pauls
>Priority: Major
> Fix For: JSPC Maven Plugin 2.2.4
>
>
> The JSPC Maven Plugin, version 2.3.2, fails to work when used as an ordinary
> Maven plugin. The first two lines of relevance (there's a _lot_ more stack
> trace, but it is really not very informative) from the build logs are:
> {{{}[WARNING] Error injecting: org.apache.sling.maven.jspc.JspcMojo
> {}}}{{{}java.lang.NoClassDefFoundError:
> org/apache/sling/feature/ArtifactId{}}}
> The problem appears to be that the _{{org.apache.sling.feature}}_ dependency
> (and, by transitive closure, the _{{org.osgi.framework}}_ dependency as well)
> is marked as {_}provided{_}. Adding the following two as explicit plugin
> dependencies is a workaround (and allows at least my builds to work).
> However, I do not believe that ordinary Maven users should have to do such a
> workaround.
> {{ }}
> {{ org.apache.sling}}
> {{ org.apache.sling.feature}}
> {{ 1.2.30}}
> {{ }}
> {{ }}
> {{ org.osgi}}
> {{ org.osgi.framework}}
> {{ 1.10.0}}
> {{ }}
> Note that 2.3.0 worked correctly.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (SLING-11099) JSPC plugin missing critical dependencies by default
[
https://issues.apache.org/jira/browse/SLING-11099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17483984#comment-17483984
]
Karl Pauls commented on SLING-11099:
Yeah, looks like a bug. I guess I missed that adding an artifactid as a
property makes it need the classes even so it is not configured. I'll fix it.
> JSPC plugin missing critical dependencies by default
>
>
> Key: SLING-11099
> URL: https://issues.apache.org/jira/browse/SLING-11099
> Project: Sling
> Issue Type: Bug
> Components: Maven Plugins and Archetypes
>Affects Versions: JSPC Maven Plugin 2.3.2
>Reporter: Donal Fellows
>Assignee: Karl Pauls
>Priority: Major
>
> The JSPC Maven Plugin, version 2.3.2, fails to work when used as an ordinary
> Maven plugin. The first two lines of relevance (there's a _lot_ more stack
> trace, but it is really not very informative) from the build logs are:
> {{{}[WARNING] Error injecting: org.apache.sling.maven.jspc.JspcMojo
> {}}}{{{}java.lang.NoClassDefFoundError:
> org/apache/sling/feature/ArtifactId{}}}
> The problem appears to be that the _{{org.apache.sling.feature}}_ dependency
> (and, by transitive closure, the _{{org.osgi.framework}}_ dependency as well)
> is marked as {_}provided{_}. Adding the following two as explicit plugin
> dependencies is a workaround (and allows at least my builds to work).
> However, I do not believe that ordinary Maven users should have to do such a
> workaround.
> {{ }}
> {{ org.apache.sling}}
> {{ org.apache.sling.feature}}
> {{ 1.2.30}}
> {{ }}
> {{ }}
> {{ org.osgi}}
> {{ org.osgi.framework}}
> {{ 1.10.0}}
> {{ }}
> Note that 2.3.0 worked correctly.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (SLING-11099) JSPC plugin missing critical dependencies by default
[
https://issues.apache.org/jira/browse/SLING-11099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Pauls reassigned SLING-11099:
--
Assignee: Karl Pauls
> JSPC plugin missing critical dependencies by default
>
>
> Key: SLING-11099
> URL: https://issues.apache.org/jira/browse/SLING-11099
> Project: Sling
> Issue Type: Bug
> Components: Maven Plugins and Archetypes
>Affects Versions: JSPC Maven Plugin 2.3.2
>Reporter: Donal Fellows
>Assignee: Karl Pauls
>Priority: Major
>
> The JSPC Maven Plugin, version 2.3.2, fails to work when used as an ordinary
> Maven plugin. The first two lines of relevance (there's a _lot_ more stack
> trace, but it is really not very informative) from the build logs are:
> {{{}[WARNING] Error injecting: org.apache.sling.maven.jspc.JspcMojo
> {}}}{{{}java.lang.NoClassDefFoundError:
> org/apache/sling/feature/ArtifactId{}}}
> The problem appears to be that the _{{org.apache.sling.feature}}_ dependency
> (and, by transitive closure, the _{{org.osgi.framework}}_ dependency as well)
> is marked as {_}provided{_}. Adding the following two as explicit plugin
> dependencies is a workaround (and allows at least my builds to work).
> However, I do not believe that ordinary Maven users should have to do such a
> workaround.
> {{ }}
> {{ org.apache.sling}}
> {{ org.apache.sling.feature}}
> {{ 1.2.30}}
> {{ }}
> {{ }}
> {{ org.osgi}}
> {{ org.osgi.framework}}
> {{ 1.10.0}}
> {{ }}
> Note that 2.3.0 worked correctly.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Resolved] (SLING-11093) Bundled scripts should only be registered for the absolute resource type if the relative resource type is the same
[ https://issues.apache.org/jira/browse/SLING-11093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls resolved SLING-11093. Resolution: Fixed Done in the linked PR > Bundled scripts should only be registered for the absolute resource type if > the relative resource type is the same > -- > > Key: SLING-11093 > URL: https://issues.apache.org/jira/browse/SLING-11093 > Project: Sling > Issue Type: Improvement > Components: Scripting, Servlets >Affects Versions: Servlets Resolver 2.9.2 >Reporter: Karl Pauls >Assignee: Karl Pauls >Priority: Major > Fix For: Servlets Resolver 2.9.2 > > Time Spent: 0.5h > Remaining Estimate: 0h > > The capabilities for bundled scripts typically contain the same resource type > as an absolute and a relative version. Right now, we end up registering both, > which is not needed if we have an absolute resource type anyways. > Furthermore, this can cause problems if the servlet root index is configured > because, in that case, one has to take into account the bundle scripts as > their relative resource types will depend on that as well. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (SLING-11093) Bundled scripts should only be registered for the absolute resource type if the relative resource type is the same
Karl Pauls created SLING-11093: -- Summary: Bundled scripts should only be registered for the absolute resource type if the relative resource type is the same Key: SLING-11093 URL: https://issues.apache.org/jira/browse/SLING-11093 Project: Sling Issue Type: Improvement Components: Scripting, Servlets Affects Versions: Servlets Resolver 2.9.2 Reporter: Karl Pauls Assignee: Karl Pauls Fix For: Servlets Resolver 2.9.2 The capabilities for bundled scripts typically contain the same resource type as an absolute and a relative version. Right now, we end up registering both, which is not needed if we have an absolute resource type anyways. Furthermore, this can make cause problems if the servlet root index is configured because in that case, one has to take into account the bundle scripts as their relative resource types will depend on that as well. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (SLING-11075) Maven id for bundles that don't have a GAV can end up not being well formed
[ https://issues.apache.org/jira/browse/SLING-11075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls resolved SLING-11075. Resolution: Fixed > Maven id for bundles that don't have a GAV can end up not being well formed > --- > > Key: SLING-11075 > URL: https://issues.apache.org/jira/browse/SLING-11075 > Project: Sling > Issue Type: Bug > Components: Feature Model >Affects Versions: Content-Package to Feature Model Converter 1.1.10 >Reporter: Karl Pauls >Assignee: Karl Pauls >Priority: Major > Fix For: Content-Package to Feature Model Converter 1.1.12 > > > When the converter finds a bundle, it tries to determine the maven > coordinates for it by looking at the embedded maven info. If there is none, > it tries to guess it from the maven info path. If that fails, it takes the > bsn and derives the info from it. > That works, however, in the case of a bsn, it doesn't strip attributes which > can cause an invalid mvn id in the end (e.g., if the bsn has a > ;singelton:=true) -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (SLING-11075) Maven id for bundles that don't have a GAV can end up not being well formed
Karl Pauls created SLING-11075: -- Summary: Maven id for bundles that don't have a GAV can end up not being well formed Key: SLING-11075 URL: https://issues.apache.org/jira/browse/SLING-11075 Project: Sling Issue Type: Bug Components: Feature Model Affects Versions: Content-Package to Feature Model Converter 1.1.10 Reporter: Karl Pauls Assignee: Karl Pauls Fix For: Content-Package to Feature Model Converter 1.1.12 When the converter finds a bundle, it tries to determine the maven coordinates for it by looking at the embedded maven info. If there is none, it tries to guess it from the maven info path. If that fails, it takes the bsn and derives the info from it. That works, however, in the case of a bsn, it doesn't strip attributes which can cause an invalid mvn id in the end (e.g., if the bsn has a ;singelton:=true) -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (SLING-10931) CPConverter - Sling initial content - json files should be converted to folders with a content xml in any case to avoid conflicts
[ https://issues.apache.org/jira/browse/SLING-10931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls resolved SLING-10931. Resolution: Fixed Done in https://github.com/apache/sling-org-apache-sling-feature-cpconverter/pull/125 > CPConverter - Sling initial content - json files should be converted to > folders with a content xml in any case to avoid conflicts > - > > Key: SLING-10931 > URL: https://issues.apache.org/jira/browse/SLING-10931 > Project: Sling > Issue Type: Bug > Components: Content-Package to Feature Model Converter >Affects Versions: Content-Package to Feature Model Converter 1.1.10 >Reporter: Niek Raaijmakers >Assignee: Niek Raaijmakers >Priority: Major > Fix For: Content-Package to Feature Model Converter 1.1.12 > > > In case of converting sling initial content containing JSON files over to > xml, currently the cpconverter simply creates a xml file in the same level. > The problem is when there are other files in a directory with the same name > to go along the resourceType. > For example we have: > > * page.json > * page/body.html > * page/footer.html > > The result will be: > * page.xml > * page/body.html > * page/footer.html > > Vault doesn't like this approach so much, resulting in stuff like: > * page.dir > * page.xml > * page/.content.xml (with resourceType nt:folder) > * page/body.html > * page/footer.html > The solution lies in simply redirecting the output to .content.xml in a new > folder: > * page/.content.xml > * page/body.html > * page/footer.html > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (SLING-11030) OSGiServiceInjector.getService() calls ungetService even if service is not get
[ https://issues.apache.org/jira/browse/SLING-11030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17463282#comment-17463282 ] Karl Pauls commented on SLING-11030: Additionally, I think it would be good to improve the getService call to keep looping over the references until one did actually return a service. Like it is right now, it might return null even so there would have been a different service available. Obviously, the callback should then be seeded with the ref that was used (i.e., the first that didn't return null) - if any. Futhermore, the getService_s_ has a similar issue where it a) might end up returning an empty array (if there was no ref returning a service) - instead, it should return null if the array is empty in the end and regardless, it should filter out the refs that returned null from the refs given to the callback. > OSGiServiceInjector.getService() calls ungetService even if service is not get > -- > > Key: SLING-11030 > URL: https://issues.apache.org/jira/browse/SLING-11030 > Project: Sling > Issue Type: Bug > Components: Sling Models >Affects Versions: Models Implementation 1.5.0 >Reporter: Carsten Ziegeler >Priority: Major > Fix For: Models Implementation 1.5.2 > > > The getService method gets all service references, but only from one of them > it gets the service. However all service references are passed in to the > callback for disposal. So for all references an unget is called, although it > happened only for one > In addition, the code is assuming that the service with the highest ranking > is always gettable. A null check is missing at : > https://github.com/apache/sling-org-apache-sling-models-impl/blob/89fcb8702e29ad3322ee2a023ae6b24e5d2f83ab/src/main/java/org/apache/sling/models/impl/injectors/OSGiServiceInjector.java#L114 > > It would be better to loop over the services references until one returns non > null and then only dispose that reference later -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-10926) Error Handler throws Error checking if response is Open
[ https://issues.apache.org/jira/browse/SLING-10926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls closed SLING-10926. -- > Error Handler throws Error checking if response is Open > --- > > Key: SLING-10926 > URL: https://issues.apache.org/jira/browse/SLING-10926 > Project: Sling > Issue Type: Bug > Components: Servlets >Affects Versions: Servlets Resolver 2.8.0 >Reporter: Hakim Sadikali >Assignee: Carsten Ziegeler >Priority: Major > Fix For: Servlets Resolver 2.9.2 > > > The Error handler could check to see if its open before the writer is ever > created, leading to a null pointer exception: > > 17.11.2021 10:21:15.603 *ERROR* [[0:0:0:0:0:0:0:1] [1637162475519] GET > /foobar/foo HTTP/1.1] org.apache.sling.engine.impl.DefaultErrorHandler Error > handler failed:java.io.IOException > java.io.IOException: Error handler failed: java.lang.NullPointerException > at > org.apache.sling.servlets.resolver.internal.SlingServletResolver.handleError(SlingServletResolver.java:657) > [org.apache.sling.servlets.resolver:2.8.2] > at > org.apache.sling.servlets.resolver.internal.SlingServletResolver.handleError(SlingServletResolver.java:320) > [org.apache.sling.servlets.resolver:2.8.2] > at > org.apache.sling.engine.impl.DefaultErrorHandler.handleError(DefaultErrorHandler.java:97) > [org.apache.sling.engine:2.7.10] > at > org.apache.sling.engine.impl.SlingRequestProcessorImpl$1.render(SlingRequestProcessorImpl.java:346) > [org.apache.sling.engine:2.7.10] > at > org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:88) > [org.apache.sling.engine:2.7.10] > at > org.apache.sling.rewriter.impl.RewriterFilter.doFilter(RewriterFilter.java:87) > [org.apache.sling.rewriter:1.2.2] > at > org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:78) > [org.apache.sling.engine:2.7.10] > at org.apache.sling.i18n.impl.I18NFilter.doFilter(I18NFilter.java:131) > [org.apache.sling.i18n:2.5.14] > at > org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:78) > [org.apache.sling.engine:2.7.10] > at > org.apache.sling.engine.impl.SlingRequestProcessorImpl.handleError(SlingRequestProcessorImpl.java:353) > [org.apache.sling.engine:2.7.10] > at > org.apache.sling.engine.impl.SlingRequestProcessorImpl.doProcessRequest(SlingRequestProcessorImpl.java:167) > [org.apache.sling.engine:2.7.10] > at > org.apache.sling.engine.impl.SlingMainServlet.service(SlingMainServlet.java:250) > [org.apache.sling.engine:2.7.10] > at > org.apache.felix.http.base.internal.handler.ServletHandler.handle(ServletHandler.java:123) > [org.apache.felix.http.jetty:4.1.12] > at > org.apache.felix.http.base.internal.dispatch.InvocationChain.doFilter(InvocationChain.java:86) > [org.apache.felix.http.jetty:4.1.12] > at > com.adobe.granite.metrics.knownerrors.impl.ReportingRequestFilter.doFilter(ReportingRequestFilter.java:87) > [com.adobe.granite.metrics.knownerrors:0.0.22] > at > org.apache.felix.http.base.internal.handler.FilterHandler.handle(FilterHandler.java:142) > [org.apache.felix.http.jetty:4.1.12] > at > org.apache.felix.http.base.internal.dispatch.InvocationChain.doFilter(InvocationChain.java:81) > [org.apache.felix.http.jetty:4.1.12] > at com.adobe.granite.cors.impl.CORSFilter.doFilter(CORSFilter.java:87) > [com.adobe.granite.cors:1.0.20] > at > org.apache.felix.http.base.internal.handler.FilterHandler.handle(FilterHandler.java:142) > [org.apache.felix.http.jetty:4.1.12] > at > org.apache.felix.http.base.internal.dispatch.InvocationChain.doFilter(InvocationChain.java:81) > [org.apache.felix.http.jetty:4.1.12] > at > com.adobe.granite.license.impl.http.LicenseCheckFilter.doFilter(LicenseCheckFilter.java:301) > [com.adobe.granite.license.http:1.0.0] > at > org.apache.felix.http.base.internal.handler.FilterHandler.handle(FilterHandler.java:142) > [org.apache.felix.http.jetty:4.1.12] > at > org.apache.felix.http.base.internal.dispatch.InvocationChain.doFilter(InvocationChain.java:81) > [org.apache.felix.http.jetty:4.1.12] > at org.apache.sling.i18n.impl.I18NFilter.doFilter(I18NFilter.java:131) > [org.apache.sling.i18n:2.5.14] > at > org.apache.felix.http.base.internal.handler.FilterHandler.handle(FilterHandler.java:142) > [org.apache.felix.http.jetty:4.1.12] > at > org.apache.felix.http.base.internal.dispatch.InvocationChain.doFilter(InvocationChain.java:81) > [org.apache.felix.http.jetty:4.1.12] > at > org.apache.sling.featureflags.impl.FeatureManager.doFilter(FeatureManager.java:116) > [org.apache.sling.featureflags:1.2.2] > at >
[jira] [Closed] (SLING-11014) Update to Apache Felix Framework 7.0.3
[ https://issues.apache.org/jira/browse/SLING-11014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls closed SLING-11014. -- > Update to Apache Felix Framework 7.0.3 > -- > > Key: SLING-11014 > URL: https://issues.apache.org/jira/browse/SLING-11014 > Project: Sling > Issue Type: Improvement > Components: Launchpad >Affects Versions: Launchpad Base 2.7.4 >Reporter: Karl Pauls >Assignee: Karl Pauls >Priority: Major > Fix For: Launchpad Base 2.7.6 > > Time Spent: 10m > Remaining Estimate: 0h > > Update to Apache Felix Framework 7.0.3 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-10323) [container] feature-launcher switch base image to jre
[ https://issues.apache.org/jira/browse/SLING-10323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls closed SLING-10323. -- > [container] feature-launcher switch base image to jre > - > > Key: SLING-10323 > URL: https://issues.apache.org/jira/browse/SLING-10323 > Project: Sling > Issue Type: Improvement > Components: Feature Model >Reporter: Stefan Bischof >Assignee: Karl Pauls >Priority: Minor > Fix For: Feature Model Launcher 1.1.28 > > > Switch Base-Image of the feature-launcher-container from > adoptopenjdk/openjdk11:alpine-slim > to > adoptopenjdk/openjdk11:alpine-jre > https://github.com/apache/sling-org-apache-sling-feature-launcher/pull/26 > h1. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-10939) Don't register precompiled scripts that are missing
[ https://issues.apache.org/jira/browse/SLING-10939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls closed SLING-10939. -- > Don't register precompiled scripts that are missing > --- > > Key: SLING-10939 > URL: https://issues.apache.org/jira/browse/SLING-10939 > Project: Sling > Issue Type: Bug > Components: Scripting, Servlets >Affects Versions: Scripting Core 2.4.0, Servlets Resolver 2.9.0 >Reporter: Karl Pauls >Assignee: Karl Pauls >Priority: Major > Fix For: Scripting Core 2.4.2, Servlets Resolver 2.9.2 > > Time Spent: 50m > Remaining Estimate: 0h > > When a bundle provides resource type capabilities for scripts that turn out > to be missing an executable from the bundle (or can't be loaded) there is a > case where if the resource type extends another resource type it is possible > that a parent script is found. > When the resource type wasn't based on a script in the bundle, then this > should cause a registration of the parent script (and it does) - however, > when it was based on a script in the bundle, it shouldn't be registered (but > it is). -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-10934) Bundled scripts in the form of .. override the Sling POST Servlet
[
https://issues.apache.org/jira/browse/SLING-10934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Pauls closed SLING-10934.
--
> Bundled scripts in the form of .. override
> the Sling POST Servlet
> ---
>
> Key: SLING-10934
> URL: https://issues.apache.org/jira/browse/SLING-10934
> Project: Sling
> Issue Type: Bug
> Components: Maven Plugins and Archetypes, Scripting, Servlets
>Affects Versions: Scripting Core 2.4.0, Servlets Resolver 2.9.0, Scripting
> Bundle Maven Plugin 0.5.0
>Reporter: Karl Pauls
>Assignee: Karl Pauls
>Priority: Major
> Fix For: Scripting Core 2.4.2, Scripting Bundle Maven Plugin 0.5.2
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Currently, it is not really possible using bundled scripts to provide a
> script for a resource label with an HTTP method and at the same time a script
> for only the HTTP method. Furthermore, when providing the former, there is a
> small difference in precedence compared to scripts provided via the resource
> tree.
> In other words, it should be possible to have (for a given resource type,
> e.g. {{{}foo{}}}) a {{foo/POST.jsp}} and as well as a {{foo/foo.POST.jsp}}
> and they should have the same matching and priority like scripts provided via
> the resource tree.
> On the metadata level, this can be achieved by just adding the resource label
> as a selector to the resulting capability but to make it work at runtime, we
> need to add a match to the bundle render unit lookup.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Closed] (SLING-10927) NPE in ResolutionCache when the Service is modified
[ https://issues.apache.org/jira/browse/SLING-10927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls closed SLING-10927. -- > NPE in ResolutionCache when the Service is modified > --- > > Key: SLING-10927 > URL: https://issues.apache.org/jira/browse/SLING-10927 > Project: Sling > Issue Type: Bug >Affects Versions: Servlets Resolver 2.9.0 >Reporter: Ahmed Musallam >Assignee: Carsten Ziegeler >Priority: Major > Fix For: Servlets Resolver 2.9.2 > > Time Spent: 0.5h > Remaining Estimate: 0h > > In version 2.8.2 of the Servlet Resolver, an NPE is thrown here: > [https://github.com/apache/sling-org-apache-sling-servlets-resolver/blob/org.apache.sling.servlets.resolver-2.8.2/src/main/java/org/apache/sling/servlets/resolver/internal/resolution/ResolutionCache.java#L98] > When the component is modified. > since `cache` member is set to null on deactivate here: > [https://github.com/apache/sling-org-apache-sling-servlets-resolver/blob/org.apache.sling.servlets.resolver-2.8.2/src/main/java/org/apache/sling/servlets/resolver/internal/resolution/ResolutionCache.java#L157] > > looking at the code in version 2.9.0 the issue persist there as well./ -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-10887) Optionally allow osgi dependencies provided by a feature
[ https://issues.apache.org/jira/browse/SLING-10887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls closed SLING-10887. -- > Optionally allow osgi dependencies provided by a feature > > > Key: SLING-10887 > URL: https://issues.apache.org/jira/browse/SLING-10887 > Project: Sling > Issue Type: Improvement > Components: Maven Plugins and Archetypes >Affects Versions: JSPC Maven Plugin 2.3.0 >Reporter: Karl Pauls >Assignee: Karl Pauls >Priority: Major > Fix For: JSPC Maven Plugin 2.3.2 > > Time Spent: 3h 10m > Remaining Estimate: 0h > > When using the jspc-maven-plugin to compile against osgi bundles the current > way of just adding them as dependencies doesn't work very well as bundles can > have embedded jar files (which then don't show up on the real class path) and > obviously, just because a bundle contains a package doesn't mean it exports > it. > It would be good if we could give the jspc-maven-plugin a feature and it > would, in turn, load the classes from the resolved bundles of the feature. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-10826) Update to Felix Framework 7.0.1
[ https://issues.apache.org/jira/browse/SLING-10826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls closed SLING-10826. -- > Update to Felix Framework 7.0.1 > --- > > Key: SLING-10826 > URL: https://issues.apache.org/jira/browse/SLING-10826 > Project: Sling > Issue Type: Improvement > Components: Feature Model >Reporter: Robert Munteanu >Assignee: Robert Munteanu >Priority: Major > Fix For: Feature Model Launcher 1.1.28 > > > We should pick up on the fixes - > https://issues.apache.org/jira/issues/?jql=project%20%3D%20FELIX%20AND%20fixVersion%20%3D%20framework-7.0.1 > , mostly for Java 17 support. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-10956) Create assembly for feature launcher
[ https://issues.apache.org/jira/browse/SLING-10956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls closed SLING-10956. -- > Create assembly for feature launcher > > > Key: SLING-10956 > URL: https://issues.apache.org/jira/browse/SLING-10956 > Project: Sling > Issue Type: Improvement > Components: Feature Model >Affects Versions: Feature Model Launcher 1.1.26 >Reporter: Karl Pauls >Assignee: Karl Pauls >Priority: Major > Fix For: Feature Model Launcher 1.1.28 > > > The launcher can be extended with service loader based class path extenders. > That makes it tricky to have it inline its dependencies (especially > conditionally) as the extenders might have dependencies as well. > I think we should provide the launcher as an assembly so that we can have the > launcher jar only contain the launcher classes and provide a zip file with > everything included. > That way, one can drop in extensions (and their dependencies) into the libs > dir and manage the dependencies if required. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-10723) Update to Apache Johnzon 1.2.14
[ https://issues.apache.org/jira/browse/SLING-10723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls closed SLING-10723. -- > Update to Apache Johnzon 1.2.14 > --- > > Key: SLING-10723 > URL: https://issues.apache.org/jira/browse/SLING-10723 > Project: Sling > Issue Type: Improvement > Components: Feature Model, Maven Plugins and Archetypes >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler >Priority: Major > Fix For: Feature Model Launcher 1.1.22, slingfeature-maven-plugin > 1.5.12, Content-Package to Feature Model Converter 1.1.8, Feature Model API > Regions Extension 1.3.10, Feature Model Analyser 1.3.34, Feature Model > 1.2.30, Commons Johnzon 1.2.14 > > > It seems we have different versions of the johnzon library in various feature > model related projects. In order to get bug fixes/improvements included we > should update all of them to the latest version 1.2.14 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-10867) The launcher should fail fast when it can't create parent directories for the application feature file
[ https://issues.apache.org/jira/browse/SLING-10867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls closed SLING-10867. -- > The launcher should fail fast when it can't create parent directories for the > application feature file > -- > > Key: SLING-10867 > URL: https://issues.apache.org/jira/browse/SLING-10867 > Project: Sling > Issue Type: Bug > Components: Feature Model >Reporter: Robert Munteanu >Assignee: Robert Munteanu >Priority: Major > Fix For: Feature Model Launcher 1.1.28 > > > When the parent directories can't be created the problem is silently ignored. > It will fail immediately later when trying to create the application feature > file but the cause will be less clear. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-11015) Update to Felix Framework 7.0.3
[ https://issues.apache.org/jira/browse/SLING-11015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls closed SLING-11015. -- > Update to Felix Framework 7.0.3 > --- > > Key: SLING-11015 > URL: https://issues.apache.org/jira/browse/SLING-11015 > Project: Sling > Issue Type: Improvement > Components: Feature Model >Reporter: Karl Pauls >Assignee: Karl Pauls >Priority: Major > Fix For: Feature Model Launcher 1.1.28 > > > Update to Felix Framework 7.0.3 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (SLING-11022) Commons Classloaders should be parallel capable where possible
Karl Pauls created SLING-11022: -- Summary: Commons Classloaders should be parallel capable where possible Key: SLING-11022 URL: https://issues.apache.org/jira/browse/SLING-11022 Project: Sling Issue Type: Improvement Components: Commons Affects Versions: File System ClassLoader 1.0.14, Commons ClassLoader 1.4.4 Reporter: Karl Pauls Assignee: Karl Pauls Fix For: File System ClassLoader 1.0.16, Commons ClassLoader 1.4.6 We are not registering our class loaders in commons class loader and commons file system class loader as parallel capable - as a consequence, we are synchronizing on the global lock per class loader which can cause unnecessary contention. We should register them as parallel capable and explicitly use the class loading lock where necessary. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (SLING-8039) Inline logback jars in commons log
[ https://issues.apache.org/jira/browse/SLING-8039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17461420#comment-17461420 ] Karl Pauls commented on SLING-8039: --- and yes, [~rombert] - current master doesn't have it embedded anymore as far as I can see (didn't test if it is still working but the jar is gone) - thanks! > Inline logback jars in commons log > -- > > Key: SLING-8039 > URL: https://issues.apache.org/jira/browse/SLING-8039 > Project: Sling > Issue Type: Improvement > Components: Commons >Affects Versions: Commons Log 5.1.10 >Reporter: Karl Pauls >Priority: Minor > Fix For: Commons Log 5.2.2 > > > It be nice to inline the embeded logback-classic-1.2.3.jar and > logback-core-1.2.3.jar to avoid having them extracted into the bundle cache. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (SLING-8039) Inline logback jars in commons log
[ https://issues.apache.org/jira/browse/SLING-8039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17461416#comment-17461416 ] Karl Pauls commented on SLING-8039: --- If we don't have to embed them that would be even better I think - I just created the issue to not have the embedded jar but not embedding at all would solve that as well. > Inline logback jars in commons log > -- > > Key: SLING-8039 > URL: https://issues.apache.org/jira/browse/SLING-8039 > Project: Sling > Issue Type: Improvement > Components: Commons >Affects Versions: Commons Log 5.1.10 >Reporter: Karl Pauls >Priority: Minor > Fix For: Commons Log 5.2.2 > > > It be nice to inline the embeded logback-classic-1.2.3.jar and > logback-core-1.2.3.jar to avoid having them extracted into the bundle cache. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (SLING-10929) CPConverter - error messages can be obfuscated
[ https://issues.apache.org/jira/browse/SLING-10929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls resolved SLING-10929. Resolution: Fixed > CPConverter - error messages can be obfuscated > -- > > Key: SLING-10929 > URL: https://issues.apache.org/jira/browse/SLING-10929 > Project: Sling > Issue Type: Improvement > Components: Content-Package to Feature Model Converter >Affects Versions: Content-Package to Feature Model Converter 1.1.10 >Reporter: Niek Raaijmakers >Assignee: Niek Raaijmakers >Priority: Minor > Fix For: Content-Package to Feature Model Converter 1.1.12 > > > Currently, when performing a CPConversion, if the customer has wrong code, > sometimes the exception can be very obfuscated. > This gives the customer no chance to fix their error easily: > In this example a xml file is empty: > [ERROR] Unable to convert content-package > [/tmp/packages/???.ui.content-1.28.0-SNAPSHOT.zip, > /tmp/packages/???.ui.apps-1.28.0-SNAPSHOT.zip]: Premature end of file. > We would like a path to be provided in the exception so the customer can take > a look there. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (SLING-10706) Order of selectors not kept
[ https://issues.apache.org/jira/browse/SLING-10706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls updated SLING-10706: --- Fix Version/s: Scripting Bundle Maven Plugin 0.5.4 (was: Scripting Bundle Maven Plugin 0.5.2) > Order of selectors not kept > --- > > Key: SLING-10706 > URL: https://issues.apache.org/jira/browse/SLING-10706 > Project: Sling > Issue Type: Bug > Components: Maven Plugins and Archetypes >Affects Versions: Scripting Bundle Maven Plugin 0.3.0 >Reporter: Konrad Windszus >Priority: Major > Fix For: Scripting Bundle Maven Plugin 0.5.4 > > > The selectors used for registration of script/servlets have an order: Only if > they appear in the given order the script/servlet matches > (https://sling.apache.org/documentation/the-sling-engine/servlets.html#servlet-registration). > The order is potentially lost, though during the generation of the > capabilities headers as the code is using Sets internally. > Also it is totally valid to register a script to "myselector.myselector" > which cannot be expressed with Sets either. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (SLING-10821) Support resource types with characters invalid in zip entry names
[ https://issues.apache.org/jira/browse/SLING-10821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls updated SLING-10821: --- Fix Version/s: Scripting Bundle Maven Plugin 0.5.4 (was: Scripting Bundle Maven Plugin 0.5.2) > Support resource types with characters invalid in zip entry names > - > > Key: SLING-10821 > URL: https://issues.apache.org/jira/browse/SLING-10821 > Project: Sling > Issue Type: Bug > Components: Maven Plugins and Archetypes >Affects Versions: Scripting Bundle Maven Plugin 0.4.0 >Reporter: Konrad Windszus >Priority: Major > Fix For: Scripting Bundle Maven Plugin 0.5.4 > > > Sling does not limit the character set to use for a resource type. For > example a colon is perfectly valid (also in JCR names). As the resource type > is directly determined from the zip entry name but the filesystem imposes > several limitations > (https://en.wikipedia.org/wiki/Filename#Comparison_of_filename_limitations) > some kind of escaping need to be supported to allow giving arbitrary resource > types just via path name. Filevault Content Packages for example leverage > these escaping rules: > http://jackrabbit.apache.org/filevault/vaultfs.html#Filename_escaping. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (SLING-11015) Update to Felix Framework 7.0.3
[ https://issues.apache.org/jira/browse/SLING-11015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls resolved SLING-11015. Resolution: Fixed Done in https://github.com/apache/sling-org-apache-sling-feature-launcher/pull/34 > Update to Felix Framework 7.0.3 > --- > > Key: SLING-11015 > URL: https://issues.apache.org/jira/browse/SLING-11015 > Project: Sling > Issue Type: Improvement > Components: Feature Model >Reporter: Karl Pauls >Assignee: Karl Pauls >Priority: Major > Fix For: Feature Model Launcher 1.1.28 > > > Update to Felix Framework 7.0.3 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (SLING-11015) Update to Felix Framework 7.0.3
Karl Pauls created SLING-11015: -- Summary: Update to Felix Framework 7.0.3 Key: SLING-11015 URL: https://issues.apache.org/jira/browse/SLING-11015 Project: Sling Issue Type: Improvement Components: Feature Model Reporter: Karl Pauls Assignee: Karl Pauls Fix For: Feature Model Launcher 1.1.28 Update to Felix Framework 7.0.3 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (SLING-10323) [container] feature-launcher switch base image to jre
[ https://issues.apache.org/jira/browse/SLING-10323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls updated SLING-10323: --- Fix Version/s: Feature Model Launcher 1.1.28 > [container] feature-launcher switch base image to jre > - > > Key: SLING-10323 > URL: https://issues.apache.org/jira/browse/SLING-10323 > Project: Sling > Issue Type: Improvement > Components: Feature Model >Reporter: Stefan Bischof >Priority: Minor > Fix For: Feature Model Launcher 1.1.28 > > > Switch Base-Image of the feature-launcher-container from > adoptopenjdk/openjdk11:alpine-slim > to > adoptopenjdk/openjdk11:alpine-jre > https://github.com/apache/sling-org-apache-sling-feature-launcher/pull/26 > h1. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (SLING-10323) [container] feature-launcher switch base image to jre
[ https://issues.apache.org/jira/browse/SLING-10323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17460649#comment-17460649 ] Karl Pauls commented on SLING-10323: I applied your PR - Thanks! > [container] feature-launcher switch base image to jre > - > > Key: SLING-10323 > URL: https://issues.apache.org/jira/browse/SLING-10323 > Project: Sling > Issue Type: Improvement > Components: Feature Model >Reporter: Stefan Bischof >Assignee: Karl Pauls >Priority: Minor > Fix For: Feature Model Launcher 1.1.28 > > > Switch Base-Image of the feature-launcher-container from > adoptopenjdk/openjdk11:alpine-slim > to > adoptopenjdk/openjdk11:alpine-jre > https://github.com/apache/sling-org-apache-sling-feature-launcher/pull/26 > h1. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (SLING-10323) [container] feature-launcher switch base image to jre
[ https://issues.apache.org/jira/browse/SLING-10323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls reassigned SLING-10323: -- Assignee: Karl Pauls > [container] feature-launcher switch base image to jre > - > > Key: SLING-10323 > URL: https://issues.apache.org/jira/browse/SLING-10323 > Project: Sling > Issue Type: Improvement > Components: Feature Model >Reporter: Stefan Bischof >Assignee: Karl Pauls >Priority: Minor > Fix For: Feature Model Launcher 1.1.28 > > > Switch Base-Image of the feature-launcher-container from > adoptopenjdk/openjdk11:alpine-slim > to > adoptopenjdk/openjdk11:alpine-jre > https://github.com/apache/sling-org-apache-sling-feature-launcher/pull/26 > h1. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (SLING-10323) [container] feature-launcher switch base image to jre
[ https://issues.apache.org/jira/browse/SLING-10323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls resolved SLING-10323. Resolution: Fixed > [container] feature-launcher switch base image to jre > - > > Key: SLING-10323 > URL: https://issues.apache.org/jira/browse/SLING-10323 > Project: Sling > Issue Type: Improvement > Components: Feature Model >Reporter: Stefan Bischof >Priority: Minor > Fix For: Feature Model Launcher 1.1.28 > > > Switch Base-Image of the feature-launcher-container from > adoptopenjdk/openjdk11:alpine-slim > to > adoptopenjdk/openjdk11:alpine-jre > https://github.com/apache/sling-org-apache-sling-feature-launcher/pull/26 > h1. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (SLING-11014) Update to Apache Felix Framework 7.0.3
[ https://issues.apache.org/jira/browse/SLING-11014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls resolved SLING-11014. Resolution: Fixed Done in https://github.com/apache/sling-org-apache-sling-launchpad-base/pull/12 > Update to Apache Felix Framework 7.0.3 > -- > > Key: SLING-11014 > URL: https://issues.apache.org/jira/browse/SLING-11014 > Project: Sling > Issue Type: Improvement > Components: Launchpad >Affects Versions: Launchpad Base 2.7.4 >Reporter: Karl Pauls >Assignee: Karl Pauls >Priority: Major > Fix For: Launchpad Base 2.7.6 > > Time Spent: 10m > Remaining Estimate: 0h > > Update to Apache Felix Framework 7.0.3 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (SLING-11014) Update to Apache Felix Framework 7.0.3
Karl Pauls created SLING-11014: -- Summary: Update to Apache Felix Framework 7.0.3 Key: SLING-11014 URL: https://issues.apache.org/jira/browse/SLING-11014 Project: Sling Issue Type: Improvement Components: Launchpad Affects Versions: Launchpad Base 2.7.4 Reporter: Karl Pauls Assignee: Karl Pauls Fix For: Launchpad Base 2.7.6 Update to Apache Felix Framework 7.0.3 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (SLING-10887) Optionally allow osgi dependencies provided by a feature
[ https://issues.apache.org/jira/browse/SLING-10887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls resolved SLING-10887. Resolution: Fixed > Optionally allow osgi dependencies provided by a feature > > > Key: SLING-10887 > URL: https://issues.apache.org/jira/browse/SLING-10887 > Project: Sling > Issue Type: Improvement > Components: Maven Plugins and Archetypes >Affects Versions: JSPC Maven Plugin 2.3.0 >Reporter: Karl Pauls >Assignee: Karl Pauls >Priority: Major > Fix For: JSPC Maven Plugin 2.3.2 > > Time Spent: 3h 10m > Remaining Estimate: 0h > > When using the jspc-maven-plugin to compile against osgi bundles the current > way of just adding them as dependencies doesn't work very well as bundles can > have embedded jar files (which then don't show up on the real class path) and > obviously, just because a bundle contains a package doesn't mean it exports > it. > It would be good if we could give the jspc-maven-plugin a feature and it > would, in turn, load the classes from the resolved bundles of the feature. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (SLING-10956) Create assembly for feature launcher
[ https://issues.apache.org/jira/browse/SLING-10956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls resolved SLING-10956. Resolution: Fixed > Create assembly for feature launcher > > > Key: SLING-10956 > URL: https://issues.apache.org/jira/browse/SLING-10956 > Project: Sling > Issue Type: Improvement > Components: Feature Model >Affects Versions: Feature Model Launcher 1.1.26 >Reporter: Karl Pauls >Assignee: Karl Pauls >Priority: Major > Fix For: Feature Model Launcher 1.1.28 > > > The launcher can be extended with service loader based class path extenders. > That makes it tricky to have it inline its dependencies (especially > conditionally) as the extenders might have dependencies as well. > I think we should provide the launcher as an assembly so that we can have the > launcher jar only contain the launcher classes and provide a zip file with > everything included. > That way, one can drop in extensions (and their dependencies) into the libs > dir and manage the dependencies if required. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (SLING-10956) Create assembly for feature launcher
Karl Pauls created SLING-10956: -- Summary: Create assembly for feature launcher Key: SLING-10956 URL: https://issues.apache.org/jira/browse/SLING-10956 Project: Sling Issue Type: Improvement Components: Feature Model Affects Versions: Feature Model Launcher 1.1.26 Reporter: Karl Pauls Assignee: Karl Pauls Fix For: Feature Model Launcher 1.1.28 The launcher can be extended with service loader based class path extenders. That makes it tricky to have it inline its dependencies (especially conditionally) as the extenders might have dependencies as well. I think we should provide the launcher as an assembly so that we can have the launcher jar only contain the launcher classes and provide a zip file with everything included. That way, one can drop in extensions (and their dependencies) into the libs dir and manage the dependencies if required. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (SLING-10938) Exception thrown on Sling Starter shutdown in JobManagerConfiguration
[
https://issues.apache.org/jira/browse/SLING-10938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17449707#comment-17449707
]
Karl Pauls commented on SLING-10938:
Can't see the service user mapper involved in these, no?
> Exception thrown on Sling Starter shutdown in JobManagerConfiguration
> -
>
> Key: SLING-10938
> URL: https://issues.apache.org/jira/browse/SLING-10938
> Project: Sling
> Issue Type: Task
> Components: Event
>Affects Versions: Event 4.2.24
>Reporter: Michał Goliński
>Priority: Minor
> Attachments: error.log, stacktrace.txt, stdout.txt
>
>
> On stopping the Sling Starter with Ctrl+C we can occasionally see the
> following stacktrace:
> {code:java}
> ERROR : bundle org.apache.sling.event:4.2.20
> (151)[org.apache.sling.event.impl.jobs.config.JobManagerConfiguration(247)] :
> The activate method has thrown an exception
> java.lang.IllegalArgumentException: Can't create child on a synthetic root
> at
> org.apache.sling.resourceresolver.impl.ResourceResolverImpl.create(ResourceResolverImpl.java:1006)
> ...
> at
> org.apache.sling.api.resource.ResourceUtil.getOrCreateResource(ResourceUtil.java:571)
> at
> org.apache.sling.event.impl.support.ResourceHelper.getOrCreateBasePath(ResourceHelper.java:258)
> at
> org.apache.sling.event.impl.jobs.config.JobManagerConfiguration.activate(JobManagerConfiguration.java:225)
> ...
> at
> org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.executeServiceRegistrations(ServiceUserMapperImpl.java:439)
> at
> org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.lambda$executeServiceRegistrationsAsync$0(ServiceUserMapperImpl.java:406)
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
> at java.base/java.lang.Thread.run(Thread.java:833)
> {code}
> This happens also with bundle version 4.2.24.
> This doesn't happen every time, but I've seen up to seven of these at a time
> (the number of stacktraces changes), see the attached file. This might be
> similar to SLING-10204 , although in the debugger I can see the
> ServiceUserMapped being mentioned, not ResourceResolverFactory.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (SLING-10938) Exception thrown on Sling Starter shutdown in JobManagerConfiguration
[
https://issues.apache.org/jira/browse/SLING-10938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17449586#comment-17449586
]
Karl Pauls commented on SLING-10938:
[~golinski] - would it be possible to get the error.log for this case?
> Exception thrown on Sling Starter shutdown in JobManagerConfiguration
> -
>
> Key: SLING-10938
> URL: https://issues.apache.org/jira/browse/SLING-10938
> Project: Sling
> Issue Type: Task
> Components: Event
>Affects Versions: Event 4.2.24
>Reporter: Michał Goliński
>Priority: Minor
> Attachments: stacktrace.txt
>
>
> On stopping the Sling Starter with Ctrl+C we can occasionally see the
> following stacktrace:
> {code:java}
> ERROR : bundle org.apache.sling.event:4.2.20
> (151)[org.apache.sling.event.impl.jobs.config.JobManagerConfiguration(247)] :
> The activate method has thrown an exception
> java.lang.IllegalArgumentException: Can't create child on a synthetic root
> at
> org.apache.sling.resourceresolver.impl.ResourceResolverImpl.create(ResourceResolverImpl.java:1006)
> ...
> at
> org.apache.sling.api.resource.ResourceUtil.getOrCreateResource(ResourceUtil.java:571)
> at
> org.apache.sling.event.impl.support.ResourceHelper.getOrCreateBasePath(ResourceHelper.java:258)
> at
> org.apache.sling.event.impl.jobs.config.JobManagerConfiguration.activate(JobManagerConfiguration.java:225)
> ...
> at
> org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.executeServiceRegistrations(ServiceUserMapperImpl.java:439)
> at
> org.apache.sling.serviceusermapping.impl.ServiceUserMapperImpl.lambda$executeServiceRegistrationsAsync$0(ServiceUserMapperImpl.java:406)
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
> at java.base/java.lang.Thread.run(Thread.java:833)
> {code}
> This happens also with bundle version 4.2.24.
> This doesn't happen every time, but I've seen up to seven of these at a time
> (the number of stacktraces changes), see the attached file. This might be
> similar to SLING-10204 , although in the debugger I can see the
> ServiceUserMapped being mentioned, not ResourceResolverFactory.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Resolved] (SLING-10939) Don't register precompiled scripts that are missing
[ https://issues.apache.org/jira/browse/SLING-10939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls resolved SLING-10939. Resolution: Fixed > Don't register precompiled scripts that are missing > --- > > Key: SLING-10939 > URL: https://issues.apache.org/jira/browse/SLING-10939 > Project: Sling > Issue Type: Bug > Components: Scripting, Servlets >Affects Versions: Scripting Core 2.4.0, Servlets Resolver 2.9.0 >Reporter: Karl Pauls >Assignee: Karl Pauls >Priority: Major > Fix For: Scripting Core 2.4.2, Servlets Resolver 2.9.2 > > Time Spent: 50m > Remaining Estimate: 0h > > When a bundle provides resource type capabilities for scripts that turn out > to be missing an executable from the bundle (or can't be loaded) there is a > case where if the resource type extends another resource type it is possible > that a parent script is found. > When the resource type wasn't based on a script in the bundle, then this > should cause a registration of the parent script (and it does) - however, > when it was based on a script in the bundle, it shouldn't be registered (but > it is). -- This message was sent by Atlassian Jira (v8.20.1#820001)
