[jira] [Resolved] (SLING-12267) Log all paths in case of errors
[ https://issues.apache.org/jira/browse/SLING-12267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider resolved SLING-12267. - Resolution: Fixed > Log all paths in case of errors > --- > > Key: SLING-12267 > URL: https://issues.apache.org/jira/browse/SLING-12267 > Project: Sling > Issue Type: Improvement > Components: Content Distribution >Affects Versions: Content Distribution Journal Core 0.2.0 >Reporter: Christian Schneider >Assignee: Christian Schneider >Priority: Major > Fix For: Content Distribution Journal Core 0.3.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (SLING-12293) Remove jcr binarystore
[ https://issues.apache.org/jira/browse/SLING-12293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider resolved SLING-12293. - Resolution: Fixed > Remove jcr binarystore > -- > > Key: SLING-12293 > URL: https://issues.apache.org/jira/browse/SLING-12293 > Project: Sling > Issue Type: Improvement >Reporter: Christian Schneider >Assignee: Christian Schneider >Priority: Major > Fix For: Content Distribution Journal Core 0.3.0 > > > Jcr binary store is not used for a long time. We can safely remove it. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (SLING-12294) Remove buffer on subscriber side
Christian Schneider created SLING-12294: --- Summary: Remove buffer on subscriber side Key: SLING-12294 URL: https://issues.apache.org/jira/browse/SLING-12294 Project: Sling Issue Type: Improvement Reporter: Christian Schneider Assignee: Christian Schneider Fix For: Content Distribution Journal Core 0.3.0 As we now do batching on messaging side I think, there is no need for the items buffer anymore. By removing it we can remove quite some complexity. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SLING-12281) Content Parser: Update to Parent 60, Java 11 Minimum Version
[ https://issues.apache.org/jira/browse/SLING-12281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert closed SLING-12281. -- > Content Parser: Update to Parent 60, Java 11 Minimum Version > > > Key: SLING-12281 > URL: https://issues.apache.org/jira/browse/SLING-12281 > Project: Sling > Issue Type: Improvement > Components: Content Parser >Reporter: Stefan Seifert >Assignee: Stefan Seifert >Priority: Major > Fix For: Content Parser API 2.1.0, Content Parser Test Utilities > 2.1.0, Content Parser JSON 2.1.0, Content Parser XML 2.1.0, Content Parser > XML JCR 2.1.0 > > > update to parent 60, regarding [https://cwiki.apache.org/confluence/x/SI75E] > this drops java 8 support, and instead supports java 11, 17, 21 - build is > done with java 17 > minimum java requirement for runtime is java 11 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SLING-12102) Content Parser: Update to Parent 52
[ https://issues.apache.org/jira/browse/SLING-12102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert closed SLING-12102. -- > Content Parser: Update to Parent 52 > --- > > Key: SLING-12102 > URL: https://issues.apache.org/jira/browse/SLING-12102 > Project: Sling > Issue Type: Improvement > Components: Content Parser >Affects Versions: Content Parser API 2.0.0, Content Parser JSON 2.0.0, > Content Parser XML 2.0.0, Content Parser XML JCR 2.0.0, Content Parser Test > Utilities 2.0.0 >Reporter: Stefan Seifert >Assignee: Stefan Seifert >Priority: Major > Fix For: Content Parser API 2.1.0, Content Parser Test Utilities > 2.1.0, Content Parser JSON 2.1.0, Content Parser XML 2.1.0, Content Parser > XML JCR 2.1.0 > > > update to latest parent, fix build with java 17 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SLING-12282) Content Parser: Update Dependencies to 2023
[ https://issues.apache.org/jira/browse/SLING-12282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert closed SLING-12282. -- > Content Parser: Update Dependencies to 2023 > --- > > Key: SLING-12282 > URL: https://issues.apache.org/jira/browse/SLING-12282 > Project: Sling > Issue Type: Improvement > Components: Content Parser >Reporter: Stefan Seifert >Assignee: Stefan Seifert >Priority: Major > Fix For: Content Parser Test Utilities 2.1.0, Content Parser JSON > 2.1.0, Content Parser XML 2.1.0, Content Parser XML JCR 2.1.0 > > > in line with and using the same concept of SLING-12208 update 3rdparty > dependencies to a newer version for content parser modules -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SLING-12280) Migrate org.apache.sling.contentparser.json to jakarta.json
[ https://issues.apache.org/jira/browse/SLING-12280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert closed SLING-12280. -- > Migrate org.apache.sling.contentparser.json to jakarta.json > --- > > Key: SLING-12280 > URL: https://issues.apache.org/jira/browse/SLING-12280 > Project: Sling > Issue Type: Sub-task > Components: Content Parser >Reporter: Stefan Seifert >Assignee: Stefan Seifert >Priority: Major > Fix For: Content Parser JSON 2.1.0 > > > to support johnzon 2.0 in unit tests with sling-mocks, we need to switch to > jakarta.json for the JSON content parser as well. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[RESULT] [VOTE] Release Apache Sling Content Parser JSON 2.1.0
Hi, The vote has passed with the following result : +1 (binding): Stefan Seifert, Robert Munteanu, Konrad Windszus I will copy this release to the Sling dist directory and promote the artifacts to the central Maven repository. stefan
Re: [VOTE] Release Apache Sling Content Parser JSON 2.1.0
+1 Konrad > On 9. Apr 2024, at 12:15, Stefan Seifert > wrote: > > Hi, > > We solved 4 issues in this release: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12353724=Text=12310710 > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-2844/ > > You can use this UNIX script to download the release and verify the > signatures: > https://raw.githubusercontent.com/apache/sling-tooling-release/master/check_staged_release.sh > > Usage: > sh check_staged_release.sh 2844 /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. > > stefan
[jira] [Resolved] (SLING-12276) Update to java-html-sanitizer 20240325.1
[ https://issues.apache.org/jira/browse/SLING-12276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-12276. - Resolution: Fixed > Update to java-html-sanitizer 20240325.1 > > > Key: SLING-12276 > URL: https://issues.apache.org/jira/browse/SLING-12276 > Project: Sling > Issue Type: Improvement > Components: XSS Protection API >Reporter: Robert Munteanu >Assignee: Robert Munteanu >Priority: Major > Fix For: XSS Protection API 2.4.2 > > > A new Java HTML Sanitizer version is out, notably removing the dependency on > Guava ( > https://github.com/OWASP/java-html-sanitizer/releases/tag/release-20240325.1 > ). > This will allow us to remove: > - the embedding of Guava classes, cutting down on bundle size > - the shading of the Guava classes, reducing the complexity of the pom -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] SLING-12276 - Update to java-html-sanitizer 20240325.1 [sling-org-apache-sling-xss]
rombert merged PR #42: URL: https://github.com/apache/sling-org-apache-sling-xss/pull/42 -- 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 Commons JSON 2.0.26
+1 stefan
RE: [VOTE] Release Apache Sling Content Parser JSON 2.1.0
we need one more binding vote! steafn > -Original Message- > From: Stefan Seifert > Sent: Tuesday, April 9, 2024 12:15 PM > To: dev@sling.apache.org > Subject: [VOTE] Release Apache Sling Content Parser JSON 2.1.0 > > Hi, > > We solved 4 issues in this release: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12353724 > yleName=Text=12310710 > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-2844/ > > You can use this UNIX script to download the release and verify the > signatures: > https://raw.githubusercontent.com/apache/sling-tooling- > release/master/check_staged_release.sh > > Usage: > sh check_staged_release.sh 2844 /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. > > stefan
Re: [PR] SLING-12290 - Update tenant module to use parent pom 52 [sling-org-apache-sling-tenant]
rombert commented on PR #5: URL: https://github.com/apache/sling-org-apache-sling-tenant/pull/5#issuecomment-2051240585 You're right, I had it in my had that we require Java 17 for running, but it's for building only. Need to do more parent pom updates to help me remember :-) -- 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
[VOTE] Release Apache Sling Commons JSON 2.0.26
Hi, We solved 1 issue in this release: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310710=12354548=Text Staging repository: https://repository.apache.org/content/repositories/orgapachesling-2846/ You can use this UNIX script to download the release and verify the signatures: https://raw.githubusercontent.com/apache/sling-tooling-release/master/check_staged_release.sh Usage: sh check_staged_release.sh 2846 /tmp/sling-staging Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ... This majority vote is open for at least 72 hours. Regards, Robert Munteanu
[jira] [Updated] (SLING-12291) Broken backwards compatibility for duplicated keys
[ https://issues.apache.org/jira/browse/SLING-12291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-12291: Fix Version/s: Commons JSON 2.0.26 (was: Commons JSON 2.0.24) > Broken backwards compatibility for duplicated keys > -- > > Key: SLING-12291 > URL: https://issues.apache.org/jira/browse/SLING-12291 > Project: Sling > Issue Type: Bug >Affects Versions: Commons JSON 2.0.24 >Reporter: Remo Liechti >Assignee: Remo Liechti >Priority: Major > Fix For: Commons JSON 2.0.26 > > > The fix of CVE-2022-47937 introduced an invalid backwards compatibility for > duplicated keys in a json. > New behaviour: throws an exception on duplicated keys > Old behaviour: ignores the fact and is able to process json with duplicated > keys. > To no break existing users of the library, reestablish the old behaviour. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (SLING-12291) Broken backwards compatibility for duplicated keys
[ https://issues.apache.org/jira/browse/SLING-12291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-12291. - Resolution: Fixed PR applied, thanks [~rliechti]! > Broken backwards compatibility for duplicated keys > -- > > Key: SLING-12291 > URL: https://issues.apache.org/jira/browse/SLING-12291 > Project: Sling > Issue Type: Bug >Affects Versions: Commons JSON 2.0.24 >Reporter: Remo Liechti >Assignee: Remo Liechti >Priority: Major > Fix For: Commons JSON 2.0.24 > > > The fix of CVE-2022-47937 introduced an invalid backwards compatibility for > duplicated keys in a json. > New behaviour: throws an exception on duplicated keys > Old behaviour: ignores the fact and is able to process json with duplicated > keys. > To no break existing users of the library, reestablish the old behaviour. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (SLING-12287) sling-mock-oak: Use latest Oak Version and add ITs to ensure compatiblity with 1.22.x
[ https://issues.apache.org/jira/browse/SLING-12287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836439#comment-17836439 ] Stefan Seifert commented on SLING-12287: looking deeper into this, i think it's not easy possible to have a single JAR/POM supporting both oak 1.22 and latest oak version at the same time. there is too much change between them, regarding supported jdks and the change guava is embedded. i currently plan to do a branching of sling-mock-oak - one maintenance branch for 1.22.x and one for latest versions - this is in-line how oak itself it is doing. i started two draft PRs and will continue test the produced JARs in different project environments if this is working. maybe we can eliminate more of the shading/embedding in the latest sling-mock-oak version which would be a good thing. * sling-mock-oak 4.x with Oak 1.60: https://github.com/apache/sling-org-apache-sling-testing-sling-mock-oak/pull/13 * sling-mock-oak 3.2.x with Oak 1.22: https://github.com/apache/sling-org-apache-sling-testing-sling-mock-oak/pull/14 > sling-mock-oak: Use latest Oak Version and add ITs to ensure compatiblity > with 1.22.x > - > > Key: SLING-12287 > URL: https://issues.apache.org/jira/browse/SLING-12287 > Project: Sling > Issue Type: Improvement > Components: Testing >Reporter: Stefan Seifert >Assignee: Stefan Seifert >Priority: Major > Fix For: Testing Sling Mock Oak 3.2.0-1.44.0 > > > following the discussion with [~reschke] in SLING-12266 we should move away > from oak 1.44 which is quite outdated. however, we need to ensure to keep > compatibility with the old 1.22.x version range to support all sorts of > projects using the mocks. > a solution might be to switch to a recent version of oak in the POM, and > create dedicated ITs to test against this and older 1.22.x versions to ensure > compatibility. > the benefit is, that all projects that are "just using" sling-mock-oak > without thinking about the dependency management (e.g. not using something > like [https://wcm.io/tooling/maven/aem-dependencies.html)] will get the > latest version which is better supported. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] SLING-12287 Switch to Oak 1.60 [sling-org-apache-sling-testing-sling-mock-oak]
sonarcloud[bot] commented on PR #14: URL: https://github.com/apache/sling-org-apache-sling-testing-sling-mock-oak/pull/14#issuecomment-2051164075 ## [](https://sonarcloud.io/dashboard?id=apache_sling-org-apache-sling-testing-sling-mock-oak=14) **Quality Gate passed** Issues  [0 New issues](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-sling-mock-oak=14=false=true)  [0 Accepted issues](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-testing-sling-mock-oak=14=new_accepted_issues=list) Measures  [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-testing-sling-mock-oak=14=false=true)  No data about Coverage  [0.0% Duplication on New Code](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-testing-sling-mock-oak=14=new_duplicated_lines_density=list) [See analysis details on SonarCloud](https://sonarcloud.io/dashboard?id=apache_sling-org-apache-sling-testing-sling-mock-oak=14) -- 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: [PR] SLING-12287 Switch to Oak 1.22 [sling-org-apache-sling-testing-sling-mock-oak]
sonarcloud[bot] commented on PR #13: URL: https://github.com/apache/sling-org-apache-sling-testing-sling-mock-oak/pull/13#issuecomment-2051120443 ## [](https://sonarcloud.io/dashboard?id=apache_sling-org-apache-sling-testing-sling-mock-oak=13) **Quality Gate passed** Issues  [0 New issues](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-sling-mock-oak=13=false=true)  [0 Accepted issues](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-testing-sling-mock-oak=13=new_accepted_issues=list) Measures  [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-testing-sling-mock-oak=13=false=true)  No data about Coverage  [0.0% Duplication on New Code](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-testing-sling-mock-oak=13=new_duplicated_lines_density=list) [See analysis details on SonarCloud](https://sonarcloud.io/dashboard?id=apache_sling-org-apache-sling-testing-sling-mock-oak=13) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] SLING-12287 Switch to Oak 1.22 [sling-org-apache-sling-testing-sling-mock-oak]
stefanseifert opened a new pull request, #13: URL: https://github.com/apache/sling-org-apache-sling-testing-sling-mock-oak/pull/13 switch back to Oak 1.22, which is the officially support "legacy" version of oak. switch back to parent 52 and limit build to java 11, as build with the old oak version is not working with Java 17+ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (SLING-12293) Remove jcr binarystore
Christian Schneider created SLING-12293: --- Summary: Remove jcr binarystore Key: SLING-12293 URL: https://issues.apache.org/jira/browse/SLING-12293 Project: Sling Issue Type: Improvement Reporter: Christian Schneider Assignee: Christian Schneider Fix For: Content Distribution Journal Core 0.3.0 Jcr binary store is not used for a long time. We can safely remove it. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (SLING-12292) Improve metric support
Christian Schneider created SLING-12292: --- Summary: Improve metric support Key: SLING-12292 URL: https://issues.apache.org/jira/browse/SLING-12292 Project: Sling Issue Type: Improvement Reporter: Christian Schneider Assignee: Christian Schneider Fix For: Content Distribution Journal Core 0.3.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
