[Jenkins] Sling » Modules » sling-org-apache-sling-launchpad-testing » master #950 is FIXED
Please see https://ci-builds.apache.org/job/Sling/job/modules/job/sling-org-apache-sling-launchpad-testing/job/master/950/ for details. No further emails will be sent until the status of the build is changed.
[jira] [Resolved] (SLING-11179) Update Jetbrains annotations to version 23
[ https://issues.apache.org/jira/browse/SLING-11179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus resolved SLING-11179. - Assignee: Konrad Windszus Resolution: Fixed Fixed in https://github.com/apache/sling-parent/commit/331d8f280ba6bb94d4f20814fdf5c76c4cbb07cd. > Update Jetbrains annotations to version 23 > -- > > Key: SLING-11179 > URL: https://issues.apache.org/jira/browse/SLING-11179 > Project: Sling > Issue Type: Improvement > Components: General >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > Fix For: Parent 48 > > > https://github.com/JetBrains/java-annotations/releases -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (SLING-11179) Update Jetbrains annotations to version 23
Konrad Windszus created SLING-11179: --- Summary: Update Jetbrains annotations to version 23 Key: SLING-11179 URL: https://issues.apache.org/jira/browse/SLING-11179 Project: Sling Issue Type: Improvement Components: General Reporter: Konrad Windszus Fix For: Parent 48 https://github.com/JetBrains/java-annotations/releases -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (SLING-11178) Update to animal-sniffer-m-p 1.21
[ https://issues.apache.org/jira/browse/SLING-11178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus reassigned SLING-11178: --- Assignee: Konrad Windszus > Update to animal-sniffer-m-p 1.21 > - > > Key: SLING-11178 > URL: https://issues.apache.org/jira/browse/SLING-11178 > Project: Sling > Issue Type: Improvement > Components: General >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > Fix For: Parent 48 > > > https://github.com/mojohaus/animal-sniffer/releases/tag/animal-sniffer-parent-1.21 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (SLING-11178) Update to animal-sniffer-m-p 1.21
[ https://issues.apache.org/jira/browse/SLING-11178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus resolved SLING-11178. - Resolution: Fixed Fixed in https://github.com/apache/sling-parent/commit/6b6ad1e493f201be9d42cbe158f360931ad0e0ab. > Update to animal-sniffer-m-p 1.21 > - > > Key: SLING-11178 > URL: https://issues.apache.org/jira/browse/SLING-11178 > Project: Sling > Issue Type: Improvement > Components: General >Reporter: Konrad Windszus >Priority: Major > Fix For: Parent 48 > > > https://github.com/mojohaus/animal-sniffer/releases/tag/animal-sniffer-parent-1.21 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (SLING-11178) Update to animal-sniffer-m-p 1.21
Konrad Windszus created SLING-11178: --- Summary: Update to animal-sniffer-m-p 1.21 Key: SLING-11178 URL: https://issues.apache.org/jira/browse/SLING-11178 Project: Sling Issue Type: Improvement Components: General Reporter: Konrad Windszus Fix For: Parent 48 https://github.com/mojohaus/animal-sniffer/releases/tag/animal-sniffer-parent-1.21 -- This message was sent by Atlassian Jira (v8.20.1#820001)
[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-1053709995 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-1058312583 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-feature-analyser] anchela opened a new pull request #35: SLING-11177 : Update repo-init parser dependency to 1.6.14
anchela opened a new pull request #35: URL: https://github.com/apache/sling-org-apache-sling-feature-analyser/pull/35 once "Apache Sling Repoinit Parser 1.6.14" is officially released the dependency in the feature analyzer should be adjusted afaik to make sure new language features can be used. -- 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
Re: [VOTE] Release Apache Sling Repoinit Parser 1.6.14, Apache Sling Repoinit JCR 1.1.38
Le jeu. 3 mars 2022 à 10:56, ang...@apache.org a écrit : ... > Please vote to approve this release: +1 -Bertrand
[jira] [Comment Edited] (SLING-11168) Sling Starter 12: Unable to launch Composum
[
https://issues.apache.org/jira/browse/SLING-11168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500773#comment-17500773
]
Konrad Windszus edited comment on SLING-11168 at 3/3/22, 2:08 PM:
--
bq. the problem is that some content from the initial bundle content are
created as files instead of a node structure
This sounds like a race condition of
https://github.com/apache/sling-org-apache-sling-jcr-contentloader/blob/master/src/main/java/org/apache/sling/jcr/contentloader/internal/ContentReaderWhiteboard.java.
We somehow need to ensure that all content readers are registered before
https://github.com/apache/sling-org-apache-sling-jcr-contentloader/blob/master/src/main/java/org/apache/sling/jcr/contentloader/internal/BundleContentLoaderListener.java
kicks in.
was (Author: kwin):
bq. the problem is that some content from the initial bundle content are
created as files instead of a node structure
This sounds like a race condition of
https://github.com/apache/sling-org-apache-sling-jcr-contentloader/blob/master/src/main/java/org/apache/sling/jcr/contentloader/internal/ContentReaderWhiteboard.java.
We somehow need to assure that all content readers are registered before
https://github.com/apache/sling-org-apache-sling-jcr-contentloader/blob/master/src/main/java/org/apache/sling/jcr/contentloader/internal/BundleContentLoaderListener.java
kicks in.
> 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
>Priority: Major
> Attachments: error.log, image-2022-03-01-17-47-08-965.png,
> screenshot-1.png, starter-12-windows.log
>
>
> 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] [Comment Edited] (SLING-11168) Sling Starter 12: Unable to launch Composum
[
https://issues.apache.org/jira/browse/SLING-11168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500773#comment-17500773
]
Konrad Windszus edited comment on SLING-11168 at 3/3/22, 2:08 PM:
--
bq. the problem is that some content from the initial bundle content are
created as files instead of a node structure
This sounds like a race condition of
https://github.com/apache/sling-org-apache-sling-jcr-contentloader/blob/master/src/main/java/org/apache/sling/jcr/contentloader/internal/ContentReaderWhiteboard.java.
We somehow need to assure that all content readers are registered before
https://github.com/apache/sling-org-apache-sling-jcr-contentloader/blob/master/src/main/java/org/apache/sling/jcr/contentloader/internal/BundleContentLoaderListener.java
kicks in.
was (Author: kwin):
> the problem is that some content from the initial bundle content are created
> as files instead of a node structure
This sounds like a race condition of
https://github.com/apache/sling-org-apache-sling-jcr-contentloader/blob/master/src/main/java/org/apache/sling/jcr/contentloader/internal/ContentReaderWhiteboard.java.
We somehow need to assure that all content readers are registered before
https://github.com/apache/sling-org-apache-sling-jcr-contentloader/blob/master/src/main/java/org/apache/sling/jcr/contentloader/internal/BundleContentLoaderListener.java
kicks in.
> 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
>Priority: Major
> Attachments: error.log, image-2022-03-01-17-47-08-965.png,
> screenshot-1.png, starter-12-windows.log
>
>
> 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] [Commented] (SLING-11168) Sling Starter 12: Unable to launch Composum
[
https://issues.apache.org/jira/browse/SLING-11168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500773#comment-17500773
]
Konrad Windszus commented on SLING-11168:
-
> the problem is that some content from the initial bundle content are created
> as files instead of a node structure
This sounds like a race condition of
https://github.com/apache/sling-org-apache-sling-jcr-contentloader/blob/master/src/main/java/org/apache/sling/jcr/contentloader/internal/ContentReaderWhiteboard.java.
We somehow need to assure that all content readers are registered before
https://github.com/apache/sling-org-apache-sling-jcr-contentloader/blob/master/src/main/java/org/apache/sling/jcr/contentloader/internal/BundleContentLoaderListener.java
kicks in.
> 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
>Priority: Major
> Attachments: error.log, image-2022-03-01-17-47-08-965.png,
> screenshot-1.png, starter-12-windows.log
>
>
> 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)
Re: [VOTE] Release Apache Sling Repoinit Parser 1.6.14, Apache Sling Repoinit JCR 1.1.38
+1 On Thu, Mar 3, 2022 at 9:03 AM Stefan Seifert wrote: > +1 > > stefan >
RE: [VOTE] Release Apache Sling Repoinit Parser 1.6.14, Apache Sling Repoinit JCR 1.1.38
+1 stefan
[jira] [Commented] (SLING-11168) Sling Starter 12: Unable to launch Composum
[
https://issues.apache.org/jira/browse/SLING-11168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500771#comment-17500771
]
Stefan Seifert commented on SLING-11168:
good idea - i'm not familiar how to switch best from bundles to content
packages in the feature model of the starter - if you can prepare a branch than
i can give it a try.
> 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
>Priority: Major
> Attachments: error.log, image-2022-03-01-17-47-08-965.png,
> screenshot-1.png, starter-12-windows.log
>
>
> 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)
Re: [VOTE] Release Apache Sling Repoinit Parser 1.6.14, Apache Sling Repoinit JCR 1.1.38
+1 regards, Karl On Thu, Mar 3, 2022 at 2:45 PM ang...@apache.org wrote: > > [x] +1 Approve the release > > NOTE: the usage instruction below did not contain the right id. > > should obviously be > > > sh check_staged_release.sh 2605 /tmp/sling-staging > > kind regards > angela > > > On 03.03.22 10:56, ang...@apache.org wrote: > > Hi, > > > > We solved the following issues in this release: > > > > https://issues.apache.org/jira/projects/SLING/versions/12351292 > > https://issues.apache.org/jira/projects/SLING/versions/12350313 > > > > Staging repository: > > https://repository.apache.org/content/repositories/orgapachesling-2605 > > > > You can use this UNIX script to download the release and verify the > > signatures: > > https://gitbox.apache.org/repos/asf?p=sling-tooling-release.git;a=blob;f=check_staged_release.sh;hb=HEAD > > > > > > Usage: > > sh check_staged_release.sh 2601 /tmp/sling-staging > > > > Please vote to approve this release: > > > >[ ] +1 Approve the release > >[ ] 0 Don't care > >[ ] -1 Don't release, because ... > > > > This majority vote is open for at least 72 hours. > > > > Kind regards > > Angela -- Karl Pauls karlpa...@gmail.com
[jira] [Commented] (SLING-11168) Sling Starter 12: Unable to launch Composum
[
https://issues.apache.org/jira/browse/SLING-11168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500767#comment-17500767
]
Robert Munteanu commented on SLING-11168:
-
Thanks for digging this up [~sseifert], it makes it much easier to understand
the problem. Perhaps we should consider switching to using the composum content
package(s), as indicated at
https://github.com/ist-dresden/composum-nodes/issues/220#issuecomment-809943639
:
{quote}With Releas 2.5.0 Composum Nodes is available as a package for
installation / upgrade via package manager. This installation via package
(composum-nodes-sling-package-.zip) is the preferred solution for
future installations/upgrades of Composum Nodes. A 'setup' bundle is used to
remove an existing version of Composum Nodes before the installation of the new
version controlled by the 'setup' bundle starts. This should hopefully
eliminate the problems with the upgrade.
https://search.maven.org/search?q=a:composum-nodes-sling-package{quote}
> 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
>Priority: Major
> Attachments: error.log, image-2022-03-01-17-47-08-965.png,
> screenshot-1.png, starter-12-windows.log
>
>
> 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] [Updated] (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
]
Stefan Seifert updated SLING-11168:
---
Description:
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
was:
environment:
* Windows 10
* java 11.0.13 2021-10-19 LTS
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
> 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
>Priority: Major
> Attachments: error.log, image-2022-03-01-17-47-08-965.png,
> screenshot-1.png, starter-12-windows.log
>
>
> 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)
Re: [VOTE] Release Apache Sling Repoinit Parser 1.6.14, Apache Sling Repoinit JCR 1.1.38
[x] +1 Approve the release NOTE: the usage instruction below did not contain the right id. should obviously be > sh check_staged_release.sh 2605 /tmp/sling-staging kind regards angela On 03.03.22 10:56, ang...@apache.org wrote: Hi, We solved the following issues in this release: https://issues.apache.org/jira/projects/SLING/versions/12351292 https://issues.apache.org/jira/projects/SLING/versions/12350313 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-2605 You can use this UNIX script to download the release and verify the signatures: https://gitbox.apache.org/repos/asf?p=sling-tooling-release.git;a=blob;f=check_staged_release.sh;hb=HEAD Usage: sh check_staged_release.sh 2601 /tmp/sling-staging Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This majority vote is open for at least 72 hours. Kind regards Angela
[jira] [Commented] (SLING-11168) Sling Starter 12: Unable to launch Composum
[
https://issues.apache.org/jira/browse/SLING-11168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500757#comment-17500757
]
Stefan Seifert commented on SLING-11168:
it seems the problem is already discussed in
https://github.com/ist-dresden/composum-nodes/issues/220 (discussion started
dec 2020!).
it was also bothering peregrine CMS:
https://github.com/headwirecom/peregrine-cms/issues/569
last comment from [~reusr1] was:
{quote}
this issue is now limited to windows 10 and some newer jvm's - the problem is
that some content from the initial bundle content are created as files instead
of a node structure - the problem is tracked as well in
ist-dresden/composum-nodes#220
{quote}
> 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
>Priority: Major
> Attachments: error.log, image-2022-03-01-17-47-08-965.png,
> screenshot-1.png, starter-12-windows.log
>
>
> environment:
> * Windows 10
> * java 11.0.13 2021-10-19 LTS
> 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] [Commented] (SLING-11168) Sling Starter 12: Unable to launch Composum
[
https://issues.apache.org/jira/browse/SLING-11168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500744#comment-17500744
]
Stefan Seifert commented on SLING-11168:
it seems to be more a composum issue. the only difference is see when opening
componsum on a working instance compared to a broken instance is the content of
this JS file:
http://localhost:8080/bin/public/clientlibs.min.js/PsEKh_JItUQ/composum.nodes.console.base.js
on the broken instance a whole block is missing starting with
{{(function(g){window.composum=window.CPM=window.CPM||{};CPM.namespace...}}
this block is setting up (amongst other) a method {{window.core.getWidget}}
within the browser - and because this is missing, the additional login dialog
pops in
([code|https://github.com/ist-dresden/composum-nodes/blob/dad4929d332358cb35d494f4e48e94a9f2806566/console/src/main/resources/root/libs/composum/nodes/console/components/tryLogin/tryLogin.jsp#L54-L68]).
the question is: why is the composum JS file missing this part when started on
windows. the actual error message shown in the composum login dialog is
misleading.
> 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
>Priority: Major
> Attachments: error.log, image-2022-03-01-17-47-08-965.png,
> screenshot-1.png, starter-12-windows.log
>
>
> environment:
> * Windows 10
> * java 11.0.13 2021-10-19 LTS
> 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)
[GitHub] [sling-org-apache-sling-starter] sonarcloud[bot] commented on pull request #56: SLING-9624 rely on Felix defaults for system packages exports
sonarcloud[bot] commented on pull request #56: URL: https://github.com/apache/sling-org-apache-sling-starter/pull/56#issuecomment-1058029481 Kudos, SonarCloud Quality Gate passed!  [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-starter=56=false=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-starter=56=false=BUG) [0 Bugs](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-starter=56=false=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-starter=56=false=VULNERABILITY) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-starter=56=false=VULNERABILITY) [0 Vulnerabilities](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-starter=56=false=VULNERABILITY) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-starter=56=false=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-starter=56=false=SECURITY_HOTSPOT) [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-starter=56=false=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-starter=56=false=CODE_SMELL) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-starter=56=false=CODE_SMELL) [0 Code Smells](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-starter=56=false=CODE_SMELL) [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-starter=56) No Coverage information [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-starter=56=duplicated_lines_density=list) No Duplication information -- 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-9572) JCR RepoInit Web Console
[ https://issues.apache.org/jira/browse/SLING-9572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Klco closed SLING-9572. --- > JCR RepoInit Web Console > > > Key: SLING-9572 > URL: https://issues.apache.org/jira/browse/SLING-9572 > Project: Sling > Issue Type: New Feature >Affects Versions: Repoinit JCR 1.1.26 >Reporter: Dan Klco >Assignee: Dan Klco >Priority: Minor > > It would be nice to have an OSGi Console for testing the JCR RepoInit > configuration scripts without having to create OSGi Configurations. > The Web Console should have the following capabilities: > - Parse the RepoInit commands > - Display the parsed commands > - Optionally execute the commands -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (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 ] Konrad Windszus reassigned SLING-9624: -- Assignee: Konrad Windszus > 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 13 > > Time Spent: 10m > Remaining Estimate: 0h > > Instead of using a Sling specific "org.osgi.framework.system.packages" > property > (https://github.com/apache/sling-org-apache-sling-starter/blob/5f44b7f6c6b75e4cfd5574fb701c3e7eca8405ef/src/main/provisioning/launchpad.txt#L26) > we should just rely on the Felix default > (https://github.com/apache/felix-dev/blob/master/framework/src/main/resources/default.properties) > to not miss to export all relevant packages for the different JREs > compare with > https://lists.apache.org/thread.html/r0aa3c02c38b5026e24684a00de3c6c8506e166334e77892ac2ee0ab3%40%3Cdev.sling.apache.org%3E. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (SLING-9572) JCR RepoInit Web Console
[ https://issues.apache.org/jira/browse/SLING-9572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Klco resolved SLING-9572. - Resolution: Won't Do Discussed on dev@sling, feedback was that there are better alternatives to check repoinit scripts closer to the build process. > JCR RepoInit Web Console > > > Key: SLING-9572 > URL: https://issues.apache.org/jira/browse/SLING-9572 > Project: Sling > Issue Type: New Feature >Affects Versions: Repoinit JCR 1.1.26 >Reporter: Dan Klco >Assignee: Dan Klco >Priority: Minor > > It would be nice to have an OSGi Console for testing the JCR RepoInit > configuration scripts without having to create OSGi Configurations. > The Web Console should have the following capabilities: > - Parse the RepoInit commands > - Display the parsed commands > - Optionally execute the commands -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [sling-org-apache-sling-starter] kwin commented on a change in pull request #56: SLING-9624 rely on Felix defaults for system packages exports
kwin commented on a change in pull request #56:
URL:
https://github.com/apache/sling-org-apache-sling-starter/pull/56#discussion_r818636689
##
File path: src/main/features/boot.json
##
@@ -145,16 +145,15 @@
"framework-properties":{
"localIndexDir":"${sling.home}/repository/index",
"repository.home":"${sling.home}/repository",
-
"sling.jre.java.xml":",javax.xml;version=\"2.1.0\",javax.xml.datatype;uses:=\"javax.xml.namespace\";version=\"2.1.0\",javax.xml.namespace;version=\"2.1.0\",javax.xml.parsers;uses:=\"javax.xml.validation,org.w3c.dom,org.xml.sax,org.xml.sax.helpers\";version=\"2.1.0\",javax.xml.stream;uses:=\"javax.xml.namespace,javax.xml.stream.events,javax.xml.stream.util,javax.xml.transform\";version=\"1.0.0\",javax.xml.stream.events;uses:=\"javax.xml.namespace,javax.xml.stream\";version=\"1.0.0\",javax.xml.stream.util;uses:=\"javax.xml.namespace,javax.xml.stream,javax.xml.stream.events\";version=\"1.0.0\",javax.xml.transform;version=\"2.1.0\",javax.xml.transform.dom;uses:=\"javax.xml.transform,org.w3c.dom\";version=\"2.1.0\",javax.xml.transform.sax;uses:=\"javax.xml.transform,javax.xml.transform.stream,org.xml.sax,org.xml.sax.ext\";version=\"2.1.0\",javax.xml.transform.stax;uses:=\"javax.xml.stream,javax.xml.stream.events,javax.xml.transform\";version=\"2.1.0\",javax.xml.transform.stream;u
ses:=\"javax.xml.transform\";version=\"2.1.0\",javax.xml.validation;uses:=\"javax.xml.transform,javax.xml.transform.stream,org.w3c.dom,org.w3c.dom.ls,org.xml.sax\";version=\"2.1.0\",javax.xml.xpath;uses:=\"javax.xml.namespace,org.xml.sax\";version=\"2.1.0\",org.w3c.dom;version=\"{dollar}{felix.detect.java.version}\",org.w3c.dom.bootstrap;uses:=\"org.w3c.dom\";version=\"{dollar}{felix.detect.java.version}\",org.w3c.dom.css;uses:=\"org.w3c.dom,org.w3c.dom.stylesheets,org.w3c.dom.views\";version=\"{dollar}{felix.detect.java.version}\",org.w3c.dom.events;uses:=\"org.w3c.dom,org.w3c.dom.views\";version=\"{dollar}{felix.detect.java.version}\",org.w3c.dom.html;uses:=\"org.w3c.dom\";version=\"{dollar}{felix.detect.java.version}\",org.w3c.dom.ls;uses:=\"org.w3c.dom,org.w3c.dom.events\";version=\"{dollar}{felix.detect.java.version}\",org.w3c.dom.ranges;uses:=\"org.w3c.dom\";version=\"{dollar}{felix.detect.java.version}\",org.w3c.dom.stylesheets;uses:=\"org.w3c.dom\";version=\"{dollar}{felix.d
etect.java.version}\",org.w3c.dom.traversal;uses:=\"org.w3c.dom\";version=\"{dollar}{felix.detect.java.version}\",org.w3c.dom.views;version=\"{dollar}{felix.detect.java.version}\",org.w3c.dom.xpath;uses:=\"org.w3c.dom\";version=\"{dollar}{felix.detect.java.version}\",org.xml.sax;version=\"{dollar}{felix.detect.java.version}\",org.xml.sax.ext;uses:=\"org.xml.sax,org.xml.sax.helpers\";version=\"{dollar}{felix.detect.java.version}\",org.xml.sax.helpers;uses:=\"org.xml.sax\";version=\"{dollar}{felix.detect.java.version}\"",
+// export XML packages in addition to JRE version with special
versions for backwards-compatibility reasons
+
"sling.jre-1.8.javax.xml":",javax.xml;version=\"2.1.0\",javax.xml.datatype;uses:=\"javax.xml.namespace\";version=\"2.1.0\",javax.xml.namespace;version=\"2.1.0\",javax.xml.parsers;uses:=\"javax.xml.validation,org.w3c.dom,org.xml.sax,org.xml.sax.helpers\";version=\"2.1.0\",javax.xml.stream;uses:=\"javax.xml.namespace,javax.xml.stream.events,javax.xml.stream.util,javax.xml.transform\";version=\"1.0.0\",javax.xml.stream.events;uses:=\"javax.xml.namespace,javax.xml.stream\";version=\"1.0.0\",javax.xml.stream.util;uses:=\"javax.xml.namespace,javax.xml.stream,javax.xml.stream.events\";version=\"1.0.0\",javax.xml.transform;version=\"2.1.0\",javax.xml.transform.dom;uses:=\"javax.xml.transform,org.w3c.dom\";version=\"2.1.0\",javax.xml.transform.sax;uses:=\"javax.xml.transform,javax.xml.transform.stream,org.xml.sax,org.xml.sax.ext\";version=\"2.1.0\",javax.xml.transform.stax;uses:=\"javax.xml.stream,javax.xml.stream.events,javax.xml.transform\";version=\"2.1.0\",javax.xml.transform.str
[jira] [Commented] (SLING-9624) Get rid of custom "org.osgi.framework.system.packages"
[ https://issues.apache.org/jira/browse/SLING-9624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500733#comment-17500733 ] Karl Pauls commented on SLING-9624: --- right, but the versions are the versions sling had since a long time. I don't know why they where like they where. > Get rid of custom "org.osgi.framework.system.packages" > -- > > Key: SLING-9624 > URL: https://issues.apache.org/jira/browse/SLING-9624 > Project: Sling > Issue Type: Improvement > Components: Starter >Reporter: Konrad Windszus >Priority: Major > Fix For: Starter 13 > > Time Spent: 10m > Remaining Estimate: 0h > > Instead of using a Sling specific "org.osgi.framework.system.packages" > property > (https://github.com/apache/sling-org-apache-sling-starter/blob/5f44b7f6c6b75e4cfd5574fb701c3e7eca8405ef/src/main/provisioning/launchpad.txt#L26) > we should just rely on the Felix default > (https://github.com/apache/felix-dev/blob/master/framework/src/main/resources/default.properties) > to not miss to export all relevant packages for the different JREs > compare with > https://lists.apache.org/thread.html/r0aa3c02c38b5026e24684a00de3c6c8506e166334e77892ac2ee0ab3%40%3Cdev.sling.apache.org%3E. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [sling-org-apache-sling-starter] kwin opened a new pull request #56: SLING-9624 rely on Felix defaults for system packages exports
kwin opened a new pull request #56: URL: https://github.com/apache/sling-org-apache-sling-starter/pull/56 Export javax.xml packages additionally with traditional Sling version numbers Update Felix to 7.0.3 -- 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-11168) Sling Starter 12: Unable to launch Composum
[
https://issues.apache.org/jira/browse/SLING-11168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500723#comment-17500723
]
Stefan Seifert commented on SLING-11168:
i was not using WSL, but starting it directly from windows.
just tested it: it actually works with WSL on the same machine.
will try to look a bit deeper as it seems i'm currently the only one to
reproduce the problem reliably.
> 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
>Priority: Major
> Attachments: error.log, image-2022-03-01-17-47-08-965.png,
> screenshot-1.png, starter-12-windows.log
>
>
> environment:
> * Windows 10
> * java 11.0.13 2021-10-19 LTS
> 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] [Comment Edited] (SLING-9624) Get rid of custom "org.osgi.framework.system.packages"
[
https://issues.apache.org/jira/browse/SLING-9624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500702#comment-17500702
]
Konrad Windszus edited comment on SLING-9624 at 3/3/22, 12:43 PM:
--
When removing the sling specific "org.osgi.framework.system.packages" property
starting fails with
{code}
[ERROR] [bundle-packages]
org.apache.servicemix.specs:org.apache.servicemix.specs.jaxb-api-2.3:2.3_3: is
importing package(s) Package javax.xml.stream;version=[1.0,2) in start level 1
but no bundle is exporting these for that start level in the required version
range.
{code}
Seems that the servicemix XML bundles assume versioning according to the
underlying standard, i.e. Stax 1.x but Felix exports those packages by default
with the version of the detected Java runtime
(https://github.com/apache/felix-dev/blob/5becb8f971f904334eb3f32e7eaa9126186a2898/framework/src/main/resources/default.properties#L261-L293).
Maybe it is time to switch from servicemix to the bundles from Eclipse (still
under the old namespace javax.xml) which is licensed under BSD-3
(https://github.com/eclipse-ee4j/jaxb-api/blob/2.3.3/jaxb-api/pom.xml#L277).
Alternatively we can export those packages in addition also with version 1.0
(for backwards-compatibility)
was (Author: kwin):
When removing the sling specific "org.osgi.framework.system.packages" property
starting fails with
{code}
[ERROR] [bundle-packages]
org.apache.servicemix.specs:org.apache.servicemix.specs.jaxb-api-2.3:2.3_3: is
importing package(s) Package javax.xml.stream;version=[1.0,2) in start level 1
but no bundle is exporting these for that start level in the required version
range.
{code}
Seems that the servicemix XML bundles assume versioning according to the
underlying standard, i.e. JAXP 1.x but Felix exports those packages by default
with the version of the detected Java runtime
(https://github.com/apache/felix-dev/blob/5becb8f971f904334eb3f32e7eaa9126186a2898/framework/src/main/resources/default.properties#L261-L293).
Maybe it is time to switch from servicemix to the bundles from Eclipse (still
under the old namespace javax.xml) which is licensed under BSD-3
(https://github.com/eclipse-ee4j/jaxb-api/blob/2.3.3/jaxb-api/pom.xml#L277).
Alternatively we can export those packages in addition also with version 1.0
(for backwards-compatibility)
> Get rid of custom "org.osgi.framework.system.packages"
> --
>
> Key: SLING-9624
> URL: https://issues.apache.org/jira/browse/SLING-9624
> Project: Sling
> Issue Type: Improvement
> Components: Starter
>Reporter: Konrad Windszus
>Priority: Major
> Fix For: Starter 13
>
>
> Instead of using a Sling specific "org.osgi.framework.system.packages"
> property
> (https://github.com/apache/sling-org-apache-sling-starter/blob/5f44b7f6c6b75e4cfd5574fb701c3e7eca8405ef/src/main/provisioning/launchpad.txt#L26)
> we should just rely on the Felix default
> (https://github.com/apache/felix-dev/blob/master/framework/src/main/resources/default.properties)
> to not miss to export all relevant packages for the different JREs
> compare with
> https://lists.apache.org/thread.html/r0aa3c02c38b5026e24684a00de3c6c8506e166334e77892ac2ee0ab3%40%3Cdev.sling.apache.org%3E.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (SLING-11173) Wrong version of org.osgi.framework exported (OSGi R7 instead of OSGi R8)
[
https://issues.apache.org/jira/browse/SLING-11173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500718#comment-17500718
]
Konrad Windszus commented on SLING-11173:
-
Maintaining manually twice is too much effort. Let us rely on Felix defaults
and only tweak via {{org.osgi.framework.system.packages.extra}}
> Wrong version of org.osgi.framework exported (OSGi R7 instead of OSGi R8)
> -
>
> Key: SLING-11173
> URL: https://issues.apache.org/jira/browse/SLING-11173
> Project: Sling
> Issue Type: Bug
> Components: Starter
>Reporter: Konrad Windszus
>Priority: Blocker
> Fix For: Starter 12
>
>
> Although Felix was updated in SLING-10409 to Felix 7 (OSGi R8 compliant) the
> package exports are still only for OSGi R7 in
> https://github.com/apache/sling-org-apache-sling-starter/blob/150e60df97a6d8911e938b76903f64d54f1201df/src/main/features/boot.json#L151.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (SLING-11173) Wrong version of org.osgi.framework exported (OSGi R7 instead of OSGi R8)
[ https://issues.apache.org/jira/browse/SLING-11173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500715#comment-17500715 ] Karl Pauls commented on SLING-11173: [~kwin], I guess you just have to adjust the exports to match, no? Unless you wanted to go with SLING-9624 - the problem there is that if you want to use the modules/classpath then we have bundles that assume that the versions are different. The correct list for the current felix osgi exports is here: https://github.com/apache/felix-dev/blob/master/framework/src/main/resources/default.properties#L108 > Wrong version of org.osgi.framework exported (OSGi R7 instead of OSGi R8) > - > > Key: SLING-11173 > URL: https://issues.apache.org/jira/browse/SLING-11173 > Project: Sling > Issue Type: Bug > Components: Starter >Reporter: Konrad Windszus >Priority: Blocker > Fix For: Starter 12 > > > Although Felix was updated in SLING-10409 to Felix 7 (OSGi R8 compliant) the > package exports are still only for OSGi R7 in > https://github.com/apache/sling-org-apache-sling-starter/blob/150e60df97a6d8911e938b76903f64d54f1201df/src/main/features/boot.json#L151. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Comment Edited] (SLING-9624) Get rid of custom "org.osgi.framework.system.packages"
[
https://issues.apache.org/jira/browse/SLING-9624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500714#comment-17500714
]
Konrad Windszus edited comment on SLING-9624 at 3/3/22, 12:33 PM:
--
I am confused by the exported version of the javax.xml packages. This is what I
found out:
||Spec||Version||Link||
|JavaTM API for XML Processing (JAXP)|1.6 (since Java
8)|https://www.jcp.org/en/jsr/detail?id=206|
|Streaming API for XML (Stax)|1.3|https://jcp.org/en/jsr/detail?id=173|
|J2METM Web Services Specification|1.1|https://jcp.org/en/jsr/detail?id=172|
|XML API for JavaTM ME|1.0|https://jcp.org/en/jsr/detail?id=280|
|XML Catalogs|Version 1.1 (only
Java9+)|https://www.oasis-open.org/committees/download.php/14809/xml-catalogs.html|
But for example package {{javax.xml.namespace}} is exported as 2.1.0 although
it implements JAXP 1.3, so I would have expected version 1.3 instead. Or is the
version number the version of the underlying implementation?
was (Author: kwin):
I am confused by the exported version of the javax.xml packages. This is what I
found out:
||Spec||Version||Link||
|JavaTM API for XML Processing (JAXP)|1.6 (since Java
8)|https://www.jcp.org/en/jsr/detail?id=206|
|Streaming API for XML (Stax)|1.3|https://jcp.org/en/jsr/detail?id=173|
|J2METM Web Services Specification|1.1|https://jcp.org/en/jsr/detail?id=172|
|XML API for JavaTM ME|1.0|https://jcp.org/en/jsr/detail?id=280|
|XML Catalogs|Version 1.1 (only
Java9+)|https://www.oasis-open.org/committees/download.php/14809/xml-catalogs.html|
But for example package {{javax.xml.namespace}} is exported as 2.1.0 although
it implements JAXP 1.3...
> Get rid of custom "org.osgi.framework.system.packages"
> --
>
> Key: SLING-9624
> URL: https://issues.apache.org/jira/browse/SLING-9624
> Project: Sling
> Issue Type: Improvement
> Components: Starter
>Reporter: Konrad Windszus
>Priority: Major
> Fix For: Starter 13
>
>
> Instead of using a Sling specific "org.osgi.framework.system.packages"
> property
> (https://github.com/apache/sling-org-apache-sling-starter/blob/5f44b7f6c6b75e4cfd5574fb701c3e7eca8405ef/src/main/provisioning/launchpad.txt#L26)
> we should just rely on the Felix default
> (https://github.com/apache/felix-dev/blob/master/framework/src/main/resources/default.properties)
> to not miss to export all relevant packages for the different JREs
> compare with
> https://lists.apache.org/thread.html/r0aa3c02c38b5026e24684a00de3c6c8506e166334e77892ac2ee0ab3%40%3Cdev.sling.apache.org%3E.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (SLING-9624) Get rid of custom "org.osgi.framework.system.packages"
[
https://issues.apache.org/jira/browse/SLING-9624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500714#comment-17500714
]
Konrad Windszus commented on SLING-9624:
I am confused by the exported version of the javax.xml packages. This is what I
found out:
||Spec||Version||Link||
|JavaTM API for XML Processing (JAXP)|1.6 (since Java
8)|https://www.jcp.org/en/jsr/detail?id=206|
|Streaming API for XML (Stax)|1.3|https://jcp.org/en/jsr/detail?id=173|
|J2METM Web Services Specification|1.1|https://jcp.org/en/jsr/detail?id=172|
|XML API for JavaTM ME|1.0|https://jcp.org/en/jsr/detail?id=280|
|XML Catalogs|Version 1.1 (only
Java9+)|https://www.oasis-open.org/committees/download.php/14809/xml-catalogs.html|
But for example package {{javax.xml.namespace}} is exported as 2.1.0 although
it implements JAXP 1.3...
> Get rid of custom "org.osgi.framework.system.packages"
> --
>
> Key: SLING-9624
> URL: https://issues.apache.org/jira/browse/SLING-9624
> Project: Sling
> Issue Type: Improvement
> Components: Starter
>Reporter: Konrad Windszus
>Priority: Major
> Fix For: Starter 13
>
>
> Instead of using a Sling specific "org.osgi.framework.system.packages"
> property
> (https://github.com/apache/sling-org-apache-sling-starter/blob/5f44b7f6c6b75e4cfd5574fb701c3e7eca8405ef/src/main/provisioning/launchpad.txt#L26)
> we should just rely on the Felix default
> (https://github.com/apache/felix-dev/blob/master/framework/src/main/resources/default.properties)
> to not miss to export all relevant packages for the different JREs
> compare with
> https://lists.apache.org/thread.html/r0aa3c02c38b5026e24684a00de3c6c8506e166334e77892ac2ee0ab3%40%3Cdev.sling.apache.org%3E.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (SLING-9624) Get rid of custom "org.osgi.framework.system.packages"
[ https://issues.apache.org/jira/browse/SLING-9624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500713#comment-17500713 ] Karl Pauls commented on SLING-9624: --- Right, that was the issue - we had bundles that have imports with version ranges that assume the old package versioning sling did. Thats why I did massage the exports of the system bundle to work with that and still pick up the modules from the jvm where possible. > Get rid of custom "org.osgi.framework.system.packages" > -- > > Key: SLING-9624 > URL: https://issues.apache.org/jira/browse/SLING-9624 > Project: Sling > Issue Type: Improvement > Components: Starter >Reporter: Konrad Windszus >Priority: Major > Fix For: Starter 13 > > > Instead of using a Sling specific "org.osgi.framework.system.packages" > property > (https://github.com/apache/sling-org-apache-sling-starter/blob/5f44b7f6c6b75e4cfd5574fb701c3e7eca8405ef/src/main/provisioning/launchpad.txt#L26) > we should just rely on the Felix default > (https://github.com/apache/felix-dev/blob/master/framework/src/main/resources/default.properties) > to not miss to export all relevant packages for the different JREs > compare with > https://lists.apache.org/thread.html/r0aa3c02c38b5026e24684a00de3c6c8506e166334e77892ac2ee0ab3%40%3Cdev.sling.apache.org%3E. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Comment Edited] (SLING-9624) Get rid of custom "org.osgi.framework.system.packages"
[
https://issues.apache.org/jira/browse/SLING-9624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500702#comment-17500702
]
Konrad Windszus edited comment on SLING-9624 at 3/3/22, 12:00 PM:
--
When removing the sling specific "org.osgi.framework.system.packages" property
starting fails with
{code}
[ERROR] [bundle-packages]
org.apache.servicemix.specs:org.apache.servicemix.specs.jaxb-api-2.3:2.3_3: is
importing package(s) Package javax.xml.stream;version=[1.0,2) in start level 1
but no bundle is exporting these for that start level in the required version
range.
{code}
Seems that the servicemix XML bundles assume versioning according to the
underlying standard, i.e. JAXP 1.x but Felix exports those packages by default
with the version of the detected Java runtime
(https://github.com/apache/felix-dev/blob/5becb8f971f904334eb3f32e7eaa9126186a2898/framework/src/main/resources/default.properties#L261-L293).
Maybe it is time to switch from servicemix to the bundles from Eclipse (still
under the old namespace javax.xml) which is licensed under BSD-3
(https://github.com/eclipse-ee4j/jaxb-api/blob/2.3.3/jaxb-api/pom.xml#L277).
Alternatively we can export those packages in addition also with version 1.0
(for backwards-compatibility)
was (Author: kwin):
When removing the sling specific "org.osgi.framework.system.packages" property
starting fails with
{code}
[ERROR] [bundle-packages]
org.apache.servicemix.specs:org.apache.servicemix.specs.jaxb-api-2.3:2.3_3: is
importing package(s) Package javax.xml.stream;version=[1.0,2) in start level 1
but no bundle is exporting these for that start level in the required version
range.
{code}
Seems that the servicemix XML bundles assume versioning according to the
underlying standard, i.e. JAXP 1.x but Felix exports those packages by default
with the version of the detected Java runtime
(https://github.com/apache/felix-dev/blob/5becb8f971f904334eb3f32e7eaa9126186a2898/framework/src/main/resources/default.properties#L261-L293).
Maybe it is time to switch from servicemix to the bundles from Eclipse (still
under the old namespace javax.xml) which is licensed under BSD-3
(https://github.com/eclipse-ee4j/jaxb-api/blob/2.3.3/jaxb-api/pom.xml#L277).
> Get rid of custom "org.osgi.framework.system.packages"
> --
>
> Key: SLING-9624
> URL: https://issues.apache.org/jira/browse/SLING-9624
> Project: Sling
> Issue Type: Improvement
> Components: Starter
>Reporter: Konrad Windszus
>Priority: Major
> Fix For: Starter 13
>
>
> Instead of using a Sling specific "org.osgi.framework.system.packages"
> property
> (https://github.com/apache/sling-org-apache-sling-starter/blob/5f44b7f6c6b75e4cfd5574fb701c3e7eca8405ef/src/main/provisioning/launchpad.txt#L26)
> we should just rely on the Felix default
> (https://github.com/apache/felix-dev/blob/master/framework/src/main/resources/default.properties)
> to not miss to export all relevant packages for the different JREs
> compare with
> https://lists.apache.org/thread.html/r0aa3c02c38b5026e24684a00de3c6c8506e166334e77892ac2ee0ab3%40%3Cdev.sling.apache.org%3E.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (SLING-9624) Get rid of custom "org.osgi.framework.system.packages"
[
https://issues.apache.org/jira/browse/SLING-9624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500702#comment-17500702
]
Konrad Windszus commented on SLING-9624:
When removing the sling specific "org.osgi.framework.system.packages" property
starting fails with
{code}
[ERROR] [bundle-packages]
org.apache.servicemix.specs:org.apache.servicemix.specs.jaxb-api-2.3:2.3_3: is
importing package(s) Package javax.xml.stream;version=[1.0,2) in start level 1
but no bundle is exporting these for that start level in the required version
range.
{code}
Seems that the servicemix XML bundles assume versioning according to the
underlying standard, i.e. JAXP 1.x but Felix exports those packages by default
with the version of the detected Java runtime
(https://github.com/apache/felix-dev/blob/5becb8f971f904334eb3f32e7eaa9126186a2898/framework/src/main/resources/default.properties#L261-L293).
Maybe it is time to switch from servicemix to the bundles from Eclipse (still
under the old namespace javax.xml) which is licensed under BSD-3
(https://github.com/eclipse-ee4j/jaxb-api/blob/2.3.3/jaxb-api/pom.xml#L277).
> Get rid of custom "org.osgi.framework.system.packages"
> --
>
> Key: SLING-9624
> URL: https://issues.apache.org/jira/browse/SLING-9624
> Project: Sling
> Issue Type: Improvement
> Components: Starter
>Reporter: Konrad Windszus
>Priority: Major
> Fix For: Starter 13
>
>
> Instead of using a Sling specific "org.osgi.framework.system.packages"
> property
> (https://github.com/apache/sling-org-apache-sling-starter/blob/5f44b7f6c6b75e4cfd5574fb701c3e7eca8405ef/src/main/provisioning/launchpad.txt#L26)
> we should just rely on the Felix default
> (https://github.com/apache/felix-dev/blob/master/framework/src/main/resources/default.properties)
> to not miss to export all relevant packages for the different JREs
> compare with
> https://lists.apache.org/thread.html/r0aa3c02c38b5026e24684a00de3c6c8506e166334e77892ac2ee0ab3%40%3Cdev.sling.apache.org%3E.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[Jenkins] Sling » Modules » sling-org-apache-sling-launchpad-testing » master #949 is BROKEN
i.http.whiteboard.context.select=(osgi.http.whiteboard.context.name=org.apache.sling),
osgi.http.whiteboard.filter.pattern=[/], request.max=-1, service.bundleid=133,
service.description=Filter for request parameter support, service.id=479,
service.ranking=2147483647, service.scope=bundle, service.vendor=The Apache
Software Foundation, sling.default.max.parameters=1,
sling.default.parameter.checkForAdditionalContainerParameters=false,
sling.default.parameter.encoding=ISO-8859-1}] Ignoring unmatching Filter service
[INFO] Apachde Felix Http Whiteboard Service stopped
[INFO] Stopped Jetty.
[INFO]
[INFO] --- tools-maven-plugin:1.4:verify-legal-files (verify-legal-files) @
org.apache.sling.launchpad.testing ---
[INFO] Checking legal files in:
org.apache.sling.launchpad.testing-13-SNAPSHOT.jar
[INFO] Checking legal files in:
org.apache.sling.launchpad.testing-13-SNAPSHOT-sources.jar
[INFO]
[INFO] --- apache-rat-plugin:0.13:check (rat-check) @
org.apache.sling.launchpad.testing ---
[INFO] Enabled default license matchers.
[INFO] Will parse SCM ignores for exclusions...
[INFO] Parsing exclusions from
/home/jenkins/workspace/e-sling-launchpad-testing_master/.gitignore
[INFO] Finished adding exclusions from SCM ignore files.
[INFO] 75 implicit excludes (use -debug for more details).
[INFO] 13 explicit excludes (use -debug for more details).
[INFO] 4 resources included (use -debug for more details)
[INFO] Rat check: Summary over all files. Unapproved: 0, unknown: 0, generated:
0, approved: 3 licenses.
[INFO]
[INFO] --- maven-failsafe-plugin:2.21.0:verify (default) @
org.apache.sling.launchpad.testing ---
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 03:43 min
[INFO] Finished at: 2022-03-03T11:27:26Z
[INFO]
[INFO] [jenkins-event-spy] Generated
/home/jenkins/workspace/e-sling-launchpad-testing_master@tmp/withMaven035092bd/maven-spy-20220303-112342-5702191750517638094413.log
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-failsafe-plugin:2.21.0:verify (default) on
project org.apache.sling.launchpad.testing: There are test failures.
[ERROR]
[ERROR] Please refer to
/home/jenkins/workspace/e-sling-launchpad-testing_master/target/failsafe-reports
for the individual test results.
[ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump,
[date].dumpstream and [date]-jvmRun[N].dumpstream.
[ERROR] -> [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/MojoFailureException
[Pipeline] }
[DevOpticsMavenPublisher] dependencies consumed: 0, artifacts produced: 0
[withMaven] Publishers: Pipeline Graph Publisher: 1 ms, CloudBees DevOptics
Gate Artifact Publisher: 34581 ms
[Pipeline] // withMaven
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // timeout
[Pipeline] stage
[Pipeline] { (Notifications)
[Pipeline] echo
Status change is BROKEN, notifications will be sent.
[Pipeline] emailext
[jira] [Resolved] (SLING-11174) Update to ASF Parent 25
[ https://issues.apache.org/jira/browse/SLING-11174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus resolved SLING-11174. - Resolution: Fixed Fixed in https://github.com/apache/sling-parent/commit/50ead69d8cac198dfb7246b47f7a6a6340b9cdaf. > Update to ASF Parent 25 > --- > > Key: SLING-11174 > URL: https://issues.apache.org/jira/browse/SLING-11174 > Project: Sling > Issue Type: Improvement > Components: General >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > Fix For: Parent 48 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (SLING-11176) Update to newest micro version of OSGi dependencies
[ https://issues.apache.org/jira/browse/SLING-11176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus resolved SLING-11176. - Resolution: Fixed Fixed in https://github.com/apache/sling-parent/commit/48b8347f44952356ef2c5a85ffe48c1b9a11cbbd. > Update to newest micro version of OSGi dependencies > --- > > Key: SLING-11176 > URL: https://issues.apache.org/jira/browse/SLING-11176 > Project: Sling > Issue Type: Improvement > Components: General >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > Fix For: Bundle Parent 48 > > Time Spent: 20m > Remaining Estimate: 0h > > There were some backwards-compatible fixes applied to several OSGi artifacts > which are compatible with the underlying chapter of the OSGi spec. All those > artifacts should be updated to the newest micro version. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [sling-parent] kwin merged pull request #23: SLING-11174 Update to ASF parent 25
kwin merged pull request #23: URL: https://github.com/apache/sling-parent/pull/23 -- 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-parent] kwin merged pull request #22: SLING-11176 use newest OSGi dependencies
kwin merged pull request #22: URL: https://github.com/apache/sling-parent/pull/22 -- 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-11172) Make API documentation link point to the (not yet published) Sling 12 javadoc
[ https://issues.apache.org/jira/browse/SLING-11172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus resolved SLING-11172. - Resolution: Fixed Fixed in https://github.com/apache/sling-org-apache-sling-starter-content/commit/e795d2565dd19fa90fbf32a8401022db80bd6ceb. > Make API documentation link point to the (not yet published) Sling 12 javadoc > - > > Key: SLING-11172 > URL: https://issues.apache.org/jira/browse/SLING-11172 > Project: Sling > Issue Type: Bug > Components: Starter >Affects Versions: Starter Content 1.0.10 >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > Fix For: Starter Content 1.0.12 > > Time Spent: 0.5h > Remaining Estimate: 0h > > The new content used in Sling Starter 12 should point to Sling 12 javadocs > instead of Sling 11 ones. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [sling-org-apache-sling-starter-content] kwin merged pull request #5: SLING-11172 Adjust API links to point to Sling 12 Javadoc
kwin merged pull request #5: URL: https://github.com/apache/sling-org-apache-sling-starter-content/pull/5 -- 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-11172) Make API documentation link point to the (not yet published) Sling 12 javadoc
[ https://issues.apache.org/jira/browse/SLING-11172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500672#comment-17500672 ] Konrad Windszus commented on SLING-11172: - [~rombert] Good idea, please create a dedicated issue for that. > Make API documentation link point to the (not yet published) Sling 12 javadoc > - > > Key: SLING-11172 > URL: https://issues.apache.org/jira/browse/SLING-11172 > Project: Sling > Issue Type: Bug > Components: Starter >Affects Versions: Starter Content 1.0.10 >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > Fix For: Starter Content 1.0.12 > > Time Spent: 20m > Remaining Estimate: 0h > > The new content used in Sling Starter 12 should point to Sling 12 javadocs > instead of Sling 11 ones. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (SLING-11173) Wrong version of org.osgi.framework exported (OSGi R7 instead of OSGi R8)
[ https://issues.apache.org/jira/browse/SLING-11173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500670#comment-17500670 ] Konrad Windszus commented on SLING-11173: - [~karlpauls] Can you help here? https://github.com/apache/sling-org-apache-sling-starter/commit/0eb7629f102f8ed6f11e20763cff67afb61f9643 upgraded from Felix 6 to Felix 7 without adjusting the framework properties. > Wrong version of org.osgi.framework exported (OSGi R7 instead of OSGi R8) > - > > Key: SLING-11173 > URL: https://issues.apache.org/jira/browse/SLING-11173 > Project: Sling > Issue Type: Bug > Components: Starter >Reporter: Konrad Windszus >Priority: Blocker > Fix For: Starter 12 > > > Although Felix was updated in SLING-10409 to Felix 7 (OSGi R8 compliant) the > package exports are still only for OSGi R7 in > https://github.com/apache/sling-org-apache-sling-starter/blob/150e60df97a6d8911e938b76903f64d54f1201df/src/main/features/boot.json#L151. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [sling-org-apache-sling-models-impl] sagarmiglani commented on pull request #34: SLING-11132 - Exception handling while clearing OSGiServiceReferences
sagarmiglani commented on pull request #34: URL: https://github.com/apache/sling-org-apache-sling-models-impl/pull/34#issuecomment-1057935614 @kwin @cziegeler @Buuhuu can we merge this, if all looks ok? -- 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
Re: [VOTE] Release Apache Sling Starter 12, Apache Sling Project Archetype 1.0.6 and associated testing modules,
For me only 1 is a blocker, as I think that running in an OSGi R8 compliant container should also be mentioned in the release notes. Konrad > Am 03.03.2022 um 11:41 schrieb Robert Munteanu : > > Hi Konrad, > >> On Wed, 2022-03-02 at 18:47 +0100, Konrad Windszus wrote: >> And I found another blocker: >> https://issues.apache.org/jira/browse/SLING-11173 < >> https://issues.apache.org/jira/browse/SLING-11173> which deserves >> fixing prior to release. >> Therefore voting -1. > > Thanks for looking into this and for raising issues. > > I'd like to make sure I understand how severe these bugs are. Not > necessarilly because of the time needed to redo the release, but > because I'd like to keep the '12' version for the next Starter release > and I'm not sure that this is feasible. > > Current we have > > 1. SLING-11173 - Wrong version of org.osgi.framework exported (OSGi R7 > instead of OSGi R8) > 2. SLING-11172 - Make API documentation link point to the (not yet > published) Sling 12 javadoc > 3. 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." > 4. SLING-11168 - Sling Starter 12: Unable to launch Composum > > I'll try to assess the impact for each of these, let me know if these > match your understanding. > > 1. Bundles using OSGi R8 specific features won't work in the Sling > Starter 12 version. > 2. Anyone using the 'API docs' version of the Starter will find the > docs for the old 11 version instead. > 3. I am not sure what the impact is here. I traced the code > JcrSystemUserValidator → ServiceUserMapperImpl → > AbstractSlingRepository2 but I don't understand what happens next. > Technically loginService should fail, but I do not see evidence of that > in the logs. > 4. Still up for discussion. I saw that it fails for Stefan on Windows, > but I could not reproduce it in a VM. Sergiu also mentioned in the > issue that he saw it happen sporadically. > > I personally don't see 1 and 2 as blockers. For 3 and 4 I would like to > understand the impact before cancelling the release. > > Thanks, > Robert > >> >> Konrad >> On 2. Mar 2022, at 18:28, Konrad Windszus wrote: >>> >>> Hi, >>> I cannot reproduce the issue from Stefan on my Mac. >>> But I would like to fix the wrong API documentation >>> (https://issues.apache.org/jira/browse/SLING-11172 < >>> https://issues.apache.org/jira/browse/SLING-11172>) and also the >>> WARN around the missing/wrong service user for Sling Auth Core >>> (https://issues.apache.org/jira/browse/SLING-11171 < >>> https://issues.apache.org/jira/browse/SLING-11171>). >>> For the former I already created a PR for the latter it would be >>> good if someone more familiar with Auth Core could have a look. >>> I would rather tend to wait for those issues (and potentially >>> Stefan one’s if we figure out the root cause) until we release >>> Sling Starter 12. >>> >>> Konrad >>> >>> >>> On 25. Feb 2022, at 17:37, Robert Munteanu wrote: Hi, We solved 80 issues in these releases (not accounting for duplicates): https://issues.apache.org/jira/browse/SLING/fixforversion/12344080 (57) https://issues.apache.org/jira/browse/SLING/fixforversion/12348435 (3) https://issues.apache.org/jira/browse/SLING/fixforversion/12345675 (7) https://issues.apache.org/jira/browse/SLING/fixforversion/12348357 (6) https://issues.apache.org/jira/browse/SLING/fixforversion/12348291 (7) There is no Jira version for the test-fragment bundle, but I've included it in the release since we keep the same version for all the testing projects. Staging repository: https://repository.apache.org/content/repositories/orgapachesling-2604 You can use this UNIX script to download the release and verify the signatures: https://gitbox.apache.org/repos/asf?p=sling-tooling-release.git;a=blob;f=check_staged_release.sh;hb=HEAD Usage: sh check_staged_release.sh 2604 /tmp/sling-staging Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This majority vote is open for at least 72 hours. Thanks, Robert >>> >> >
Re: [VOTE] Release Apache Sling Repoinit Parser 1.6.14, Apache Sling Repoinit JCR 1.1.38
On Thu, 2022-03-03 at 10:56 +0100, ang...@apache.org wrote: > Please vote to approve this release: +1 Robert signature.asc Description: This is a digitally signed message part
Re: [VOTE] Release Apache Sling Starter 12, Apache Sling Project Archetype 1.0.6 and associated testing modules,
Hi Konrad, On Wed, 2022-03-02 at 18:47 +0100, Konrad Windszus wrote: > And I found another blocker: > https://issues.apache.org/jira/browse/SLING-11173 < > https://issues.apache.org/jira/browse/SLING-11173> which deserves > fixing prior to release. > Therefore voting -1. Thanks for looking into this and for raising issues. I'd like to make sure I understand how severe these bugs are. Not necessarilly because of the time needed to redo the release, but because I'd like to keep the '12' version for the next Starter release and I'm not sure that this is feasible. Current we have 1. SLING-11173 - Wrong version of org.osgi.framework exported (OSGi R7 instead of OSGi R8) 2. SLING-11172 - Make API documentation link point to the (not yet published) Sling 12 javadoc 3. 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." 4. SLING-11168 - Sling Starter 12: Unable to launch Composum I'll try to assess the impact for each of these, let me know if these match your understanding. 1. Bundles using OSGi R8 specific features won't work in the Sling Starter 12 version. 2. Anyone using the 'API docs' version of the Starter will find the docs for the old 11 version instead. 3. I am not sure what the impact is here. I traced the code JcrSystemUserValidator → ServiceUserMapperImpl → AbstractSlingRepository2 but I don't understand what happens next. Technically loginService should fail, but I do not see evidence of that in the logs. 4. Still up for discussion. I saw that it fails for Stefan on Windows, but I could not reproduce it in a VM. Sergiu also mentioned in the issue that he saw it happen sporadically. I personally don't see 1 and 2 as blockers. For 3 and 4 I would like to understand the impact before cancelling the release. Thanks, Robert > > Konrad > > > On 2. Mar 2022, at 18:28, Konrad Windszus wrote: > > > > Hi, > > I cannot reproduce the issue from Stefan on my Mac. > > But I would like to fix the wrong API documentation > > (https://issues.apache.org/jira/browse/SLING-11172 < > > https://issues.apache.org/jira/browse/SLING-11172>) and also the > > WARN around the missing/wrong service user for Sling Auth Core > > (https://issues.apache.org/jira/browse/SLING-11171 < > > https://issues.apache.org/jira/browse/SLING-11171>). > > For the former I already created a PR for the latter it would be > > good if someone more familiar with Auth Core could have a look. > > I would rather tend to wait for those issues (and potentially > > Stefan one’s if we figure out the root cause) until we release > > Sling Starter 12. > > > > Konrad > > > > > > > > > On 25. Feb 2022, at 17:37, Robert Munteanu > > > wrote: > > > > > > Hi, > > > > > > We solved 80 issues in these releases (not accounting for > > > duplicates): > > > > > > > > > https://issues.apache.org/jira/browse/SLING/fixforversion/12344080 > > > (57) > > > https://issues.apache.org/jira/browse/SLING/fixforversion/12348435 > > > (3) > > > https://issues.apache.org/jira/browse/SLING/fixforversion/12345675 > > > (7) > > > https://issues.apache.org/jira/browse/SLING/fixforversion/12348357 > > > (6) > > > https://issues.apache.org/jira/browse/SLING/fixforversion/12348291 > > > (7) > > > > > > There is no Jira version for the test-fragment bundle, but I've > > > included it in the release since we keep the same version for all > > > the > > > testing projects. > > > > > > Staging repository: > > > https://repository.apache.org/content/repositories/orgapachesling-2604 > > > > > > You can use this UNIX script to download the release and verify > > > the > > > signatures: > > > > > > https://gitbox.apache.org/repos/asf?p=sling-tooling-release.git;a=blob;f=check_staged_release.sh;hb=HEAD > > > > > > Usage: > > > sh check_staged_release.sh 2604 /tmp/sling-staging > > > > > > Please vote to approve this release: > > > > > > [ ] +1 Approve the release > > > [ ] 0 Don't care > > > [ ] -1 Don't release, because ... > > > > > > This majority vote is open for at least 72 hours. > > > > > > Thanks, > > > Robert > > >
[jira] [Comment Edited] (SLING-11173) Wrong version of org.osgi.framework exported (OSGi R7 instead of OSGi R8)
[ https://issues.apache.org/jira/browse/SLING-11173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500634#comment-17500634 ] Robert Munteanu edited comment on SLING-11173 at 3/3/22, 10:18 AM: --- I touched this last for the feature reorg, but I think [~karlpauls]] was the one that initially added them. I can't really make sense of what is going on there :-) was (Author: rombert): I touched this last for the feature reorg, but I think [~pauls] was the one that initially added them. I can't really make sense of what is going on there :-) > Wrong version of org.osgi.framework exported (OSGi R7 instead of OSGi R8) > - > > Key: SLING-11173 > URL: https://issues.apache.org/jira/browse/SLING-11173 > Project: Sling > Issue Type: Bug > Components: Starter >Reporter: Konrad Windszus >Priority: Blocker > Fix For: Starter 12 > > > Although Felix was updated in SLING-10409 to Felix 7 (OSGi R8 compliant) the > package exports are still only for OSGi R7 in > https://github.com/apache/sling-org-apache-sling-starter/blob/150e60df97a6d8911e938b76903f64d54f1201df/src/main/features/boot.json#L151. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Comment Edited] (SLING-11173) Wrong version of org.osgi.framework exported (OSGi R7 instead of OSGi R8)
[ https://issues.apache.org/jira/browse/SLING-11173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500634#comment-17500634 ] Robert Munteanu edited comment on SLING-11173 at 3/3/22, 10:18 AM: --- I touched this last for the feature reorg, but I think [~karlpauls] was the one that initially added them. I can't really make sense of what is going on there :-) was (Author: rombert): I touched this last for the feature reorg, but I think [~karlpauls]] was the one that initially added them. I can't really make sense of what is going on there :-) > Wrong version of org.osgi.framework exported (OSGi R7 instead of OSGi R8) > - > > Key: SLING-11173 > URL: https://issues.apache.org/jira/browse/SLING-11173 > Project: Sling > Issue Type: Bug > Components: Starter >Reporter: Konrad Windszus >Priority: Blocker > Fix For: Starter 12 > > > Although Felix was updated in SLING-10409 to Felix 7 (OSGi R8 compliant) the > package exports are still only for OSGi R7 in > https://github.com/apache/sling-org-apache-sling-starter/blob/150e60df97a6d8911e938b76903f64d54f1201df/src/main/features/boot.json#L151. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (SLING-11173) Wrong version of org.osgi.framework exported (OSGi R7 instead of OSGi R8)
[ https://issues.apache.org/jira/browse/SLING-11173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500634#comment-17500634 ] Robert Munteanu commented on SLING-11173: - I touched this last for the feature reorg, but I think [~pauls] was the one that initially added them. I can't really make sense of what is going on there :-) > 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: Robert Munteanu >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] [Assigned] (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 reassigned SLING-11173: --- Assignee: (was: Robert Munteanu) > Wrong version of org.osgi.framework exported (OSGi R7 instead of OSGi R8) > - > > Key: SLING-11173 > URL: https://issues.apache.org/jira/browse/SLING-11173 > Project: Sling > Issue Type: Bug > Components: Starter >Reporter: Konrad Windszus >Priority: Blocker > Fix For: Starter 12 > > > Although Felix was updated in SLING-10409 to Felix 7 (OSGi R8 compliant) the > package exports are still only for OSGi R7 in > https://github.com/apache/sling-org-apache-sling-starter/blob/150e60df97a6d8911e938b76903f64d54f1201df/src/main/features/boot.json#L151. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (SLING-11172) Make API documentation link point to the (not yet published) Sling 12 javadoc
[ https://issues.apache.org/jira/browse/SLING-11172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17500631#comment-17500631 ] Robert Munteanu commented on SLING-11172: - I think this is the right thing to do, for the current release. I wonder though if we should make the version that the links point to configurable via a server-side script, so that we don't have to bump the Starter Content package each time we do a Starter release. For SNAPSHOT versions of the Starter we can go back to the previous release. > Make API documentation link point to the (not yet published) Sling 12 javadoc > - > > Key: SLING-11172 > URL: https://issues.apache.org/jira/browse/SLING-11172 > Project: Sling > Issue Type: Bug > Components: Starter >Affects Versions: Starter Content 1.0.10 >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > Fix For: Starter Content 1.0.12 > > Time Spent: 20m > Remaining Estimate: 0h > > The new content used in Sling Starter 12 should point to Sling 12 javadocs > instead of Sling 11 ones. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[VOTE] Release Apache Sling Repoinit Parser 1.6.14, Apache Sling Repoinit JCR 1.1.38
Hi, We solved the following issues in this release: https://issues.apache.org/jira/projects/SLING/versions/12351292 https://issues.apache.org/jira/projects/SLING/versions/12350313 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-2605 You can use this UNIX script to download the release and verify the signatures: https://gitbox.apache.org/repos/asf?p=sling-tooling-release.git;a=blob;f=check_staged_release.sh;hb=HEAD Usage: sh check_staged_release.sh 2601 /tmp/sling-staging Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This majority vote is open for at least 72 hours. Kind regards Angela
[jira] [Updated] (SLING-9524) Add Support for Bundle URL References
[
https://issues.apache.org/jira/browse/SLING-9524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Angela Schreiber updated SLING-9524:
Fix Version/s: (was: Repoinit JCR 1.1.38)
> Add Support for Bundle URL References
> -
>
> Key: SLING-9524
> URL: https://issues.apache.org/jira/browse/SLING-9524
> Project: Sling
> Issue Type: New Feature
> Components: Repoinit
>Affects Versions: Repoinit JCR 1.1.26
>Reporter: Dan Klco
>Assignee: Dan Klco
>Priority: Major
>
> JCR RepoInit supports references to URLs using the
> {{org.apache.sling.jcr.repoinit.impl.RepositoryInitializer}} service _AND_
> the OSGi framework supports resolving resources to bundles via the bundle://
> URL protocol:
> https://docs.osgi.org/javadoc/r4v43/core/org/osgi/framework/Bundle.html#getResource(java.lang.String)
> However, (in Apache Felix at least) the OSGi container generates the Bundle
> URLs based on a UUID rather than a stable identifier (such as the Bundle's
> Symbolic Name):
> https://github.com/apache/felix-dev/blob/master/framework/src/main/java/org/apache/felix/framework/URLHandlersBundleStreamHandler.java
> While it is possible to resolve these UUID's at runtime, this requires an
> additional OSGi Component to resolve the Bundle URL and then create a
> configuration for the RepositoryInitializer.
> Ideally, we would be able to use a URL to reference a bundle resource using
> the Symbolic Name, which would be resolved at runtime to the bundle UUID.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (SLING-9572) JCR RepoInit Web Console
[ https://issues.apache.org/jira/browse/SLING-9572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Angela Schreiber updated SLING-9572: Fix Version/s: (was: Repoinit JCR 1.1.38) > JCR RepoInit Web Console > > > Key: SLING-9572 > URL: https://issues.apache.org/jira/browse/SLING-9572 > Project: Sling > Issue Type: New Feature >Affects Versions: Repoinit JCR 1.1.26 >Reporter: Dan Klco >Assignee: Dan Klco >Priority: Minor > > It would be nice to have an OSGi Console for testing the JCR RepoInit > configuration scripts without having to create OSGi Configurations. > The Web Console should have the following capabilities: > - Parse the RepoInit commands > - Display the parsed commands > - Optionally execute the commands -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (SLING-10740) Repoinit create path statement fails for node types with a mandatory property
[ https://issues.apache.org/jira/browse/SLING-10740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Angela Schreiber updated SLING-10740: - Fix Version/s: (was: Repoinit JCR 1.1.38) > Repoinit create path statement fails for node types with a mandatory property > - > > Key: SLING-10740 > URL: https://issues.apache.org/jira/browse/SLING-10740 > Project: Sling > Issue Type: Bug > Components: Repoinit >Reporter: Eric Norman >Assignee: Eric Norman >Priority: Major > > The processing of the "create path" statement calls save() at the end which > will cause a constraint violation if the nodetype of the created path > contains any properties that are declared as mandatory (and not autocreated). > No processing of "set properties" statements happens before the save() call > in AclVisitor#visitCreatePath so it does not seem to be possible to define > any mandatory properties using the current repoinit grammar. > I could see this solved in a couple ways: > # The AclVisitor#visitCreatePath could possibly pre-process any "set > properties" statements that are applicable to the created path before calling > save and then skip those same items when NodePropertiesVisitor visits the > same. > # Or, the "create path" grammar could be extended to allow defining > properties to be set at the same time as the create (with a syntax that is > similar to the "set properties" statement?) > # Or, perhaps calling save in AclVisitor#visitCreatePath is not necessary? > I'm not sure of the historical reasons why save() is done there. > # Or, maybe something else I haven't thought of > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (SLING-10281) Revert SLING-9449: set principal ACL should throw an Exception it it fails
[ https://issues.apache.org/jira/browse/SLING-10281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Angela Schreiber updated SLING-10281: - Fix Version/s: (was: Repoinit JCR 1.1.38) > Revert SLING-9449: set principal ACL should throw an Exception it it fails > -- > > Key: SLING-10281 > URL: https://issues.apache.org/jira/browse/SLING-10281 > Project: Sling > Issue Type: Bug > Components: Repoinit >Affects Versions: Repoinit JCR 1.1.34 >Reporter: Konrad Windszus >Assignee: Bertrand Delacretaz >Priority: Major > Time Spent: 7h > Remaining Estimate: 0h > > As highlighted in the last comment of SLING-9449, repoinit should use > exceptions when some statements cannot be applied (as that leads to an > undesired repository state). In the worst case it could lead to privilege > escalation -- This message was sent by Atlassian Jira (v8.20.1#820001)
[Jenkins] Sling » Modules » sling-org-apache-sling-launchpad-testing » master #948 is FIXED
Please see https://ci-builds.apache.org/job/Sling/job/modules/job/sling-org-apache-sling-launchpad-testing/job/master/948/ for details. No further emails will be sent until the status of the build is changed.
[jira] [Updated] (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
]
Konrad Windszus updated SLING-11171:
Fix Version/s: Starter 12
> 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
>Priority: Major
> Fix For: Starter 12
>
>
> 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)
