[GitHub] [sling-org-apache-sling-caconfig-integration-tests] sonarcloud[bot] removed a comment on pull request #1: SLING-11114 update SLING API to 2.21.0
sonarcloud[bot] removed a comment on pull request #1: URL: https://github.com/apache/sling-org-apache-sling-caconfig-integration-tests/pull/1#issuecomment-1071139069 Kudos, SonarCloud Quality Gate passed!  [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-caconfig-integration-tests=1=false=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-caconfig-integration-tests=1=false=BUG) [0 Bugs](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-caconfig-integration-tests=1=false=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-caconfig-integration-tests=1=false=VULNERABILITY) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-caconfig-integration-tests=1=false=VULNERABILITY) [0 Vulnerabilities](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-caconfig-integration-tests=1=false=VULNERABILITY) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-caconfig-integration-tests=1=false=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-caconfig-integration-tests=1=false=SECURITY_HOTSPOT) [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-caconfig-integration-tests=1=false=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-caconfig-integration-tests=1=false=CODE_SMELL) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-caconfig-integration-tests=1=false=CODE_SMELL) [0 Code Smells](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-caconfig-integration-tests=1=false=CODE_SMELL) [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-caconfig-integration-tests=1) No Coverage information [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-caconfig-integration-tests=1=new_duplicated_lines_density=list) [0.0% Duplication](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-caconfig-integration-tests=1=new_duplicated_lines_density=list) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [sling-org-apache-sling-caconfig-integration-tests] sonarcloud[bot] commented on pull request #1: SLING-11114 update SLING API to 2.21.0
sonarcloud[bot] commented on pull request #1: URL: https://github.com/apache/sling-org-apache-sling-caconfig-integration-tests/pull/1#issuecomment-1072902759 Kudos, SonarCloud Quality Gate passed!  [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-caconfig-integration-tests=1=false=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-caconfig-integration-tests=1=false=BUG) [0 Bugs](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-caconfig-integration-tests=1=false=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-caconfig-integration-tests=1=false=VULNERABILITY) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-caconfig-integration-tests=1=false=VULNERABILITY) [0 Vulnerabilities](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-caconfig-integration-tests=1=false=VULNERABILITY) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-caconfig-integration-tests=1=false=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-caconfig-integration-tests=1=false=SECURITY_HOTSPOT) [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-caconfig-integration-tests=1=false=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-caconfig-integration-tests=1=false=CODE_SMELL) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-caconfig-integration-tests=1=false=CODE_SMELL) [0 Code Smells](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-caconfig-integration-tests=1=false=CODE_SMELL) [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-caconfig-integration-tests=1) No Coverage information [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-caconfig-integration-tests=1=new_duplicated_lines_density=list) [0.0% Duplication](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-caconfig-integration-tests=1=new_duplicated_lines_density=list) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [sling-org-apache-sling-jcr-contentloader] enapps-enorman commented on pull request #13: SLING-11203: Introduce requireImportProvider directive
enapps-enorman commented on pull request #13: URL: https://github.com/apache/sling-org-apache-sling-jcr-contentloader/pull/13#issuecomment-1072860927 closing. Replaced by PR #15 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [sling-org-apache-sling-jcr-contentloader] enapps-enorman closed pull request #13: SLING-11203: Introduce requireImportProvider directive
enapps-enorman closed pull request #13: URL: https://github.com/apache/sling-org-apache-sling-jcr-contentloader/pull/13 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (SLING-11203) Content Loader: Introduce requireImportProvider directive
[
https://issues.apache.org/jira/browse/SLING-11203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Norman updated SLING-11203:
Description: in context of SLING-11189 [~enorman] proposed the introduction
of a {{requireImportProvider}} directive which allows bundles to declare on
which import provider implementations they actually depend. with this, it can
be ensured a bundle's content is not imported in an inconsistent state when one
of the required providers is not (yet) available. (was: in context of
SLING-11189 [~enorman] proposed the introduction of a {{requireImportProvider}}
directive which allows bundles to declare on which import provider
implementations they actually depend. with this, it can be ensured a bundle's
content is not imported in an inconsistent state when one of the required
providers is not (yet) available.
for backward compatibility this paired with a configurable list of default
import providers which is used for bundles which do not declare their own list
of via {{requireImportProvider}}.)
> Content Loader: Introduce requireImportProvider directive
> -
>
> Key: SLING-11203
> URL: https://issues.apache.org/jira/browse/SLING-11203
> Project: Sling
> Issue Type: New Feature
> Components: Extensions
>Reporter: Stefan Seifert
>Assignee: Eric Norman
>Priority: Major
> Fix For: JCR ContentLoader 2.5.4
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> in context of SLING-11189 [~enorman] proposed the introduction of a
> {{requireImportProvider}} directive which allows bundles to declare on which
> import provider implementations they actually depend. with this, it can be
> ensured a bundle's content is not imported in an inconsistent state when one
> of the required providers is not (yet) available.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (SLING-11203) Content Loader: Introduce requireImportProvider directive
[
https://issues.apache.org/jira/browse/SLING-11203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Norman updated SLING-11203:
Fix Version/s: JCR ContentLoader 2.5.4
> Content Loader: Introduce requireImportProvider directive
> -
>
> Key: SLING-11203
> URL: https://issues.apache.org/jira/browse/SLING-11203
> Project: Sling
> Issue Type: New Feature
> Components: Extensions
>Reporter: Stefan Seifert
>Assignee: Eric Norman
>Priority: Major
> Fix For: JCR ContentLoader 2.5.4
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> in context of SLING-11189 [~enorman] proposed the introduction of a
> {{requireImportProvider}} directive which allows bundles to declare on which
> import provider implementations they actually depend. with this, it can be
> ensured a bundle's content is not imported in an inconsistent state when one
> of the required providers is not (yet) available.
> for backward compatibility this paired with a configurable list of default
> import providers which is used for bundles which do not declare their own
> list of via {{requireImportProvider}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (SLING-11203) Content Loader: Introduce requireImportProvider directive
[
https://issues.apache.org/jira/browse/SLING-11203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Norman reassigned SLING-11203:
---
Assignee: Eric Norman
> Content Loader: Introduce requireImportProvider directive
> -
>
> Key: SLING-11203
> URL: https://issues.apache.org/jira/browse/SLING-11203
> Project: Sling
> Issue Type: New Feature
> Components: Extensions
>Reporter: Stefan Seifert
>Assignee: Eric Norman
>Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> in context of SLING-11189 [~enorman] proposed the introduction of a
> {{requireImportProvider}} directive which allows bundles to declare on which
> import provider implementations they actually depend. with this, it can be
> ensured a bundle's content is not imported in an inconsistent state when one
> of the required providers is not (yet) available.
> for backward compatibility this paired with a configurable list of default
> import providers which is used for bundles which do not declare their own
> list of via {{requireImportProvider}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (SLING-11203) Content Loader: Introduce requireImportProvider directive
[
https://issues.apache.org/jira/browse/SLING-11203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17509092#comment-17509092
]
Eric Norman commented on SLING-11203:
-
Replaced PR #13 with PR #15 to fix conflicts, refactor the tests and remove the
"default import providers" support as that seems less relevant after the
SLING-11189 changes.
> Content Loader: Introduce requireImportProvider directive
> -
>
> Key: SLING-11203
> URL: https://issues.apache.org/jira/browse/SLING-11203
> Project: Sling
> Issue Type: New Feature
> Components: Extensions
>Reporter: Stefan Seifert
>Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> in context of SLING-11189 [~enorman] proposed the introduction of a
> {{requireImportProvider}} directive which allows bundles to declare on which
> import provider implementations they actually depend. with this, it can be
> ensured a bundle's content is not imported in an inconsistent state when one
> of the required providers is not (yet) available.
> for backward compatibility this paired with a configurable list of default
> import providers which is used for bundles which do not declare their own
> list of via {{requireImportProvider}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[GitHub] [sling-org-apache-sling-jcr-contentloader] sonarcloud[bot] commented on pull request #15: SLING-11203 Introduce requireImportProvider directive
sonarcloud[bot] commented on pull request #15: URL: https://github.com/apache/sling-org-apache-sling-jcr-contentloader/pull/15#issuecomment-1072859128 Kudos, SonarCloud Quality Gate passed!  [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-contentloader=15=false=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-contentloader=15=false=BUG) [0 Bugs](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-contentloader=15=false=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-contentloader=15=false=VULNERABILITY) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-contentloader=15=false=VULNERABILITY) [0 Vulnerabilities](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-contentloader=15=false=VULNERABILITY) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-jcr-contentloader=15=false=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-jcr-contentloader=15=false=SECURITY_HOTSPOT) [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-jcr-contentloader=15=false=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-contentloader=15=false=CODE_SMELL) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-contentloader=15=false=CODE_SMELL) [2 Code Smells](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-contentloader=15=false=CODE_SMELL) [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-jcr-contentloader=15=new_coverage=list) [85.9% Coverage](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-jcr-contentloader=15=new_coverage=list) [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-jcr-contentloader=15=new_duplicated_lines_density=list) [0.0% Duplication](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-jcr-contentloader=15=new_duplicated_lines_density=list) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [sling-org-apache-sling-jcr-contentloader] enapps-enorman opened a new pull request #15: SLING-11203 Introduce requireImportProvider directive
enapps-enorman opened a new pull request #15: URL: https://github.com/apache/sling-org-apache-sling-jcr-contentloader/pull/15 A declared requireImportProvider directive so the author can ensure that the files are processed as intended -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Resolved] (SLING-10585) Add support for invalidation requests
[
https://issues.apache.org/jira/browse/SLING-10585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothee Maret resolved SLING-10585.
Resolution: Fixed
> Add support for invalidation requests
> -
>
> Key: SLING-10585
> URL: https://issues.apache.org/jira/browse/SLING-10585
> Project: Sling
> Issue Type: New Feature
> Components: Content Distribution
>Reporter: Timothee Maret
>Assignee: Roxana-Elena Balasoiu
>Priority: Major
> Fix For: Content Distribution Journal Core 0.1.26, Content
> Distribution API 0.7.0, Content Distribution Journal Messages 0.5.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Caching invalidation is typically triggered by content distribution, after
> processing an `ADD` or `DELETE` distribution request. When distributing
> referenced content, invalidation must also include on the referencing
> resources. To support this use case, we'll add support for a new type of
> distribution request that invalidates the caches without importing content.
> To support this, the org.apache.sling.distribution.DistributionRequestType
> API will be extended with
> {code:java}
> /**
> * Action type for invalidating content
> */
> INVALIDATE,
> {code}
> The PackageMessage.ReqType will be extended with the new INVALIDATION type.
> The DistributionPublisher will handle the invalidation distribution requests
> by sending a package message with the INVALIDATION type and no payload (like
> the DELETE package messages).
> The DistributionSubscriber will process invalidation messages by raising
> imported events and invoking the import post processors.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (SLING-10585) Add support for invalidation requests
[
https://issues.apache.org/jira/browse/SLING-10585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothee Maret reassigned SLING-10585:
--
Assignee: Roxana-Elena Balasoiu (was: Timothee Maret)
> Add support for invalidation requests
> -
>
> Key: SLING-10585
> URL: https://issues.apache.org/jira/browse/SLING-10585
> Project: Sling
> Issue Type: New Feature
> Components: Content Distribution
>Reporter: Timothee Maret
>Assignee: Roxana-Elena Balasoiu
>Priority: Major
> Fix For: Content Distribution Journal Core 0.1.26, Content
> Distribution API 0.7.0, Content Distribution Journal Messages 0.5.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Caching invalidation is typically triggered by content distribution, after
> processing an `ADD` or `DELETE` distribution request. When distributing
> referenced content, invalidation must also include on the referencing
> resources. To support this use case, we'll add support for a new type of
> distribution request that invalidates the caches without importing content.
> To support this, the org.apache.sling.distribution.DistributionRequestType
> API will be extended with
> {code:java}
> /**
> * Action type for invalidating content
> */
> INVALIDATE,
> {code}
> The PackageMessage.ReqType will be extended with the new INVALIDATION type.
> The DistributionPublisher will handle the invalidation distribution requests
> by sending a package message with the INVALIDATION type and no payload (like
> the DELETE package messages).
> The DistributionSubscriber will process invalidation messages by raising
> imported events and invoking the import post processors.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (SLING-10585) Add support for invalidation requests
[
https://issues.apache.org/jira/browse/SLING-10585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothee Maret updated SLING-10585:
---
Fix Version/s: Content Distribution Journal Messages 0.5.0
> Add support for invalidation requests
> -
>
> Key: SLING-10585
> URL: https://issues.apache.org/jira/browse/SLING-10585
> Project: Sling
> Issue Type: New Feature
> Components: Content Distribution
>Reporter: Timothee Maret
>Assignee: Timothee Maret
>Priority: Major
> Fix For: Content Distribution Journal Core 0.1.26, Content
> Distribution API 0.7.0, Content Distribution Journal Messages 0.5.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Caching invalidation is typically triggered by content distribution, after
> processing an `ADD` or `DELETE` distribution request. When distributing
> referenced content, invalidation must also include on the referencing
> resources. To support this use case, we'll add support for a new type of
> distribution request that invalidates the caches without importing content.
> To support this, the org.apache.sling.distribution.DistributionRequestType
> API will be extended with
> {code:java}
> /**
> * Action type for invalidating content
> */
> INVALIDATE,
> {code}
> The PackageMessage.ReqType will be extended with the new INVALIDATION type.
> The DistributionPublisher will handle the invalidation distribution requests
> by sending a package message with the INVALIDATION type and no payload (like
> the DELETE package messages).
> The DistributionSubscriber will process invalidation messages by raising
> imported events and invoking the import post processors.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (SLING-10585) Add support for invalidation requests
[
https://issues.apache.org/jira/browse/SLING-10585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothee Maret updated SLING-10585:
---
Fix Version/s: Content Distribution API 0.7.0
> Add support for invalidation requests
> -
>
> Key: SLING-10585
> URL: https://issues.apache.org/jira/browse/SLING-10585
> Project: Sling
> Issue Type: New Feature
> Components: Content Distribution
>Reporter: Timothee Maret
>Assignee: Timothee Maret
>Priority: Major
> Fix For: Content Distribution Journal Core 0.1.26, Content
> Distribution API 0.7.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Caching invalidation is typically triggered by content distribution, after
> processing an `ADD` or `DELETE` distribution request. When distributing
> referenced content, invalidation must also include on the referencing
> resources. To support this use case, we'll add support for a new type of
> distribution request that invalidates the caches without importing content.
> To support this, the org.apache.sling.distribution.DistributionRequestType
> API will be extended with
> {code:java}
> /**
> * Action type for invalidating content
> */
> INVALIDATE,
> {code}
> The PackageMessage.ReqType will be extended with the new INVALIDATION type.
> The DistributionPublisher will handle the invalidation distribution requests
> by sending a package message with the INVALIDATION type and no payload (like
> the DELETE package messages).
> The DistributionSubscriber will process invalidation messages by raising
> imported events and invoking the import post processors.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (SLING-10585) Add support for invalidation requests
[
https://issues.apache.org/jira/browse/SLING-10585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17509072#comment-17509072
]
Timothee Maret commented on SLING-10585:
Merged PR
[#101|https://github.com/apache/sling-org-apache-sling-distribution-journal/pull/101],
thank you [~balasoiu]!
> Add support for invalidation requests
> -
>
> Key: SLING-10585
> URL: https://issues.apache.org/jira/browse/SLING-10585
> Project: Sling
> Issue Type: New Feature
> Components: Content Distribution
>Reporter: Timothee Maret
>Assignee: Timothee Maret
>Priority: Major
> Fix For: Content Distribution Journal Core 0.1.26
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Caching invalidation is typically triggered by content distribution, after
> processing an `ADD` or `DELETE` distribution request. When distributing
> referenced content, invalidation must also include on the referencing
> resources. To support this use case, we'll add support for a new type of
> distribution request that invalidates the caches without importing content.
> To support this, the org.apache.sling.distribution.DistributionRequestType
> API will be extended with
> {code:java}
> /**
> * Action type for invalidating content
> */
> INVALIDATE,
> {code}
> The PackageMessage.ReqType will be extended with the new INVALIDATION type.
> The DistributionPublisher will handle the invalidation distribution requests
> by sending a package message with the INVALIDATION type and no payload (like
> the DELETE package messages).
> The DistributionSubscriber will process invalidation messages by raising
> imported events and invoking the import post processors.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Resolved] (SLING-11217) Website publish job fails to run after adding the Sling 12 java docs
[
https://issues.apache.org/jira/browse/SLING-11217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu resolved SLING-11217.
-
Resolution: Fixed
Fixed with manual push.
> Website publish job fails to run after adding the Sling 12 java docs
>
>
> Key: SLING-11217
> URL: https://issues.apache.org/jira/browse/SLING-11217
> Project: Sling
> Issue Type: Bug
> Components: Documentation, Site
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>Priority: Major
>
> The Sling Site Jenkins jobs currently fails ( e.g.
> https://ci-builds.apache.org/job/Sling/job/modules/job/sling-site/job/master/441/console
> ) with
> {noformat}[ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-scm-publish-plugin:3.1.0:publish-scm
> (publish-site) on project sling-site: Failed to add new files to SCM:
> Exception while executing SCM command. Error while executing command. Error
> while executing process. Cannot run program "/bin/sh" (in directory
> "/home/jenkins/712657a4/workspace/Sling_modules_sling-site_master/target/scmpublish-checkout"):
> error=7, Argument list too long -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> {noformat}
> We are adding too many files and hitting MSCMPUB-18.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Assigned] (SLING-11217) Website publish job fails to run after adding the Sling 12 java docs
[
https://issues.apache.org/jira/browse/SLING-11217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu reassigned SLING-11217:
---
Assignee: Robert Munteanu
> Website publish job fails to run after adding the Sling 12 java docs
>
>
> Key: SLING-11217
> URL: https://issues.apache.org/jira/browse/SLING-11217
> Project: Sling
> Issue Type: Bug
> Components: Documentation, Site
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>Priority: Major
>
> The Sling Site Jenkins jobs currently fails ( e.g.
> https://ci-builds.apache.org/job/Sling/job/modules/job/sling-site/job/master/441/console
> ) with
> {noformat}[ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-scm-publish-plugin:3.1.0:publish-scm
> (publish-site) on project sling-site: Failed to add new files to SCM:
> Exception while executing SCM command. Error while executing command. Error
> while executing process. Cannot run program "/bin/sh" (in directory
> "/home/jenkins/712657a4/workspace/Sling_modules_sling-site_master/target/scmpublish-checkout"):
> error=7, Argument list too long -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> {noformat}
> We are adding too many files and hitting MSCMPUB-18.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (SLING-11217) Website publish job fails to run after adding the Sling 12 java docs
Robert Munteanu created SLING-11217:
---
Summary: Website publish job fails to run after adding the Sling
12 java docs
Key: SLING-11217
URL: https://issues.apache.org/jira/browse/SLING-11217
Project: Sling
Issue Type: Bug
Components: Documentation, Site
Reporter: Robert Munteanu
The Sling Site Jenkins jobs currently fails ( e.g.
https://ci-builds.apache.org/job/Sling/job/modules/job/sling-site/job/master/441/console
) with
{noformat}[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-scm-publish-plugin:3.1.0:publish-scm
(publish-site) on project sling-site: Failed to add new files to SCM: Exception
while executing SCM command. Error while executing command. Error while
executing process. Cannot run program "/bin/sh" (in directory
"/home/jenkins/712657a4/workspace/Sling_modules_sling-site_master/target/scmpublish-checkout"):
error=7, Argument list too long -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
{noformat}
We are adding too many files and hitting MSCMPUB-18.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[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=17509030#comment-17509030
]
Eric Norman commented on SLING-11158:
-
[~karlpauls] [~rombert] I'd agree that trying to maintain two different ways of
launching may be difficult to explain or maintain in the future. That's why my
first attempt at pull requests was to unify the starter and the
feature-launcher-maven-plugin to use the SLING-10956 style assembly+scripts to
do the same work.
Do you have any concerns with those specific 2 pull requests or the approach in
general?
If there are no objections in a few days I guess I will proceed with merging
those.
> 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)
[GitHub] [sling-org-apache-sling-jcr-maintenance] klcodanr merged pull request #2: SLING-11211: updated maven dependencies && fixed broken links
klcodanr merged pull request #2: URL: https://github.com/apache/sling-org-apache-sling-jcr-maintenance/pull/2 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (SLING-10585) Add support for invalidation requests
[
https://issues.apache.org/jira/browse/SLING-10585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17508913#comment-17508913
]
Timothee Maret commented on SLING-10585:
Thank you [~balasoiu] !
I have merged PR
[#9|https://github.com/apache/sling-org-apache-sling-distribution-journal-messages/pull/9]
with a twist to avoid the backward incompatible change and merged PR
[#11|https://github.com/apache/sling-org-apache-sling-distribution-api/pull/11].
Please update PR
[#101|https://github.com/apache/sling-org-apache-sling-distribution-journal/pull/101]
to reference the SNAPSHOT version of the distribution-api and journal-messages
modules and adjust to the latest journal-messages.
> Add support for invalidation requests
> -
>
> Key: SLING-10585
> URL: https://issues.apache.org/jira/browse/SLING-10585
> Project: Sling
> Issue Type: New Feature
> Components: Content Distribution
>Reporter: Timothee Maret
>Assignee: Timothee Maret
>Priority: Major
> Fix For: Content Distribution Journal Core 0.1.26
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Caching invalidation is typically triggered by content distribution, after
> processing an `ADD` or `DELETE` distribution request. When distributing
> referenced content, invalidation must also include on the referencing
> resources. To support this use case, we'll add support for a new type of
> distribution request that invalidates the caches without importing content.
> To support this, the org.apache.sling.distribution.DistributionRequestType
> API will be extended with
> {code:java}
> /**
> * Action type for invalidating content
> */
> INVALIDATE,
> {code}
> The PackageMessage.ReqType will be extended with the new INVALIDATION type.
> The DistributionPublisher will handle the invalidation distribution requests
> by sending a package message with the INVALIDATION type and no payload (like
> the DELETE package messages).
> The DistributionSubscriber will process invalidation messages by raising
> imported events and invoking the import post processors.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[GitHub] [sling-org-apache-sling-jcr-maintenance] ashokmca07 commented on pull request #2: SLING-11211: updated maven dependencies && fixed broken links
ashokmca07 commented on pull request #2: URL: https://github.com/apache/sling-org-apache-sling-jcr-maintenance/pull/2#issuecomment-1072591923 Hi @enapps-enorman or @klcodanr who will merge this pull request? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (SLING-11216) Add default FileDataStore support to the standard starter
Yuri Simione created SLING-11216: Summary: Add default FileDataStore support to the standard starter Key: SLING-11216 URL: https://issues.apache.org/jira/browse/SLING-11216 Project: Sling Issue Type: Improvement Components: Starter Affects Versions: Starter 12 Reporter: Yuri Simione In some environments *FileDataStore* is an important configuration point. I would suggest to add it to the standard Sling starter as configured in the Sling CMS app: https://github.com/apache/sling-org-apache-sling-app-cms/blob/4630ef9a293d54dbd8b91356fe9b975e401292ff/feature/src/main/features/oak/node-store/segment.json -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [sling-org-apache-sling-distribution-api] tmaret merged pull request #11: SLING-10585 - Add INVALIDATE distribution request type
tmaret merged pull request #11: URL: https://github.com/apache/sling-org-apache-sling-distribution-api/pull/11 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Closed] (SLING-11177) Update repo-init parser dependency to 1.6.14
[ https://issues.apache.org/jira/browse/SLING-11177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Angela Schreiber closed SLING-11177. > Update repo-init parser dependency to 1.6.14 > > > Key: SLING-11177 > URL: https://issues.apache.org/jira/browse/SLING-11177 > Project: Sling > Issue Type: Task > Components: Feature Model Analyser >Affects Versions: Feature Model Analyser 1.6.0 >Reporter: Angela Schreiber >Assignee: Angela Schreiber >Priority: Major > Fix For: Feature Model Analyser 1.6.2 > > > [~kpauls], [~cziegeler], I plan to release repoinit parser 1.6.14 and > repoinit jcr implementation 1.1.38 to make the bug fix for SLING-11160 > available in Adobe AEM. > As far as I remember this requires however that the feature model analyzer > also gets released with dependency pointing to the latest parser: > https://github.com/apache/sling-org-apache-sling-feature-analyser/blob/master/pom.xml#L165 > Question: is there any open issues that needs to go into "Feature Model > Analyser 1.6.2" or is it ok to release it along side the repo-init bundles > with an updated dependency? -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-11207) Update repo-init parser dependency to 1.6.14
[ https://issues.apache.org/jira/browse/SLING-11207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Angela Schreiber closed SLING-11207. > Update repo-init parser dependency to 1.6.14 > > > Key: SLING-11207 > URL: https://issues.apache.org/jira/browse/SLING-11207 > Project: Sling > Issue Type: Task > Components: Feature Model >Reporter: Angela Schreiber >Assignee: Angela Schreiber >Priority: Major > Fix For: slingfeature-maven-plugin 1.6.2 > > > [~cziegeler], as discussed. follow up to SLING-11177: > - update repoinit-parser dependency in the maven plugin as well > - for release also include latest analyser -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [sling-site] rombert commented on pull request #89: Sling 12 release notes: describe the new ways to launch Sling
rombert commented on pull request #89: URL: https://github.com/apache/sling-site/pull/89#issuecomment-1072551718 Accidentally pushed it with the Sling 12 javadocs, sorry. @kwin - let me know if you see anything that needs to be changed, these are not yet live. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [sling-site] rombert merged pull request #89: Sling 12 release notes: describe the new ways to launch Sling
rombert merged pull request #89: URL: https://github.com/apache/sling-site/pull/89 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Resolved] (SLING-11163) Update generate_javadoc_for_release.sh to work on the feature model
[ https://issues.apache.org/jira/browse/SLING-11163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-11163. - Resolution: Fixed Fixed with https://github.com/apache/sling-tooling-release/pull/4 > Update generate_javadoc_for_release.sh to work on the feature model > --- > > Key: SLING-11163 > URL: https://issues.apache.org/jira/browse/SLING-11163 > Project: Sling > Issue Type: Task > Components: Build and Source Control >Reporter: Robert Munteanu >Assignee: Robert Munteanu >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > So far we need to fix: > - parsing the feature instead of the provisioning model > - mixed requirements for JDKs. Some modules only build with Java 8, but at > least one bundle (Sling API) needs Java9 or newer. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [sling-tooling-release] rombert merged pull request #4: SLING-11163 - Update generate_javadoc_for_release.sh to work on the feature model
rombert merged pull request #4: URL: https://github.com/apache/sling-tooling-release/pull/4 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[RESULT][VOTE] Release Apache Sling Feature Model Analyser version 1.6.2, slingfeature-maven-plugin version 1.6.2
Hi, The vote has passed with the following result : +1 (binding): Carsten Ziegeler, Karl Pauls, Angela Schreiber +1 (non binding): Christian Schneider I will copy this release to the Sling dist directory and promote the artifacts to the central Maven repository. Kind regards Angela
[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-9773) Starter project does not build with the enforced minimum version of maven
[ https://issues.apache.org/jira/browse/SLING-9773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-9773. -- > Starter project does not build with the enforced minimum version of maven > - > > Key: SLING-9773 > URL: https://issues.apache.org/jira/browse/SLING-9773 > Project: Sling > Issue Type: Bug >Reporter: Eric Norman >Assignee: Konrad Windszus >Priority: Major > Fix For: Starter 12 > > > The org-apache-sling-starter project does not build with maven 3.3.9 which > is the current enforcer minimum version. > The bnd-indexer-maven-plugin doesn't appear to work with maven 3.3.9 even > with the skip flag set to true. It reports lots of nasty exceptions and > fails the build. > I did some additional testing and it looks like maven version 3.5.0 is the > minimum version that seems to work. > Do we need to enforce/change the minimum maven version required to build > sling to something newer than 3.3.9? -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-10601) Add a launcher module to the project archetype
[ https://issues.apache.org/jira/browse/SLING-10601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-10601. --- > Add a launcher module to the project archetype > -- > > Key: SLING-10601 > URL: https://issues.apache.org/jira/browse/SLING-10601 > Project: Sling > Issue Type: Improvement > Components: Maven Plugins and Archetypes >Reporter: Robert Munteanu >Assignee: Robert Munteanu >Priority: Major > Fix For: Project Archetype 1.0.8 > > > We should include a launcher module showing how to build on top of the Sling > Starter. The module should deploy the core bundle and the ui.apps module, but > not the all or any of the samples. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-10608) Refresh sample servlets
[ https://issues.apache.org/jira/browse/SLING-10608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-10608. --- > Refresh sample servlets > --- > > Key: SLING-10608 > URL: https://issues.apache.org/jira/browse/SLING-10608 > Project: Sling > Issue Type: Improvement > Components: Maven Plugins and Archetypes >Reporter: Robert Munteanu >Assignee: Robert Munteanu >Priority: Minor > Fix For: Project Archetype 1.0.8 > > > We should improve the documentation and add more sample servlets. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-10600) Add a mapping entry redirecting to the project's top-level content path
[
https://issues.apache.org/jira/browse/SLING-10600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu closed SLING-10600.
---
> Add a mapping entry redirecting to the project's top-level content path
> ---
>
> Key: SLING-10600
> URL: https://issues.apache.org/jira/browse/SLING-10600
> Project: Sling
> Issue Type: Improvement
> Components: Maven Plugins and Archetypes
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>Priority: Minor
> Fix For: Project Archetype 1.0.8
>
>
> When a project created via the sling-project-archetype is deployed it creates
> an entry under {{/content/${contentFolderName}/home}} which is not easily
> accessible. We should create a mapping entry that redirects to that page,
> which is what many projects want.
> Since it can 'hijack' the front page we should not deploy it by default, but
> allow enabling it from the sample module.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Closed] (SLING-11189) Content Loader: Race condition registering readers vs. loading content
[ https://issues.apache.org/jira/browse/SLING-11189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-11189. --- > Content Loader: Race condition registering readers vs. loading content > -- > > Key: SLING-11189 > URL: https://issues.apache.org/jira/browse/SLING-11189 > Project: Sling > Issue Type: Bug > Components: Extensions >Affects Versions: JCR ContentLoader 2.5.0 >Reporter: Stefan Seifert >Assignee: Stefan Seifert >Priority: Major > Fix For: JCR ContentLoader 2.5.2 > > Time Spent: 6h 50m > Remaining Estimate: 0h > > in SLING-11168 we detected a specific problem with Composum in Sling Starter > 12, which only occured on Windows 10 environments (and even there not > consistently in every scenario). > it seems that it may happen that Sling-Initial-Content is loaded from the > bundles when the ContentReader implementations are not yet registered on the > ContentReaderWhiteboard. > when this happens, the content is loaded into the repository, but files like > *.json are not transformed to nodes and properties, but is stored as binary > json files in the repository. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-10594) Generated project imports with error in Eclipse
[
https://issues.apache.org/jira/browse/SLING-10594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu closed SLING-10594.
---
> Generated project imports with error in Eclipse
> ---
>
> Key: SLING-10594
> URL: https://issues.apache.org/jira/browse/SLING-10594
> Project: Sling
> Issue Type: Bug
> Components: Maven Plugins and Archetypes
>Affects Versions: Sling Project Archetype 1.0.4
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>Priority: Major
> Fix For: Project Archetype 1.0.8
>
>
> I generated a project using the following command
> {noformat}
> $ mvn archetype:generate \
> -DarchetypeGroupId=org.apache.sling \
> -DarchetypeArtifactId=sling-project-archetype \
> -DarchetypeVersion=1.0.4 \
> -B \
> -DgroupId=com.example \
> -DartifactId=apachecon001 \
> -Dversion=1.0.0-SNAPSHOT \
> -DartifactName=ApacheCon \
> -Dpackage=com.example.apachecon \
> -DpackageGroup=apachecon \
> -DappsFolderName=apachecon001 \
> -DcontentFolderName=apachecon001 \
> -DslingModelSubPackage=models \
> -DslingHostName=localhost \
> -DslingPort=8080 \
> -DoptionAll=y \
> -DoptionExample=s
> {noformat}
> And ended up with a couple of compilation error in Eclipse:
> {noformat}
> Description ResourcePathLocationType
> The declared package "empty" does not match the expected package
> "com.example.apachecon.empty"DoesNothing.java
> /core/src/main/java/com/example/apachecon/empty line 17 Java Problem
> The declared package "com.example.apachecon.servlet" does not match the
> expected package "com.example.apachecon.com.example.apachecon.servlet"
> ByPathServletTest.java
> /core.example/src/test/java/com/example/apachecon/com/example/apachecon/servlet
> line 17 Java Problem
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Closed] (SLING-10604) Add default, simple, styling to the generated project
[ https://issues.apache.org/jira/browse/SLING-10604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-10604. --- > Add default, simple, styling to the generated project > - > > Key: SLING-10604 > URL: https://issues.apache.org/jira/browse/SLING-10604 > Project: Sling > Issue Type: Improvement > Components: Maven Plugins and Archetypes >Reporter: Robert Munteanu >Assignee: Robert Munteanu >Priority: Major > Fix For: Project Archetype 1.0.8 > > > We should make the generated project looks a bit better by adding some basic > layouts and a bit more content ( for the samples ). -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-9636) Refine feature model files
[
https://issues.apache.org/jira/browse/SLING-9636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu closed SLING-9636.
--
> Refine feature model files
> --
>
> Key: SLING-9636
> URL: https://issues.apache.org/jira/browse/SLING-9636
> Project: Sling
> Issue Type: Sub-task
> Components: Starter
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>Priority: Major
> Fix For: Starter 12
>
>
> The feature model files have been auto-generated and, while they work, there
> are improvements we can make, first of all making sure the split is
> consistent.
> We should additionally least:
> - give consistent names to the features, e.g. {{boot_boot.json}} should
> become {{boot.json}}
> - use placeholders where possible, e.g. {{ ${project.groupId} }} instead of
> {{org.apache.sling}}.
> - use variables - we have for instance {{slf4.version}} defined but we don't
> use it
> - remove (if no longer needed) {{sling.run.mode.install.options}}
> - remove {{org.apache.sling.provisioning.model}} bundle
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Closed] (SLING-9595) Fully switch starter build to the feature model
[ https://issues.apache.org/jira/browse/SLING-9595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-9595. -- > Fully switch starter build to the feature model > --- > > Key: SLING-9595 > URL: https://issues.apache.org/jira/browse/SLING-9595 > Project: Sling > Issue Type: Sub-task > Components: Starter >Reporter: Robert Munteanu >Assignee: Robert Munteanu >Priority: Major > Fix For: Starter 12 > > Time Spent: 50m > Remaining Estimate: 0h > > Fully switch starter to feature model: > - The feature model converter will be used to create individual feature files > out of the provisioning model files > - Feature model aggregates will be defined for the current run modes: oak_tar > and oak_mongo > - Feature model analysers will be configured for the main aggregates > - Produce feature archives for oak_tar and oak_mongo > - -Produce a kickstart jar- ( moved to SLING-9635 ) -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-9786) Use pre-authentication for system users
[ https://issues.apache.org/jira/browse/SLING-9786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-9786. -- > Use pre-authentication for system users > --- > > Key: SLING-9786 > URL: https://issues.apache.org/jira/browse/SLING-9786 > Project: Sling > Issue Type: Improvement > Components: Karaf, Starter >Reporter: Robert Munteanu >Assignee: Robert Munteanu >Priority: Major > Labels: Sling-12-ReleaseNotes > Fix For: Karaf Configs 1.0.0, Starter 12 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Oak [pre-authenticated > login|https://jackrabbit.apache.org/oak/docs/security/authentication/preauthentication.html] > without repository involvement presents a number of advantages: > - it is faster since the repository is not involved > - allows mapping a single principal to the repositories of multiple service > users, making ACLs easier to define in a fine-grained manner > We should therefore switch the starter to the pre-auth setup for service > users. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-9931) Upgrade to Composum 2.1.1
[ https://issues.apache.org/jira/browse/SLING-9931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-9931. -- > Upgrade to Composum 2.1.1 > - > > Key: SLING-9931 > URL: https://issues.apache.org/jira/browse/SLING-9931 > Project: Sling > Issue Type: Task > Components: Starter >Reporter: Robert Munteanu >Assignee: Robert Munteanu >Priority: Minor > Fix For: Starter 12 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-10409) Update to Felix 7 (OSGi Core R8)
[ https://issues.apache.org/jira/browse/SLING-10409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-10409. --- > Update to Felix 7 (OSGi Core R8) > > > Key: SLING-10409 > URL: https://issues.apache.org/jira/browse/SLING-10409 > Project: Sling > Issue Type: Improvement >Reporter: Konrad Windszus >Assignee: Robert Munteanu >Priority: Major > Fix For: Starter 12 > > > We are still relying on Felix 6 which is only compliant with OSGi Core R7. We > should upgrade to Felix 7. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (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:all-tabpanel ] Robert Munteanu closed SLING-9624. -- > 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 >Assignee: Konrad Windszus >Priority: Major > Fix For: Starter 12 > > Time Spent: 1h 40m > 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] [Closed] (SLING-10984) Starter IT: docker-maven-plugin:stop executed prior to feature-launcher-maven-plugin:stop
[
https://issues.apache.org/jira/browse/SLING-10984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu closed SLING-10984.
---
> Starter IT: docker-maven-plugin:stop executed prior to
> feature-launcher-maven-plugin:stop
> -
>
> Key: SLING-10984
> URL: https://issues.apache.org/jira/browse/SLING-10984
> Project: Sling
> Issue Type: Bug
> Components: Starter
>Affects Versions: Starter 12
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
> Fix For: Starter 12
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The order of the goals of {{docker-maven-plugin}} and
> {{feature-launcher-maven-plugin}} need to be executed in this order for the
> integration test
> # docker-maven-plugin:start
> # feature-launcher-maven-plugin:start
> # feature-launcher-maven-plugin:stop
> # docker-maven-plugin:stop
> But currently the docker container is stopped before the Sling feature is
> stopped.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Closed] (SLING-8403) Update composum.version to a newer version
[ https://issues.apache.org/jira/browse/SLING-8403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-8403. -- > Update composum.version to a newer version > -- > > Key: SLING-8403 > URL: https://issues.apache.org/jira/browse/SLING-8403 > Project: Sling > Issue Type: Task > Components: Starter >Reporter: Antonio Sanso >Assignee: Antonio Sanso >Priority: Minor > Fix For: Starter 12 > > > Composum 1.9.4 was released. It would be good to Update composum.version to > this newer version -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-8803) Update to Oak 1.26.0
[ https://issues.apache.org/jira/browse/SLING-8803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-8803. -- > Update to Oak 1.26.0 > > > Key: SLING-8803 > URL: https://issues.apache.org/jira/browse/SLING-8803 > Project: Sling > Issue Type: Improvement > Components: Starter >Reporter: Robert Munteanu >Assignee: Robert Munteanu >Priority: Major > Labels: Sling-12-ReleaseNotes > Fix For: Starter 12 > > > Oak 1.20.0 will be out, potentially with breaking changes (see OAK-8717) -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-9675) Update to Oak 1.32.0
[ https://issues.apache.org/jira/browse/SLING-9675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-9675. -- > Update to Oak 1.32.0 > > > Key: SLING-9675 > URL: https://issues.apache.org/jira/browse/SLING-9675 > Project: Sling > Issue Type: Improvement >Reporter: Robert Munteanu >Assignee: Robert Munteanu >Priority: Major > Labels: Sling-12-ReleaseNotes > Fix For: Starter 12 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-9491) Sling Starter: Generate bnd OSGi index
[ https://issues.apache.org/jira/browse/SLING-9491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-9491. -- > Sling Starter: Generate bnd OSGi index > -- > > Key: SLING-9491 > URL: https://issues.apache.org/jira/browse/SLING-9491 > Project: Sling > Issue Type: Improvement > Components: Starter >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > Labels: Sling-12-ReleaseNotes > Fix For: Starter 12 > > Time Spent: 2h 20m > Remaining Estimate: 0h > > To be able to easily checking resolvability of other bundles against the > Sling Starter distribution it would be beneficial if the index > ([https://github.com/bndtools/bnd/tree/master/maven/bnd-indexer-maven-plugin]) > would be provided as additional artifact for the Sling Starter module. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-9637) Re-enable Smoke IT, but only keep the repository available check
[ https://issues.apache.org/jira/browse/SLING-9637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-9637. -- > Re-enable Smoke IT, but only keep the repository available check > > > Key: SLING-9637 > URL: https://issues.apache.org/jira/browse/SLING-9637 > Project: Sling > Issue Type: Sub-task >Reporter: Robert Munteanu >Assignee: Robert Munteanu >Priority: Major > Fix For: Starter 12 > > Time Spent: 0.5h > Remaining Estimate: 0h > > The 'all bundles started' check is superfluous now that we have the feature > model analysers. However, it would be good to verify that the repository > successfully start up. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-11170) Update to DS 1.5 (OSGi R8) implementation Felix SCR 2.2.0
[ https://issues.apache.org/jira/browse/SLING-11170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-11170. --- > Update to DS 1.5 (OSGi R8) implementation Felix SCR 2.2.0 > - > > Key: SLING-11170 > URL: https://issues.apache.org/jira/browse/SLING-11170 > Project: Sling > Issue Type: Improvement >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > Fix For: Starter 12 > > Time Spent: 50m > Remaining Estimate: 0h > > Now that the Felix implementation of OSGi DS 1.5 (OSGi R8) is available we > should update to it. > The changelog is at > https://github.com/apache/felix-dev/blob/master/scr/changelog.txt. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-9690) Configure best-effort import behaviour for access control items
[
https://issues.apache.org/jira/browse/SLING-9690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu closed SLING-9690.
--
> Configure best-effort import behaviour for access control items
> ---
>
> Key: SLING-9690
> URL: https://issues.apache.org/jira/browse/SLING-9690
> Project: Sling
> Issue Type: Improvement
> Components: Karaf, Starter
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>Priority: Major
> Fix For: Karaf Features 1.0.0, Karaf Configs 1.0.0, Starter 12
>
>
> When importing principals and access control entries in the same package
> there are some scenarios that don't work out-of-the-box with FileVault
> content packages
> - users and resource-based ACEs in the same content package; users are not
> guaranteed to be processed before ACEs ( see [oak-...@jacrabbit.apache.org:
> Installing users and access control entries in the same
> package|https://lists.apache.org/thread.html/r94b8b31d3da59d18e3eaced1594c453fc7759b62d26474a42c3dbbe3%40%3Coak-dev.jackrabbit.apache.org%3E]
> )
> - users and principal-based ACEs in the same content package ( see JCRVLT-472
> )
> A reasonable workaround for this kind of scenarios is to configure
> {{AuthorizationConfigurationImpl}} to have a "besteffort" import behaviour.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Closed] (SLING-10656) SmokeIT readable URL checks need retries
[
https://issues.apache.org/jira/browse/SLING-10656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu closed SLING-10656.
---
> SmokeIT readable URL checks need retries
>
>
> Key: SLING-10656
> URL: https://issues.apache.org/jira/browse/SLING-10656
> Project: Sling
> Issue Type: Improvement
> Components: Starter
>Affects Versions: Starter 11
>Reporter: Bertrand Delacretaz
>Assignee: Bertrand Delacretaz
>Priority: Minor
> Fix For: Starter 12
>
>
> The {{SmokeIT. verifyReadableUrl}} tests introduced for SLING-10402 do not
> retry their HTTP requests and it looks like in some cases the content is not
> ready when the test runs.
> As we do have a {{Check}} class in the {{StarterReadyRule}} which does
> retries, we should also use it for the {{verifyReadableUrl}} tests.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Closed] (SLING-9685) Support principal-based authentication
[ https://issues.apache.org/jira/browse/SLING-9685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-9685. -- > Support principal-based authentication > -- > > Key: SLING-9685 > URL: https://issues.apache.org/jira/browse/SLING-9685 > Project: Sling > Issue Type: Improvement > Components: Karaf, Starter >Reporter: Robert Munteanu >Assignee: Robert Munteanu >Priority: Major > Labels: Sling-12-ReleaseNotes > Fix For: Karaf Features 1.0.0, Karaf Configs 1.0.0, Starter 12 > > > The [oak principal-based > authentication|https://jackrabbit.apache.org/oak/docs/security/authorization/principalbased.html] > is an alternate way of supporting access control entries, with the main > difference being that the policy entries are stored together with the user > itself, rather than with the content they target. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-8164) Switch to servicemix bundles for saaj in starter
[ https://issues.apache.org/jira/browse/SLING-8164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-8164. -- > Switch to servicemix bundles for saaj in starter > > > Key: SLING-8164 > URL: https://issues.apache.org/jira/browse/SLING-8164 > Project: Sling > Issue Type: Bug > Components: Launchpad >Affects Versions: Starter 11 >Reporter: Karl Pauls >Assignee: Karl Pauls >Priority: Major > Fix For: Starter 12 > > > Looks like [~kwin] was right (as usually) and I made another mistake in the > bundles that substitute missing core packages in java11 - namely, the saaj > bundle from geronimo isn't finding (or working) with the default oracle impl. > As it would be to painful to add the geronimo impl I think we should switch > to the servicemix bundles. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-10362) Sling Starter: trouble when installing packages containing install hooks with OSGi installer
[
https://issues.apache.org/jira/browse/SLING-10362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu closed SLING-10362.
---
> Sling Starter: trouble when installing packages containing install hooks with
> OSGi installer
>
>
> Key: SLING-10362
> URL: https://issues.apache.org/jira/browse/SLING-10362
> Project: Sling
> Issue Type: Improvement
> Components: Starter
>Affects Versions: Starter 12
> Environment: Sling-Starter 12-SNAPSHOT (commit 0e6a8e41) with JDK 11
> on MacOS
>Reporter: Hans-Peter Stoerr
>Assignee: Konrad Windszus
>Priority: Minor
> Fix For: Starter 12
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> I'm trying to install some packages into a snapshot of the Starter 12 using
> the Sling [fileinstaller
> provider|https://sling.apache.org/documentation/bundles/file-installer-provider.html],
> which works somewhat but not properly when the package has a setup hook.
> It seems that the packages are internally transformed by the [Content Package
> Installer
> Factory|https://sling.apache.org/documentation/bundles/content-package-installer-factory.html],
> but too early - the packages are unpacked before the repository was properly
> set up. See the stacktrace below: the package was likely installed when the
> user 'sling-package-install' wasn't properly set up in the repository yet.
> As workaround I currently set the start level of the
> org.apache.sling.installer.factory.packages to 21 - a bit later than all the
> other bundles. That makes the problem disappear. This might be a possibility
> for the Sling Starter 12, too, but I'm not sure whether it is the right
> option. Possibly the fileinstaller provider needs more dependencies from some
> bundles to make sure it's started late enough. Another way would be to give
> the Sling fileinstaller provider some additional options like the
> felix.fileinstall.active.level of [Felix File
> Install|https://felix.apache.org/documentation/subprojects/apache-felix-file-install.html].
> Or the [run mode
> support|https://sling.apache.org/documentation/bundles/file-installer-provider.html#run-mode-support-1]
> of the Sling file installer should be made to work somehow with packages, so
> that the packages are only installed when the run mode specified in the path
> is reached. That would be even better, since for packages you often have to
> specify an order as well, and that would be another option than package
> dependencies.
> To reproduce the bug you can check out Sling Starter 12 and execute the
> following commands:
> {code}
> cd target/
> mkdir fileinstall
> wget
> [https://repo1.maven.org/maven2/com/composum/nodes/composum-nodes-sling-package/2.6.1/composum-nodes-sling-package-2.6.1.zip]
> mv composum-nodes-sling-package-2.6.1.zip fileinstall/
> java -jar dependency/org.apache.sling.feature.launcher.jar -f
> org.apache.sling.starter-12-SNAPSHOT-oak_tar_far.far -D
> felix.startlevel.bundle=30 -D sling.fileinstall.dir=fileinstall/
> {code}
> In the log you get the following stacktrace in the log:
> {code}
> 07.05.2021 16:42:44.945 *INFO* [Apache Sling Repository Startup Thread #1|#1]
> org.apache.sling.installer.provider.jcr.impl.RootFolderListener Watching
> /apps to detect potential changes in
> subfoldersault.packaging.PackageException: Package extraction requires admin
> session as it has a hook (userid 'sling-package-install' not allowed).
> at
> org.apache.jackrabbit.vault.packaging.impl.ZipVaultPackage.checkAllowanceToInstallPackage(ZipVaultPackage.java:226)
> [org.apache.jackrabbit.vault:3.4.10]
> at
> org.apache.jackrabbit.vault.packaging.impl.ZipVaultPackage.prepareExtract(ZipVaultPackage.java:199)
> [org.apache.jackrabbit.vault:3.4.10]
> at
> org.apache.jackrabbit.vault.packaging.impl.JcrPackageImpl.extract(JcrPackageImpl.java:389)
> [org.apache.jackrabbit.vault:3.4.10]
> at
> org.apache.jackrabbit.vault.packaging.impl.JcrPackageImpl.extract(JcrPackageImpl.java:356)
> [org.apache.jackrabbit.vault:3.4.10]
> at
> org.apache.jackrabbit.vault.packaging.impl.JcrPackageImpl.extract(JcrPackageImpl.java:342)
> [org.apache.jackrabbit.vault:3.4.10]
> at
> org.apache.sling.installer.factory.packages.impl.PackageTransformer$InstallPackageTask.doExecute(PackageTransformer.java:337)
> [org.apache.sling.installer.factory.packages:1.0.4]
> at
> org.apache.sling.installer.factory.packages.impl.PackageTransformer$AbstractPackageInstallTask.execute(PackageTransformer.java:269)
> [org.apache.sling.installer.factory.packages:1.0.4]
> at
> org.apache.sling.installer.core.impl.OsgiInstallerImpl.doExecuteTasks(OsgiInstallerImpl.java:918)
> [org.apache.sling.installer.core:3.11.4]
> at
>
[jira] [Closed] (SLING-8614) Update to Oak 1.16
[ https://issues.apache.org/jira/browse/SLING-8614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-8614. -- > Update to Oak 1.16 > -- > > Key: SLING-8614 > URL: https://issues.apache.org/jira/browse/SLING-8614 > Project: Sling > Issue Type: Task > Components: Starter >Reporter: Robert Munteanu >Assignee: Robert Munteanu >Priority: Major > Labels: Sling-12-ReleaseNotes > Fix For: Starter 12 > > > We're lagging behind Oak releases, and Oak 1.16.0 was just released. We > should update now. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-8350) Switch the Sling starter to the feature model
[ https://issues.apache.org/jira/browse/SLING-8350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-8350. -- > Switch the Sling starter to the feature model > - > > Key: SLING-8350 > URL: https://issues.apache.org/jira/browse/SLING-8350 > Project: Sling > Issue Type: Improvement > Components: Starter >Reporter: Robert Munteanu >Assignee: Robert Munteanu >Priority: Major > Labels: Sling-12-ReleaseNotes > Fix For: Starter 12 > > Attachments: [SLING-8954] Sling Feature Launcher should support Class > Resource Feature Files - ASF JIRA.webloc, [SLING-8955] Add Support for > Feature Launcher - ASF JIRA.webloc > > > This is pretty straightforward, but we also need to have a way of generating > the jar and war files. > > Both the Sling Starter as well as the Sling Starter Maven plugin we recreated > as Kickstart projects supporting Feature Models. The support for WAR files > will be dropped with them. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-9498) Create feature model aggregates on the fly from the Sling Starter build
[ https://issues.apache.org/jira/browse/SLING-9498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-9498. -- > Create feature model aggregates on the fly from the Sling Starter build > --- > > Key: SLING-9498 > URL: https://issues.apache.org/jira/browse/SLING-9498 > Project: Sling > Issue Type: Sub-task > Components: Starter >Reporter: Robert Munteanu >Assignee: Robert Munteanu >Priority: Major > Fix For: Starter 12 > > Time Spent: 1h > Remaining Estimate: 0h > > Create feature model aggregates on the fly from the build - oak_tar and > oak_mongo. This should use the feature-converter-maven-plugin to create the > feature files. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-9707) Variable ${sling.home} not replaced in configuration values
[
https://issues.apache.org/jira/browse/SLING-9707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu closed SLING-9707.
--
> Variable ${sling.home} not replaced in configuration values
> ---
>
> Key: SLING-9707
> URL: https://issues.apache.org/jira/browse/SLING-9707
> Project: Sling
> Issue Type: Bug
> Components: Feature Model, Starter
>Affects Versions: Starter 12
>Reporter: Cris Rockwell
>Assignee: Robert Munteanu
>Priority: Major
> Fix For: Starter 12
>
>
> When configuring a file datastore, the variable ${sling.home} would be useful
> as showed in the following feature.json and in the Starter Pull Request
> ([https://github.com/apache/sling-org-apache-sling-starter/pull/13])
> {
> "bundles":[
> {
> "id":"org.apache.jackrabbit:oak-segment-tar:${oak.version}",
> "start-order":"15"
> }
> ],
> "configurations":{
> "org.apache.jackrabbit.oak.segment.SegmentNodeStoreService":
> { "name":"Default NodeStore", "customBlobStore":true }
> ,
> "org.apache.jackrabbit.oak.plugins.blob.datastore.FileDataStore": {
> "minRecordLength":4096,
> "path":"${sling.home}/repository/datastore",
> "cacheSizeInMB":128
> }
> }
> }
> Running java -jar dependency/org.apache.sling.feature.launcher.jar -f
> slingfeature-tmp/feature-oak_tar.json -p sling
> Results in a folder called ${sling.home}
> {{➜ $ ls target}}
> {{${sling.home} maven-archiver
> org.apache.sling.starter-12-SNAPSHOT-oak_tar_far.far sling}}
> {{classes maven-shared-archive-resources
> org.apache.sling.starter-12-SNAPSHOT-sources.jar
> sling-slingfeature-maven-plugin-fmtmp}}
> {{dependency maven-status org.apache.sling.starter-12-SNAPSHOT.jar
> slingfeature-tmp}}
> {{generated-test-sources
> org.apache.sling.starter-12-SNAPSHOT-oak_mongo_far.far rat.txt test-classes}}
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Closed] (SLING-7953) Switch from legacy commons lang 2 to commons lang 3
[ https://issues.apache.org/jira/browse/SLING-7953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-7953. -- > Switch from legacy commons lang 2 to commons lang 3 > --- > > Key: SLING-7953 > URL: https://issues.apache.org/jira/browse/SLING-7953 > Project: Sling > Issue Type: Improvement >Reporter: Carsten Ziegeler >Assignee: Robert Munteanu >Priority: Major > Labels: Sling-12-ReleaseNotes > Fix For: Starter 12 > > > The following bundles still use the legacy commons lang 2 version > They should be updated to use commons lang 3 > org.apache.sling.auth.form (/) > org.apache.sling.installer.hc (/) > org.apache.sling.scripting.jsp.taglib (/) > org.apache.sling.xss (/) > org.apache.tika.parsers (/) -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-8343) Use Felix Health Checks Runtime in Sling Starter
[ https://issues.apache.org/jira/browse/SLING-8343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-8343. -- > Use Felix Health Checks Runtime in Sling Starter > > > Key: SLING-8343 > URL: https://issues.apache.org/jira/browse/SLING-8343 > Project: Sling > Issue Type: New Feature > Components: Health Check >Reporter: Georg Henzler >Assignee: Georg Henzler >Priority: Major > Fix For: Starter 12 > > > https://github.com/apache/sling-org-apache-sling-starter needs to be updated > following the guide in > https://sling.apache.org/documentation/bundles/sling-health-check-tool.html#migrate-a-runtime -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-9638) Update Starter Docker image to be based on the feature model
[ https://issues.apache.org/jira/browse/SLING-9638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-9638. -- > Update Starter Docker image to be based on the feature model > > > Key: SLING-9638 > URL: https://issues.apache.org/jira/browse/SLING-9638 > Project: Sling > Issue Type: Sub-task >Reporter: Robert Munteanu >Assignee: Robert Munteanu >Priority: Major > Fix For: Starter 12 > > Time Spent: 4h 20m > Remaining Estimate: 0h > > The Sling Docker image is currently built from > https://github.com/apache/sling-org-apache-sling-starter-docker/ and is based > on the provisioning model. With the feature model we have a more > container-friendly approach where we can ship the feature files and select at > runtime what we are going to launch. > We should also take the opportunity and check if we can generate the Docker > image from the starter build itself, which makes it much simpler to develop > and evolve it. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-10832) JaxbMarhshallingTest fails on Java 17
[
https://issues.apache.org/jira/browse/SLING-10832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu closed SLING-10832.
---
> JaxbMarhshallingTest fails on Java 17
> -
>
> Key: SLING-10832
> URL: https://issues.apache.org/jira/browse/SLING-10832
> Project: Sling
> Issue Type: Bug
> Components: Starter
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>Priority: Major
> Fix For: Starter 12
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> The Starter logs contain:
> {noformat}21.09.2021 11:18:41.731 *ERROR* [127.0.0.1 [1632215921681] GET
> /bin/jaxb.xml HTTP/1.1]
> org.apache.sling.engine.impl.SlingRequestProcessorImpl service: Uncaught
> Throwable
> java.lang.ExceptionInInitializerError: null
> at
> com.sun.xml.bind.v2.runtime.reflect.opt.AccessorInjector.prepare(AccessorInjector.java:81)
> [org.apache.servicemix.bundles.jaxb-impl:2.2.11.1]
> at
> com.sun.xml.bind.v2.runtime.reflect.opt.OptimizedAccessorFactory.get(OptimizedAccessorFactory.java:125)
> [org.apache.servicemix.bundles.jaxb-impl:2.2.11.1]
> at
> com.sun.xml.bind.v2.runtime.reflect.Accessor$GetterSetterReflection.optimize(Accessor.java:402)
> [org.apache.servicemix.bundles.jaxb-impl:2.2.11.1]
> at
> com.sun.xml.bind.v2.runtime.reflect.TransducedAccessor$CompositeTransducedAccessorImpl.(TransducedAccessor.java:235)
> [org.apache.servicemix.bundles.jaxb-impl:2.2.11.1]
> at
> com.sun.xml.bind.v2.runtime.reflect.TransducedAccessor.get(TransducedAccessor.java:175)
> [org.apache.servicemix.bundles.jaxb-impl:2.2.11.1]
> at
> com.sun.xml.bind.v2.model.impl.RuntimeClassInfoImpl.calcTransducer(RuntimeClassInfoImpl.java:245)
> [org.apache.servicemix.bundles.jaxb-impl:2.2.11.1]
> at
> com.sun.xml.bind.v2.model.impl.RuntimeClassInfoImpl.getTransducer(RuntimeClassInfoImpl.java:219)
> [org.apache.servicemix.bundles.jaxb-impl:2.2.11.1]
> at
> com.sun.xml.bind.v2.model.impl.RuntimeClassInfoImpl.link(RuntimeClassInfoImpl.java:196)
> [org.apache.servicemix.bundles.jaxb-impl:2.2.11.1]
> at
> com.sun.xml.bind.v2.model.impl.ModelBuilder.link(ModelBuilder.java:454)
> [org.apache.servicemix.bundles.jaxb-impl:2.2.11.1]
> at
> com.sun.xml.bind.v2.model.impl.RuntimeModelBuilder.link(RuntimeModelBuilder.java:133)
> [org.apache.servicemix.bundles.jaxb-impl:2.2.11.1]
> at
> com.sun.xml.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet(JAXBContextImpl.java:458)
> [org.apache.servicemix.bundles.jaxb-impl:2.2.11.1]
> at
> com.sun.xml.bind.v2.runtime.JAXBContextImpl.(JAXBContextImpl.java:292)
> [org.apache.servicemix.bundles.jaxb-impl:2.2.11.1]
> at
> com.sun.xml.bind.v2.runtime.JAXBContextImpl.(JAXBContextImpl.java:139)
> [org.apache.servicemix.bundles.jaxb-impl:2.2.11.1]
> at
> com.sun.xml.bind.v2.runtime.JAXBContextImpl$JAXBContextBuilder.build(JAXBContextImpl.java:1138)
> [org.apache.servicemix.bundles.jaxb-impl:2.2.11.1]
> at
> com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:162)
> [org.apache.servicemix.bundles.jaxb-impl:2.2.11.1]
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:568)
> at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:222)
> [org.apache.servicemix.specs.jaxb-api-2.2:2.9.0]
> at javax.xml.bind.ContextFinder.find(ContextFinder.java:396)
> [org.apache.servicemix.specs.jaxb-api-2.2:2.9.0]
> at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:656)
> [org.apache.servicemix.specs.jaxb-api-2.2:2.9.0]
> at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:599)
> [org.apache.servicemix.specs.jaxb-api-2.2:2.9.0]
> at
> org.apache.sling.launchpad.testservices.servlets.JaxbServlet.doGet(JaxbServlet.java:51)
> [org.apache.sling.launchpad.test-services:12.0.0.SNAPSHOT]
> at
> org.apache.sling.api.servlets.SlingSafeMethodsServlet.mayService(SlingSafeMethodsServlet.java:266)
> [org.apache.sling.api:2.23.6]
> at
> org.apache.sling.api.servlets.SlingAllMethodsServlet.mayService(SlingAllMethodsServlet.java:137)
> [org.apache.sling.api:2.23.6]
> at
> org.apache.sling.api.servlets.SlingSafeMethodsServlet.service(SlingSafeMethodsServlet.java:342)
> [org.apache.sling.api:2.23.6]
> at
> org.apache.sling.api.servlets.SlingSafeMethodsServlet.service(SlingSafeMethodsServlet.java:374)
> [org.apache.sling.api:2.23.6]
> at
>
[jira] [Closed] (SLING-8581) Include Resource Filter in Sling Starter
[ https://issues.apache.org/jira/browse/SLING-8581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-8581. -- > Include Resource Filter in Sling Starter > > > Key: SLING-8581 > URL: https://issues.apache.org/jira/browse/SLING-8581 > Project: Sling > Issue Type: Improvement >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > Labels: Sling-12-ReleaseNotes > Fix For: Starter 12 > > > As discussed in > https://www.mail-archive.com/dev@sling.apache.org/msg86704.html the new > Resource Filter bundle should be added to Sling Starter. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-8319) Update Apache Felix modules and Installer Config Factory
[ https://issues.apache.org/jira/browse/SLING-8319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-8319. -- > Update Apache Felix modules and Installer Config Factory > > > Key: SLING-8319 > URL: https://issues.apache.org/jira/browse/SLING-8319 > Project: Sling > Issue Type: Improvement > Components: Starter >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler >Priority: Major > Fix For: Starter 12 > > > We should update: > [INFO] org.apache.felix:org.apache.felix.configadmin ... 1.9.10 -> > 1.9.14 > [INFO] org.apache.felix:org.apache.felix.http.bridge . 4.0.4 -> > 4.0.6 > [INFO] org.apache.felix:org.apache.felix.http.jetty .. 4.0.6 -> > 4.0.8 > [INFO] org.apache.felix:org.apache.felix.scr ... 2.1.14 -> > 2.1.16 > [INFO] org.apache.sling:org.apache.sling.installer.factory.configuration ... > [INFO] 1.2.0 -> > 1.2.2 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-7504) Sling File Installer Provider inactive in Sling Starter and directory not auto-created
[
https://issues.apache.org/jira/browse/SLING-7504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu closed SLING-7504.
--
> Sling File Installer Provider inactive in Sling Starter and directory not
> auto-created
> --
>
> Key: SLING-7504
> URL: https://issues.apache.org/jira/browse/SLING-7504
> Project: Sling
> Issue Type: Improvement
> Components: Launchpad
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
> Fix For: Starter 12, File Installer 1.3.4
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> Even in the newest Starter 11 the framework property for the Sling File
> Installer is not set by default. This should be fixed. The relevant framework
> property is {{sling.fileinstall.dir}}. I propose to set this to
> {{${sling.home}/install}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[GitHub] [sling-org-apache-sling-jcr-maintenance] sonarcloud[bot] removed a comment on pull request #2: SLING-11211: updated maven dependencies && fixed broken links
sonarcloud[bot] removed a comment on pull request #2: URL: https://github.com/apache/sling-org-apache-sling-jcr-maintenance/pull/2#issuecomment-1070521242 Kudos, SonarCloud Quality Gate passed!  [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-maintenance=2=false=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-maintenance=2=false=BUG) [0 Bugs](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-maintenance=2=false=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-maintenance=2=false=VULNERABILITY) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-maintenance=2=false=VULNERABILITY) [0 Vulnerabilities](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-maintenance=2=false=VULNERABILITY) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-jcr-maintenance=2=false=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-jcr-maintenance=2=false=SECURITY_HOTSPOT) [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-jcr-maintenance=2=false=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-maintenance=2=false=CODE_SMELL) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-maintenance=2=false=CODE_SMELL) [0 Code Smells](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-maintenance=2=false=CODE_SMELL) [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-jcr-maintenance=2=coverage=list) No Coverage information [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-jcr-maintenance=2=new_duplicated_lines_density=list) [0.0% Duplication](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-jcr-maintenance=2=new_duplicated_lines_density=list) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Closed] (SLING-11194) Content Loader: Add log message if Sling-Initial-Content is not processed due to stale lock node at /var/sling/bundle-content
[
https://issues.apache.org/jira/browse/SLING-11194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu closed SLING-11194.
---
> Content Loader: Add log message if Sling-Initial-Content is not processed due
> to stale lock node at /var/sling/bundle-content
> -
>
> Key: SLING-11194
> URL: https://issues.apache.org/jira/browse/SLING-11194
> Project: Sling
> Issue Type: Bug
> Components: Extensions
>Affects Versions: JCR ContentLoader 2.5.0
>Reporter: Stefan Seifert
>Assignee: Stefan Seifert
>Priority: Minor
> Fix For: JCR ContentLoader 2.5.2
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> we had one occurrence of a very difficult to debug issue that on only one out
> of many instances a given bundle with Sling-Initial-Content was not processed
> properly when the bundle was registered by ContentLoader without any
> indication about the reason in the log files, even at DEBUG level.
> only the message {{Registering bundle XYZ for content loading.}} was logged
> but nothing more, the Sling-Initial-Content was completely ignored.
> we found out that the root cause was a stale "locking node" at
> {{/var/sling/bundle-content/XYZ}} which was probably left there after and
> unexpected instance shutdown or other failure. the problem was solved by
> deleting this locking node, but the error log did not help. we should add
> some more DEBUG log messages in this error to help diagnosing rare problems
> like this.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Closed] (SLING-10363) Update to Sling Archetype Parent 6
[ https://issues.apache.org/jira/browse/SLING-10363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-10363. --- > Update to Sling Archetype Parent 6 > -- > > Key: SLING-10363 > URL: https://issues.apache.org/jira/browse/SLING-10363 > Project: Sling > Issue Type: Task >Reporter: Eric Norman >Assignee: Eric Norman >Priority: Major > Fix For: Project Archetype 1.0.8 > > > Update to sling-archetype-parent version 6 so the project will build properly > with java 11 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-10595) Project archetype should default to Java 11
[ https://issues.apache.org/jira/browse/SLING-10595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-10595. --- > Project archetype should default to Java 11 > --- > > Key: SLING-10595 > URL: https://issues.apache.org/jira/browse/SLING-10595 > Project: Sling > Issue Type: Improvement > Components: Maven Plugins and Archetypes >Reporter: Robert Munteanu >Assignee: Robert Munteanu >Priority: Major > Fix For: Project Archetype 1.0.8 > > > The archetype generates projects configured with Java 7, which is really old. > Java 11 is probably a better conservative default. > We should also configure the Jenkins job to build with Java 11. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-10999) Update logging implementations
[ https://issues.apache.org/jira/browse/SLING-10999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-10999. --- > Update logging implementations > -- > > Key: SLING-10999 > URL: https://issues.apache.org/jira/browse/SLING-10999 > Project: Sling > Issue Type: Improvement > Components: Starter >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler >Priority: Major > Fix For: Starter 12 > > > Update to Apache Felix Log 1.2.6 and Apache Sling Commons Log 5.3.0 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-11195) Downgrade ANTLR to match Sling HTL Engine
[ https://issues.apache.org/jira/browse/SLING-11195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-11195. --- > Downgrade ANTLR to match Sling HTL Engine > - > > Key: SLING-11195 > URL: https://issues.apache.org/jira/browse/SLING-11195 > Project: Sling > Issue Type: Improvement > Components: Starter >Reporter: Robert Munteanu >Assignee: Robert Munteanu >Priority: Major > Fix For: Starter 12 > > > (Description copied from > https://github.com/apache/sling-org-apache-sling-starter/pull/34 ) > Opening http://localhost/htl/repl.html gives the following warning: > ANTLR Tool version 4.7.1 used for code generation does not match the current > runtime version 4.9.1 > ANTLR Runtime version 4.7.1 used for parser compilation does not match the > current runtime version 4.9.1 > This is caused by Sling HTL Engine being compiled with ANTLR 4.7.1. This is > probably harmless (HTL works fine seemingly), but one static field was > removed in antlr-runtime (no idea how important), so the versions are in > principle not ABI compatible. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-10459) Update starter to use Oak 1.40.0
[ https://issues.apache.org/jira/browse/SLING-10459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-10459. --- > Update starter to use Oak 1.40.0 > > > Key: SLING-10459 > URL: https://issues.apache.org/jira/browse/SLING-10459 > Project: Sling > Issue Type: Improvement >Reporter: Eric Norman >Assignee: Eric Norman >Priority: Major > Labels: Sling-12-ReleaseNotes > Fix For: Starter 12 > > Time Spent: 1h > Remaining Estimate: 0h > > Oak 1.40.0 has been released. Update the starter to this version. > [https://downloads.apache.org/jackrabbit/oak/1.40.0/RELEASE-NOTES.txt] > FYI: This release of Oak contains a fix for OAK-9357 that looks useful toward > resolving the troubles reported at SLING-10402 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (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:all-tabpanel ] Robert Munteanu closed SLING-11173. --- > 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 >Assignee: 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] [Closed] (SLING-10827) Support Java 17
[ https://issues.apache.org/jira/browse/SLING-10827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-10827. --- > Support Java 17 > --- > > Key: SLING-10827 > URL: https://issues.apache.org/jira/browse/SLING-10827 > Project: Sling > Issue Type: Improvement >Reporter: Robert Munteanu >Assignee: Robert Munteanu >Priority: Major > Labels: Sling-12-ReleaseNotes > Fix For: Starter 12 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-11183) Sling is starting up page no longer present
[
https://issues.apache.org/jira/browse/SLING-11183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu closed SLING-11183.
---
> Sling is starting up page no longer present
> ---
>
> Key: SLING-11183
> URL: https://issues.apache.org/jira/browse/SLING-11183
> Project: Sling
> Issue Type: Bug
> Components: Starter
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>Priority: Major
> Fix For: Starter 12
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> [~sseifert] noted that with the Sling Starter 12 release candidate the
> startup page is no longer available. Instead we get
> {quote}503 Service Unavailable
> (Could not read 'content/content/startup/index.html' from bundle
> 'org.apache.sling.starter.content': file not found){quote}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Closed] (SLING-10597) Simplify setup of resource resolution mappings
[
https://issues.apache.org/jira/browse/SLING-10597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu closed SLING-10597.
---
> Simplify setup of resource resolution mappings
> --
>
> Key: SLING-10597
> URL: https://issues.apache.org/jira/browse/SLING-10597
> Project: Sling
> Issue Type: Improvement
> Components: Starter
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>Priority: Minor
> Fix For: Starter 12
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Creating the base path for resolution mapping entries ( {{/etc/map/http}} ,
> see
> https://sling.apache.org/documentation/the-sling-engine/mappings-for-resource-resolution.html#root-level-mappings
> ) would make creating mapping entries simpler.
> This should be created in the Sling Starter OOTB. I would not create an
> {{https}} entry for now, since TLS-enabled Sling entries require manual set
> up, and probably Sling is used with an upstream server that handles TLS
> termination anyway.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Closed] (SLING-11056) Update to Oak 1.42.0
[ https://issues.apache.org/jira/browse/SLING-11056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-11056. --- > Update to Oak 1.42.0 > > > Key: SLING-11056 > URL: https://issues.apache.org/jira/browse/SLING-11056 > Project: Sling > Issue Type: Improvement > Components: Starter >Reporter: Robert Munteanu >Assignee: Robert Munteanu >Priority: Major > Fix For: Starter 12 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-10143) bundles referenced in sling starter are out of date
[
https://issues.apache.org/jira/browse/SLING-10143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu closed SLING-10143.
---
> bundles referenced in sling starter are out of date
> ---
>
> Key: SLING-10143
> URL: https://issues.apache.org/jira/browse/SLING-10143
> Project: Sling
> Issue Type: Improvement
> Components: Starter
>Reporter: Ruben Reusser
>Assignee: Robert Munteanu
>Priority: Major
> Fix For: Starter 12
>
> Attachments:
> 0001-updated-3rd-party-dependencies-of-sling-starter.patch,
> 0002-javax.activation-dependency-needed-to-be-increased.patch,
> 0003-updated-to-latest-sling-bundles-added-missing-felix-.patch
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Would be nice to make sure the sling starter uses the latest bundles -
> according to
> {code:java}
> mvn versions:display-dependency-updates{code}
> the sling starter is a bit out of date with the dependencies
> {code:java}
> [INFO] The following dependencies in Dependencies have newer versions:
> [INFO] com.composum.nodes:composum-nodes-commons . 2.1.1 ->
> 2.3.0
> [INFO] com.composum.nodes:composum-nodes-console . 2.1.1 ->
> 2.3.0
> [INFO] com.composum.nodes:composum-nodes-jslibs .. 2.1.1 ->
> 2.3.0
> [INFO] com.composum.nodes:composum-nodes-pckgmgr . 2.1.1 ->
> 2.3.0
> [INFO] com.composum.nodes:composum-nodes-usermgr . 2.1.1 ->
> 2.3.0
> [INFO] com.fasterxml.jackson.core:jackson-annotations .. 2.11.1 ->
> 2.12.1
> [INFO] com.fasterxml.jackson.core:jackson-core . 2.11.1 ->
> 2.12.1
> [INFO] com.fasterxml.jackson.core:jackson-databind . 2.11.1 ->
> 2.12.1
> [INFO] com.google.guava:guava .. 15.0 ->
> 30.1-jre
> [INFO] com.h2database:h2-mvstore . 1.4.194 ->
> 1.4.200
> [INFO] commons-codec:commons-codec . 1.14 ->
> 1.15
> [INFO] commons-collections:commons-collections 3.2.2 ->
> 20040616
> [INFO] commons-io:commons-io ... 2.6 ->
> 2.8.0
> [INFO] io.dropwizard.metrics:metrics-core . 3.2.6 ->
> 4.2.0-beta.1
> [INFO] org.antlr:antlr4-runtime .. 4.7.2 ->
> 4.9.1
> [INFO] org.apache.commons:commons-lang3 . 3.9 ->
> 3.11
> [INFO] org.apache.felix:org.apache.felix.configadmin ... 1.9.16 ->
> 1.9.20
> [INFO] org.apache.felix:org.apache.felix.eventadmin .. 1.5.0 ->
> 1.6.2
> [INFO] org.apache.felix:org.apache.felix.http.jetty . 4.0.18 ->
> 4.1.4
> [INFO] org.apache.felix:org.apache.felix.metatype 1.2.2 ->
> 1.2.4
> [INFO] org.apache.felix:org.apache.felix.scr ... 2.1.20 ->
> 2.1.24
> [INFO] org.apache.felix:org.apache.felix.utils . 1.11.2 ->
> 1.11.6
> [INFO] org.apache.felix:org.apache.felix.webconsole .. 4.5.0 ->
> 4.6.0
> [INFO] org.apache.geronimo.specs:geronimo-annotation_1.3_spec 1.1 ->
> 1.3
> [INFO] org.apache.geronimo.specs:geronimo-atinject_1.0_spec .. 1.1 ->
> 1.2
> [INFO] org.apache.httpcomponents:httpclient 4.5.10 ->
> 4.5.13
> [INFO] org.apache.httpcomponents:httpclient-osgi ... 4.5.10 ->
> 4.5.13
> [INFO] org.apache.httpcomponents:httpcore-osgi . 4.4.12 ->
> 4.4.14
> [INFO] org.apache.jackrabbit:jackrabbit-data ... 2.20.0 ->
> 2.21.5
> [INFO] org.apache.jackrabbit:jackrabbit-jcr-commons 2.20.0 ->
> 2.21.5
> [INFO] org.apache.jackrabbit:jackrabbit-jcr-rmi 2.20.0 ->
> 2.21.5
> [INFO] org.apache.jackrabbit:jackrabbit-spi 2.20.0 ->
> 2.21.5
> [INFO] org.apache.jackrabbit:jackrabbit-spi-commons 2.20.0 ->
> 2.21.5
> [INFO] org.apache.jackrabbit:jackrabbit-webdav . 2.20.0 ->
> 2.21.5
> [INFO] org.apache.jackrabbit:oak-api ... 1.32.0 ->
> 1.38.0
> [INFO] org.apache.jackrabbit:oak-authorization-principalbased ...
> [INFO] 1.32.0 ->
> 1.38.0
> [INFO] org.apache.jackrabbit:oak-blob .. 1.32.0 ->
> 1.38.0
> [INFO] org.apache.jackrabbit:oak-blob-plugins .. 1.32.0 ->
> 1.38.0
> [INFO] org.apache.jackrabbit:oak-commons ... 1.32.0 ->
> 1.38.0
> [INFO] org.apache.jackrabbit:oak-core .. 1.32.0 ->
> 1.38.0
> [INFO] org.apache.jackrabbit:oak-core-spi .. 1.32.0 ->
> 1.38.0
> [INFO] org.apache.jackrabbit:oak-jackrabbit-api 1.32.0 ->
> 1.38.0
> [INFO] org.apache.jackrabbit:oak-jcr ... 1.32.0 ->
> 1.38.0
> [INFO]
[jira] [Closed] (SLING-11193) Configure the quartz scheduler with the known allowed thread pool names
[
https://issues.apache.org/jira/browse/SLING-11193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu closed SLING-11193.
---
> Configure the quartz scheduler with the known allowed thread pool names
> ---
>
> Key: SLING-11193
> URL: https://issues.apache.org/jira/browse/SLING-11193
> Project: Sling
> Issue Type: Improvement
> Components: Starter
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>Priority: Major
> Fix For: Starter 12
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Running the Starter now produces warnings similar to
> {noformat}
> 10.03.2022 15:47:32.111 *WARN* [FelixStartLevel]
> org.apache.sling.commons.scheduler.impl.QuartzScheduler Scheduler job
> requested thread pool with name oak but this thread pool is not in the list
> of allowed pools.
> 10.03.2022 15:47:32.111 *WARN* [FelixStartLevel]
> org.apache.sling.commons.scheduler.impl.QuartzScheduler Scheduler job
> requested thread pool with name oak but this thread pool is not in the list
> of allowed pools.
> 10.03.2022 15:47:32.111 *WARN* [FelixStartLevel]
> org.apache.sling.commons.scheduler.impl.QuartzScheduler Scheduler job
> requested thread pool with name oak but this thread pool is not in the list
> of allowed pools.
> 10.03.2022 15:47:32.111 *WARN* [FelixStartLevel]
> org.apache.sling.commons.scheduler.impl.QuartzScheduler Scheduler job
> requested thread pool with name oak but this thread pool is not in the list
> of allowed pools.
> {noformat}
> This needs to be configured via
> https://github.com/apache/sling-org-apache-sling-commons-scheduler/blob/08cbef57b9623e842486624b1e29bcb1754eae54/src/main/java/org/apache/sling/commons/scheduler/impl/QuartzSchedulerConfiguration.java#L35-L39
> .
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Closed] (SLING-9746) Add Scripting FreeMarker
[ https://issues.apache.org/jira/browse/SLING-9746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-9746. -- > Add Scripting FreeMarker > > > Key: SLING-9746 > URL: https://issues.apache.org/jira/browse/SLING-9746 > Project: Sling > Issue Type: New Feature > Components: Starter >Reporter: Oliver Lietz >Assignee: Oliver Lietz >Priority: Major > Labels: Sling-12-ReleaseNotes > Fix For: Starter 12 > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-10979) Move scripting.sightly.repl bundle into a separate feature
[
https://issues.apache.org/jira/browse/SLING-10979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu closed SLING-10979.
---
> Move scripting.sightly.repl bundle into a separate feature
> --
>
> Key: SLING-10979
> URL: https://issues.apache.org/jira/browse/SLING-10979
> Project: Sling
> Issue Type: New Feature
> Components: Starter
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>Priority: Major
> Fix For: Starter 12
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The HTL REPL is a development-time tool and should not be packaged in the
> scripting feature. Consumers of Sling might mistakenly include it in their
> deployments. We should move it to its own feature file under
> {{src/main/features/app}}.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Closed] (SLING-8418) Consolidate starter-startup and startupfilter/startupfilter-disabler to use Apache Felix HC ServiceUnavailableFilter
[ https://issues.apache.org/jira/browse/SLING-8418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-8418. -- > Consolidate starter-startup and startupfilter/startupfilter-disabler to use > Apache Felix HC ServiceUnavailableFilter > > > Key: SLING-8418 > URL: https://issues.apache.org/jira/browse/SLING-8418 > Project: Sling > Issue Type: Improvement > Components: Starter >Reporter: Georg Henzler >Assignee: Georg Henzler >Priority: Major > Fix For: Starter 12, Starter Content 1.0.4 > > > See > https://github.com/apache/felix/blob/trunk/healthcheck/README.md#service-unavailable-filter > for a general-purpose mechanism from Apache Felix to replace starter-startup > and startupfilter/startupfilter-disabler > [1] > http://apache-sling.73963.n3.nabble.com/DISCUSS-Consolidate-starter-startup-and-startupfilter-startupfilter-disabler-to-use-Apache-Felix-HC-r-tt4090963.html -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-9351) Deprecate org.apache.launchpad.test-services-war
[ https://issues.apache.org/jira/browse/SLING-9351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-9351. -- > Deprecate org.apache.launchpad.test-services-war > > > Key: SLING-9351 > URL: https://issues.apache.org/jira/browse/SLING-9351 > Project: Sling > Issue Type: Task > Components: Launchpad, Testing >Reporter: Robert Munteanu >Assignee: Robert Munteanu >Priority: Major > Fix For: Starter 12 > > > With SLING-8680 we seem to have found a interesting scenario in our testing > setup: > - org.apache.sling.launchpad.test-services-war is packaged as a WAR file > with a manifest, exposing two Servlets > - before SLING-8680 we only checked for a manifest when transforming > resources, now we reject the WAR file > - we have two tests that validate that those servlets are running properly - > see [WarSelectorServletTest.java > (permalink)|https://github.com/apache/sling-org-apache-sling-launchpad-integration-tests/blob/49e5c948a0115566f778a5696e7f3df45e5dd3f5/src/main/java/org/apache/sling/launchpad/webapp/integrationtest/servlets/resolution/WarSelectorServletTest.java] > IMO we should not test or support this scenario (WAR files installed as OSGi > bundles) as it's a quite convoluted and specific scenario. > Therefore I propose that we retire this module following our [Deprecated > Sling Modules > process|https://sling.apache.org/documentation/development/deprecating-sling-modules.html] > and delete the two tests. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-9118) Sling fails to start when database exists but 'sling' directory is missing
[ https://issues.apache.org/jira/browse/SLING-9118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-9118. -- > Sling fails to start when database exists but 'sling' directory is missing > -- > > Key: SLING-9118 > URL: https://issues.apache.org/jira/browse/SLING-9118 > Project: Sling > Issue Type: Bug >Reporter: Ben Radey >Assignee: Robert Munteanu >Priority: Major > Fix For: Starter 12 > > Attachments: drop-mongo.sh, error.log, fm-launch.zip, karaf.log, > recreateSlingReplicaSet.sh, run-mongo.sh, run-sling-initial.sh, > run-sling-second.sh, sling-startup-error.log.txt > > > # Create a persistent mongodb to use with Sling. > # Start sling using the mongodb. > # Stop sling. > # Remove 'sling' directory. > # Attempt to restart sling. Ultimately, sling fails to start. > > Steps to reproduce with attached scripts: > # Run [^run-mongo.sh] . This creates a MongoDB 3.6 container named > _mongo-sling_ > # Run [^run-sling-initial.sh]. This starts up Sling in the oak_mongo runmode, > shuts it down after it's (probably) started up > # Run [^run-sling-second.sh]. This moves away the sling directory and starts > up a new instance. This always fails > For cleanup, the [^drop-mongo.sh] script stops and removes the _mongo-sling_ > container. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-9818) Move repoinit statements out of feature files
[ https://issues.apache.org/jira/browse/SLING-9818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-9818. -- > Move repoinit statements out of feature files > - > > Key: SLING-9818 > URL: https://issues.apache.org/jira/browse/SLING-9818 > Project: Sling > Issue Type: Improvement > Components: Starter >Reporter: Robert Munteanu >Assignee: Robert Munteanu >Priority: Minor > Fix For: Starter 12 > > > With SLING-9725 we can now store the repoinit declarations outside the > feature model, which is IMO much more readable. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-6196) Add an OSGi Installer factory for content packages
[ https://issues.apache.org/jira/browse/SLING-6196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-6196. -- > Add an OSGi Installer factory for content packages > -- > > Key: SLING-6196 > URL: https://issues.apache.org/jira/browse/SLING-6196 > Project: Sling > Issue Type: Sub-task > Components: General >Reporter: Robert Munteanu >Assignee: Konrad Windszus >Priority: Major > Labels: Sling-12-ReleaseNotes > Fix For: Starter 12 > > > We are currently missing support for installing content packages through the > provisioning model. There are currently two open source options available: > - https://github.com/apache/sling-org-apache-sling-installer-factory-packages > - https://github.com/ist-dresden/composum/tree/develop/sling/core/pckginstall > We should pick one of them and make sure that the efforts converge towards a > single implementation, rather than having two exist and only one being used. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-10402) MongoDB doesn't work anymore with Sling Starter
[
https://issues.apache.org/jira/browse/SLING-10402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu closed SLING-10402.
---
> MongoDB doesn't work anymore with Sling Starter
> ---
>
> Key: SLING-10402
> URL: https://issues.apache.org/jira/browse/SLING-10402
> Project: Sling
> Issue Type: Bug
> Components: Starter
>Affects Versions: Starter 12
> Environment: Sling-Starter 12-SNAPSHOT (commit a6b94beb7b) with JDK
> 11 on MacOS
>Reporter: Hans-Peter Stoerr
>Assignee: Robert Munteanu
>Priority: Major
> Fix For: Starter 12
>
> Time Spent: 3h 40m
> Remaining Estimate: 0h
>
> When starting the Sling Starter 12 SNAPSHOT with, the Repository doesn't seem
> to work properly right now when I'm using MongoDB. It starts up, but when I
> open http://localhost:8080/bin/browser.html, I get an exception reading from
> the database (see below). I tried with mongodb 4.4.6 (the latest one) and
> 4.0.3. This issue seems to be connected to the version of
> org.mongodb:mongo-java-driver - it came in when it was upgraded from 3.8.2 to
> 3.12.7; if I downgrade to 3.10.2 it works, but with 3.11.3, 3.12.7 or 3.12.8
> it doesn't.
> {code}
> Caused by: java.lang.RuntimeException: failed to read block from backend, id
> 6e01a3001107903ee3971f74d9ba7e4bf6d512d47b1006b708f7ca295658fead@0
> at
> org.apache.jackrabbit.oak.spi.blob.AbstractBlobStore.load(AbstractBlobStore.java:509)
> at
> org.apache.jackrabbit.oak.spi.blob.AbstractBlobStore.readBlock(AbstractBlobStore.java:500)
> at
> org.apache.jackrabbit.oak.spi.blob.AbstractBlobStore.readBlob(AbstractBlobStore.java:486)
> at
> org.apache.jackrabbit.oak.spi.blob.BlobStoreInputStream.read(BlobStoreInputStream.java:45)
> ... 96 more
> Caused by: java.lang.UnsupportedOperationException: The BsonCodec can only
> encode to Bson
> at org.bson.codecs.BsonCodec.decode(BsonCodec.java:48)
> at org.bson.codecs.BsonCodec.decode(BsonCodec.java:33)
> at
> com.mongodb.operation.CommandResultArrayCodec.decode(CommandResultArrayCodec.java:52)
> at
> com.mongodb.operation.CommandResultDocumentCodec.readValue(CommandResultDocumentCodec.java:60)
> at org.bson.codecs.BsonDocumentCodec.decode(BsonDocumentCodec.java:84)
> at org.bson.codecs.BsonDocumentCodec.decode(BsonDocumentCodec.java:41)
> at org.bson.codecs.configuration.LazyCodec.decode(LazyCodec.java:47)
> at
> org.bson.codecs.BsonDocumentCodec.readValue(BsonDocumentCodec.java:101)
> at
> com.mongodb.operation.CommandResultDocumentCodec.readValue(CommandResultDocumentCodec.java:63)
> at org.bson.codecs.BsonDocumentCodec.decode(BsonDocumentCodec.java:84)
> at org.bson.codecs.BsonDocumentCodec.decode(BsonDocumentCodec.java:41)
> at
> com.mongodb.internal.connection.ReplyMessage.(ReplyMessage.java:51)
> at
> com.mongodb.internal.connection.InternalStreamConnection.getCommandResult(InternalStreamConnection.java:413)
> at
> com.mongodb.internal.connection.InternalStreamConnection.receiveCommandMessageResponse(InternalStreamConnection.java:309)
> at
> com.mongodb.internal.connection.InternalStreamConnection.sendAndReceive(InternalStreamConnection.java:259)
> at
> com.mongodb.internal.connection.UsageTrackingInternalConnection.sendAndReceive(UsageTrackingInternalConnection.java:99)
> at
> com.mongodb.internal.connection.DefaultConnectionPool$PooledConnection.sendAndReceive(DefaultConnectionPool.java:450)
> at
> com.mongodb.internal.connection.CommandProtocolImpl.execute(CommandProtocolImpl.java:72)
> at
> com.mongodb.internal.connection.DefaultServer$DefaultServerProtocolExecutor.execute(DefaultServer.java:218)
> at
> com.mongodb.internal.connection.DefaultServerConnection.executeProtocol(DefaultServerConnection.java:269)
> at
> com.mongodb.internal.connection.DefaultServerConnection.command(DefaultServerConnection.java:131)
> at
> com.mongodb.internal.connection.DefaultServerConnection.command(DefaultServerConnection.java:123)
> at
> com.mongodb.operation.CommandOperationHelper.executeCommand(CommandOperationHelper.java:343)
> at
> com.mongodb.operation.CommandOperationHelper.executeCommand(CommandOperationHelper.java:334)
> at
> com.mongodb.operation.CommandOperationHelper.executeCommandWithConnection(CommandOperationHelper.java:220)
> at com.mongodb.operation.FindOperation$1.call(FindOperation.java:731)
> at com.mongodb.operation.FindOperation$1.call(FindOperation.java:725)
> at
> com.mongodb.operation.OperationHelper.withReadConnectionSource(OperationHelper.java:463)
> at com.mongodb.operation.FindOperation.execute(FindOperation.java:725)
> at
[jira] [Closed] (SLING-8080) Almost all ITs fail after the Starter 11 release
[
https://issues.apache.org/jira/browse/SLING-8080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu closed SLING-8080.
--
> Almost all ITs fail after the Starter 11 release
>
>
> Key: SLING-8080
> URL: https://issues.apache.org/jira/browse/SLING-8080
> Project: Sling
> Issue Type: Bug
> Components: Starter, Testing
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>Priority: Critical
> Fix For: Starter 12
>
>
> Almost all tests fail:
> {noformat}
> [ERROR] Tests run: 575, Failures: 561, Errors: 10, Skipped: 1
> {noformat}
> I noticed that Sling is permanently in the 'Apache Sling is starting up'
> phase.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Closed] (SLING-11140) Update bundles referenced in sling starter to the latest releases
[
https://issues.apache.org/jira/browse/SLING-11140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu closed SLING-11140.
---
> Update bundles referenced in sling starter to the latest releases
> -
>
> Key: SLING-11140
> URL: https://issues.apache.org/jira/browse/SLING-11140
> Project: Sling
> Issue Type: Improvement
>Reporter: Eric Norman
>Assignee: Eric Norman
>Priority: Major
> Fix For: Starter 12
>
> Time Spent: 2h 40m
> Remaining Estimate: 0h
>
> Update the sling starter to use the latest bundles - according to
> {code:java}
> mvn versions:display-dependency-updates{code}
> the sling starter is a bit out of date with the dependencies
> {noformat}
> [INFO] The following dependencies in Dependencies have newer versions:
> [INFO] com.composum.nodes:composum-nodes-commons . 3.1.0 ->
> 4.0.1
> [INFO] com.composum.nodes:composum-nodes-console . 3.1.0 ->
> 4.0.1
> [INFO] com.composum.nodes:composum-nodes-jslibs .. 3.1.0 ->
> 4.0.1
> [INFO] com.composum.nodes:composum-nodes-pckgmgr . 3.1.0 ->
> 4.0.1
> [INFO] com.composum.nodes:composum-nodes-usermgr . 3.1.0 ->
> 4.0.1
> [INFO] com.fasterxml.jackson.core:jackson-annotations .. 2.13.0 ->
> 2.13.1
> [INFO] com.fasterxml.jackson.core:jackson-core . 2.13.0 ->
> 2.13.1
> [INFO] com.fasterxml.jackson.core:jackson-databind . 2.13.0 ->
> 2.13.1
> ...
> [INFO] org.apache.felix:org.apache.felix.configadmin.plugin.interpolation
> ...
> [INFO] 1.1.2 ->
> 1.2.2
> [INFO] org.apache.felix:org.apache.felix.healthcheck.core ...
> [INFO] 2.0.10 ->
> 2.0.12
> ...
> [INFO] org.apache.felix:org.apache.felix.http.jetty 4.1.12 ->
> 4.1.14
> [INFO] org.apache.httpcomponents:httpcore-osgi . 4.4.14 ->
> 4.4.15
> [INFO] org.apache.pdfbox:fontbox ... 2.0.24 ->
> 2.0.25
> [INFO] org.apache.pdfbox:pdfbox 2.0.24 ->
> 2.0.25
> [INFO] org.apache.servicemix.bundles:org.apache.servicemix.bundles.ognl ...
> [INFO] 3.2.18_1 ->
> 3.3.2_1
> [INFO] org.apache.servicemix.bundles:org.apache.servicemix.bundles.rhino ...
> [INFO] 1.7.13_1 ->
> 1.7.14_1
> [INFO]
> org.apache.servicemix.bundles:org.apache.servicemix.bundles.thymeleaf ...
> [INFO] 3.0.12.RELEASE_1 ->
> 3.0.14.RELEASE_1
> [INFO] org.apache.sling:org.apache.sling.commons.johnzon 1.2.6 ->
> 1.2.14
> [INFO] org.apache.sling:org.apache.sling.commons.log . 5.3.0 ->
> 5.4.0
> [INFO] org.apache.sling:org.apache.sling.commons.metrics 1.2.8 ->
> 1.2.10
> [INFO] org.apache.sling:org.apache.sling.event . 4.2.20 ->
> 4.2.24
> [INFO] org.apache.sling:org.apache.sling.fsresource . 2.1.16 ->
> 2.2.0
> [INFO] org.apache.sling:org.apache.sling.i18n .. 2.5.16 ->
> 2.5.18
> [INFO] org.apache.sling:org.apache.sling.installer.core 3.11.4 ->
> 3.12.0
> [INFO] org.apache.sling:org.apache.sling.installer.factory.configuration ...
> [INFO] 1.3.4 ->
> 1.4.2
> [INFO] org.apache.sling:org.apache.sling.javax.activation 0.2.0 ->
> 0.3.0
> [INFO] org.apache.sling:org.apache.sling.jcr.base ... 3.1.6 ->
> 3.1.10
> [INFO] org.apache.sling:org.apache.sling.models.validation-impl ...
> [INFO] 1.0.0 ->
> 1.1.0
> [INFO] org.apache.sling:org.apache.sling.repoinit.parser ... 1.6.10 ->
> 1.6.12
> [INFO] org.apache.sling:org.apache.sling.resourceresolver 1.8.0 ->
> 1.8.4
> [INFO] org.apache.sling:org.apache.sling.scripting.core .. 2.3.6 ->
> 2.4.2
> [INFO] org.apache.sling:org.apache.sling.scripting.jsp ... 2.5.2 ->
> 2.5.4
> [INFO] org.apache.sling:org.apache.sling.scripting.sightly ...
> [INFO] 1.4.14-1.4.0 ->
> 1.4.16-1.4.0
> [INFO] org.apache.sling:org.apache.sling.servlets.get .. 2.1.40 ->
> 2.1.44
> [INFO] org.apache.sling:org.apache.sling.servlets.resolver ... 2.9.0 ->
> 2.9.2
> [INFO] org.apache.tika:tika-core .. 1.27 ->
> 1.28.1
> [INFO] org.apache.tika:tika-parsers ... 1.27 ->
> 1.28.1
> [INFO] org.javassist:javassist ... 3.27.0-GA ->
> 3.28.0-GA
> [INFO] org.jvnet.staxex:stax-ex .. 1.7.6 ->
> 1.8.3
> [INFO] org.slf4j:jcl-over-slf4j
[jira] [Closed] (SLING-9585) Update Jackson DataBind
[ https://issues.apache.org/jira/browse/SLING-9585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-9585. -- > Update Jackson DataBind > --- > > Key: SLING-9585 > URL: https://issues.apache.org/jira/browse/SLING-9585 > Project: Sling > Issue Type: Improvement > Components: Starter >Affects Versions: Starter 11 >Reporter: Dan Klco >Assignee: Dan Klco >Priority: Major > Fix For: Starter 12 > > > The current version of Jackson DataBind packaged in Sling Starter 11 has a > number of known vulnerabilities and should be updated. This includes critical > vulnerabilities such as: > CVE-2019-17267 > CVE-2019-17531 > CVE-2019-14540 > CVE-2019-16335 > The recommendation is to upgrade to 2.9.10.5. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-10496) Prevent warning about non-existing profile "ci"
[
https://issues.apache.org/jira/browse/SLING-10496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu closed SLING-10496.
---
> Prevent warning about non-existing profile "ci"
> ---
>
> Key: SLING-10496
> URL: https://issues.apache.org/jira/browse/SLING-10496
> Project: Sling
> Issue Type: Improvement
> Components: General
>Reporter: Konrad Windszus
>Assignee: Konrad Windszus
>Priority: Major
> Fix For: Starter 12
>
>
> Most builds with Jenkins emit the following warning
> {code}
> [WARNING] The requested profile "ci" could not be activated because it does
> not exist.
> {code}
> This is especially important for the Maven 4
> (https://issues.apache.org/jira/browse/MNG-7051) as that will break by
> default if the profile is not found.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Closed] (SLING-11168) Sling Starter 12: Unable to launch Composum
[
https://issues.apache.org/jira/browse/SLING-11168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu closed SLING-11168.
---
> Sling Starter 12: Unable to launch Composum
> ---
>
> Key: SLING-11168
> URL: https://issues.apache.org/jira/browse/SLING-11168
> Project: Sling
> Issue Type: Bug
> Components: Starter
>Affects Versions: Starter 12
>Reporter: Stefan Seifert
>Assignee: Stefan Seifert
>Priority: Major
> Fix For: Starter 12
>
> Attachments: error.log, image-2022-03-01-17-47-08-965.png,
> screenshot-1.png, starter-12-windows.log
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> environment:
> * Windows 10
> * java 11.0.13 2021-10-19 LTS
> * Sling Starter: https://github.com/apache/sling-org-apache-sling-starter
> started sling starter 12 (or actually 13-SNAPSHOT from current master branch)
> with:
> {noformat}
> mvn clean install
> java -jar target/dependency/org.apache.sling.feature.launcher.jar -f
> target/slingfeature-tmp/feature-oak_tar.json
> {noformat}
> when trying to access composum via http://localhost:8080/bin/browser.html i
> get the normal sling login (if not logged in already) and login as
> admin/admin.
> directly after this i see a blink of composum, which is replaced immediately
> with another composum login dialog:
> [^image-2022-03-01-17-47-08-965.png]
> [^error.log] from the instance
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Closed] (SLING-9824) sun.misc.Unsafe accessible in Sling Starter 12
[
https://issues.apache.org/jira/browse/SLING-9824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu closed SLING-9824.
--
> sun.misc.Unsafe accessible in Sling Starter 12
> --
>
> Key: SLING-9824
> URL: https://issues.apache.org/jira/browse/SLING-9824
> Project: Sling
> Issue Type: Bug
> Components: Starter
>Affects Versions: Starter 12
> Environment: Sling-Starter 12-SNAPSHOT (commit addb8f7b) with JDK 11
> and 13 on MacOS, JDK 11 on an x86_64 Linux
>Reporter: Hans-Peter Stoerr
>Assignee: Robert Munteanu
>Priority: Minor
> Fix For: Starter 12
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> We are having some trouble running our application on [the current Sling
> Starter 12
> snapshot|https://github.com/apache/sling-org-apache-sling-starter/tree/addb8f7ba16dfb2ab6cda1a70f98a461a7cacb7a]
> since we are using ehache 3, which uses sun.misc.Unsafe internally. This
> works with Sling Starter 11, but since Sling Starter changed to the feature
> launcher, this class seems to have disappeared from the classpath: the class
> loading of ehcache classes fails with a java.lang.NoClassDefFoundError:
> sun/misc/Unsafe
> I tried to add command line arguments
> --add-modules=jdk.unsupported
> and
> --add-opens=jdk.unsupported/sun.misc=ALL-UNNAMED
> to the launcher command line, as I've seen that suggested on the net for
> similar problems, but it didn't help.
> In fact, this doesn't seem to be the problem: even without those flags the
> jdk.unsupported module does export sun.misc:
> module
> { name: jdk.unsupported@11.0.6, [mandated java.base], exports:
> [com.sun.nio.file, sun.misc, sun.reflect], opens: [sun.misc, sun.reflect] }
> So it seems the module is loaded, but not used to load the class.
> The easiest way to reproduce the problem is to add this to some JSP:
> <%
> Class clazz = sun.misc.Unsafe.class;
> %>
> In case that matters: I tried JDK 11 and 13 on MacOS, as well as JDK 11 on
> an x86_64 Linux.
> This works on Sling Starter 11, but not the current 12 snapshot.
> The workaround to add
> {{-D org.osgi.framework.system.packages.extra=sun.misc}}
> to the command line, which was thankfully suggested [in the mailing
> list|https://www.mail-archive.com/users@sling.apache.org/msg05423.html], does
> work. But I feel it is not a particularily clean solution. It also does
> something else than what happens on Sling Starter 11 : now the sun.misc
> package is listed in the exports list of the felix framework bundle
> [http://localhost:9090/system/console/bundles/0] . Not sure whether this is
> good or bad.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Closed] (SLING-10400) Update bundles in sling starter
[
https://issues.apache.org/jira/browse/SLING-10400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu closed SLING-10400.
---
> Update bundles in sling starter
> ---
>
> Key: SLING-10400
> URL: https://issues.apache.org/jira/browse/SLING-10400
> Project: Sling
> Issue Type: Sub-task
>Reporter: Eric Norman
>Assignee: Eric Norman
>Priority: Major
> Fix For: Starter 12
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Update the sling starter to use the latest bundles changed by SLING-
> Specifically updates to these:
> {noformat}
> [INFO] The following dependencies in Dependencies have newer versions:
> [INFO] org.apache.sling:org.apache.sling.scripting.core .. 2.3.4 ->
> 2.3.6
> [INFO] org.apache.sling:org.apache.sling.scripting.jsp ... 2.5.0 ->
> 2.5.2
> [INFO] org.apache.sling:org.apache.sling.scripting.sightly ...
> [INFO] 1.4.6-1.4.0 ->
> 1.4.8-1.4.0
> [INFO] org.apache.sling:org.apache.sling.servlets.resolver ...
> [INFO] 2.7.12 ->
> 2.7.14{noformat}
> And this new required bundle:
> {noformat}
> org.apache.sling:org.apache.sling.scripting.spi:1.0.2{noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Closed] (SLING-8299) Remove httpclient 3.x from the Sling Starter
[ https://issues.apache.org/jira/browse/SLING-8299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-8299. -- > Remove httpclient 3.x from the Sling Starter > > > Key: SLING-8299 > URL: https://issues.apache.org/jira/browse/SLING-8299 > Project: Sling > Issue Type: Improvement > Components: Starter >Reporter: Robert Munteanu >Assignee: Robert Munteanu >Priority: Major > Fix For: Starter 12 > > > It seems this is unused so we should remove it. We already have version 4 in > the starter. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-11143) Work around SLING-10831 by adding an add-opens flag to the Starter entrypoint
[ https://issues.apache.org/jira/browse/SLING-11143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-11143. --- > Work around SLING-10831 by adding an add-opens flag to the Starter entrypoint > - > > Key: SLING-11143 > URL: https://issues.apache.org/jira/browse/SLING-11143 > Project: Sling > Issue Type: Sub-task > Components: Starter >Reporter: Robert Munteanu >Assignee: Robert Munteanu >Priority: Major > Fix For: Starter 12 > > Time Spent: 40m > Remaining Estimate: 0h > > Until we get SLING-10831 properly fixed we should ensure that the Docker > image does not print the error by default. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Closed] (SLING-11171) WARN "The provided service user id 'serviceuser--org.apache.sling.auth.core' is not a known JCR system user id and therefore not allowed in the Sling Service User Mapper.
[
https://issues.apache.org/jira/browse/SLING-11171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu closed SLING-11171.
---
> WARN "The provided service user id 'serviceuser--org.apache.sling.auth.core'
> is not a known JCR system user id and therefore not allowed in the Sling
> Service User Mapper."
> ---
>
> Key: SLING-11171
> URL: https://issues.apache.org/jira/browse/SLING-11171
> Project: Sling
> Issue Type: Bug
> Components: Starter
>Affects Versions: Starter 12
>Reporter: Konrad Windszus
>Assignee: Robert Munteanu
>Priority: Major
> Fix For: Starter 12
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The warning is emitted when launching the Sling Starter and seem to be
> related to SLING-9622. Is a service user configuration now required? Why is
> it falling back to such a weird user id in case no mapping is provided?
> {code}
> 02.03.2022 17:54:11.343 *WARN* [pool-10-thread-1]
> org.apache.sling.jcr.resource.internal.JcrSystemUserValidator The provided
> service user id 'serviceuser--org.apache.sling.auth.core' is not a known JCR
> system user id and therefore not allowed in the Sling Service User Mapper.
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
