Re: [PR] Bump ch.qos.logback:logback-classic from 1.2.3 to 1.2.13 [sling-org-apache-sling-models-jacksonexporter]
stefanseifert merged PR #9: URL: https://github.com/apache/sling-org-apache-sling-models-jacksonexporter/pull/9 -- 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] Bump ch.qos.logback:logback-classic from 1.2.3 to 1.2.13 [sling-org-apache-sling-testing-jcr-mock]
stefanseifert merged PR #31: URL: https://github.com/apache/sling-org-apache-sling-testing-jcr-mock/pull/31 -- 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] Bump ch.qos.logback:logback-classic from 1.2.3 to 1.2.13 [sling-org-apache-sling-models-jacksonexporter]
sonarcloud[bot] commented on PR #9: URL: https://github.com/apache/sling-org-apache-sling-models-jacksonexporter/pull/9#issuecomment-1842073635 Kudos, SonarCloud Quality Gate passed! [](https://sonarcloud.io/dashboard?id=apache_sling-org-apache-sling-models-jacksonexporter=9) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-models-jacksonexporter=9=false=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-models-jacksonexporter=9=false=BUG) [0 Bugs](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-models-jacksonexporter=9=false=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-models-jacksonexporter=9=false=VULNERABILITY) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-models-jacksonexporter=9=false=VULNERABILITY) [0 Vulnerabilities](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-models-jacksonexporter=9=false=VULNERABILITY) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-models-jacksonexporter=9=false=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-models-jacksonexporter=9=false=SECURITY_HOTSPOT) [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-models-jacksonexporter=9=false=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-models-jacksonexporter=9=false=CODE_SMELL) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-models-jacksonexporter=9=false=CODE_SMELL) [0 Code Smells](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-models-jacksonexporter=9=false=CODE_SMELL) [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-models-jacksonexporter=9=coverage=list) No Coverage information [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-models-jacksonexporter=9=new_duplicated_lines_density=list) [0.0% Duplication](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-models-jacksonexporter=9=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
Re: [PR] Bump ch.qos.logback:logback-classic from 1.2.3 to 1.2.13 [sling-org-apache-sling-testing-jcr-mock]
sonarcloud[bot] commented on PR #31: URL: https://github.com/apache/sling-org-apache-sling-testing-jcr-mock/pull/31#issuecomment-1842071203 Kudos, SonarCloud Quality Gate passed! [](https://sonarcloud.io/dashboard?id=apache_sling-org-apache-sling-testing-jcr-mock=31) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-jcr-mock=31=false=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-jcr-mock=31=false=BUG) [0 Bugs](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-jcr-mock=31=false=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-jcr-mock=31=false=VULNERABILITY) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-jcr-mock=31=false=VULNERABILITY) [0 Vulnerabilities](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-jcr-mock=31=false=VULNERABILITY) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-testing-jcr-mock=31=false=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-testing-jcr-mock=31=false=SECURITY_HOTSPOT) [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-testing-jcr-mock=31=false=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-jcr-mock=31=false=CODE_SMELL) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-jcr-mock=31=false=CODE_SMELL) [0 Code Smells](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-jcr-mock=31=false=CODE_SMELL) [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-testing-jcr-mock=31=coverage=list) No Coverage information [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-testing-jcr-mock=31=new_duplicated_lines_density=list) [0.0% Duplication](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-testing-jcr-mock=31=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
Re: [PR] Bump ch.qos.logback:logback-classic from 1.2.3 to 1.2.13 [sling-org-apache-sling-sitemap]
sonarcloud[bot] commented on PR #15: URL: https://github.com/apache/sling-org-apache-sling-sitemap/pull/15#issuecomment-1842069443 Kudos, SonarCloud Quality Gate passed! [](https://sonarcloud.io/dashboard?id=apache_sling-org-apache-sling-sitemap=15) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-sitemap=15=false=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-sitemap=15=false=BUG) [0 Bugs](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-sitemap=15=false=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-sitemap=15=false=VULNERABILITY) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-sitemap=15=false=VULNERABILITY) [0 Vulnerabilities](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-sitemap=15=false=VULNERABILITY) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-sitemap=15=false=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-sitemap=15=false=SECURITY_HOTSPOT) [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-sitemap=15=false=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-sitemap=15=false=CODE_SMELL) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-sitemap=15=false=CODE_SMELL) [0 Code Smells](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-sitemap=15=false=CODE_SMELL) [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-sitemap=15=coverage=list) No Coverage information [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-sitemap=15=new_duplicated_lines_density=list) [0.0% Duplication](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-sitemap=15=new_duplicated_lines_density=list) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] Bump ch.qos.logback:logback-classic from 1.1.2 to 1.2.13 [sling-org-apache-sling-launchpad-integration-tests]
sonarcloud[bot] commented on PR #20: URL: https://github.com/apache/sling-org-apache-sling-launchpad-integration-tests/pull/20#issuecomment-1842066032 Kudos, SonarCloud Quality Gate passed! [](https://sonarcloud.io/dashboard?id=apache_sling-org-apache-sling-launchpad-integration-tests=20) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-launchpad-integration-tests=20=false=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-launchpad-integration-tests=20=false=BUG) [0 Bugs](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-launchpad-integration-tests=20=false=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-launchpad-integration-tests=20=false=VULNERABILITY) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-launchpad-integration-tests=20=false=VULNERABILITY) [0 Vulnerabilities](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-launchpad-integration-tests=20=false=VULNERABILITY) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-launchpad-integration-tests=20=false=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-launchpad-integration-tests=20=false=SECURITY_HOTSPOT) [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-launchpad-integration-tests=20=false=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-launchpad-integration-tests=20=false=CODE_SMELL) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-launchpad-integration-tests=20=false=CODE_SMELL) [0 Code Smells](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-launchpad-integration-tests=20=false=CODE_SMELL) [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-launchpad-integration-tests=20) No Coverage information [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-launchpad-integration-tests=20=new_duplicated_lines_density=list) [0.0% Duplication](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-launchpad-integration-tests=20=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
Re: [PR] Bump ch.qos.logback:logback-classic from 1.2.11 to 1.2.13 [sling-org-apache-sling-jcr-repoinit]
sonarcloud[bot] commented on PR #49: URL: https://github.com/apache/sling-org-apache-sling-jcr-repoinit/pull/49#issuecomment-1842004646 Kudos, SonarCloud Quality Gate passed! [](https://sonarcloud.io/dashboard?id=apache_sling-org-apache-sling-jcr-repoinit=49) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-repoinit=49=false=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-repoinit=49=false=BUG) [0 Bugs](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-repoinit=49=false=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-repoinit=49=false=VULNERABILITY) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-repoinit=49=false=VULNERABILITY) [0 Vulnerabilities](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-repoinit=49=false=VULNERABILITY) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-jcr-repoinit=49=false=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-jcr-repoinit=49=false=SECURITY_HOTSPOT) [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-jcr-repoinit=49=false=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-repoinit=49=false=CODE_SMELL) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-repoinit=49=false=CODE_SMELL) [0 Code Smells](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-jcr-repoinit=49=false=CODE_SMELL) [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-jcr-repoinit=49=coverage=list) No Coverage information [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-jcr-repoinit=49=new_duplicated_lines_density=list) [0.0% Duplication](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-jcr-repoinit=49=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
Re: [PR] Bump ch.qos.logback:logback-classic from 1.2.3 to 1.3.12 [sling-org-apache-sling-models-jacksonexporter]
dependabot[bot] commented on PR #8: URL: https://github.com/apache/sling-org-apache-sling-models-jacksonexporter/pull/8#issuecomment-1841739442 Superseded by #9. -- 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] Bump ch.qos.logback:logback-classic from 1.2.3 to 1.3.12 [sling-org-apache-sling-models-jacksonexporter]
dependabot[bot] closed pull request #8: Bump ch.qos.logback:logback-classic from 1.2.3 to 1.3.12 URL: https://github.com/apache/sling-org-apache-sling-models-jacksonexporter/pull/8 -- 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] Bump ch.qos.logback:logback-classic from 1.2.3 to 1.2.13 [sling-org-apache-sling-models-jacksonexporter]
dependabot[bot] opened a new pull request, #9: URL: https://github.com/apache/sling-org-apache-sling-models-jacksonexporter/pull/9 Bumps [ch.qos.logback:logback-classic](https://github.com/qos-ch/logback) from 1.2.3 to 1.2.13. Commits https://github.com/qos-ch/logback/commit/2648b9e7fbb47426c89b9c93b411c07484e8f277;>2648b9e prepare release 1.2.13 https://github.com/qos-ch/logback/commit/bb095154be011267b64e37a1d401546e7cc2b7c3;>bb09515 fix CVE-2023-6378 https://github.com/qos-ch/logback/commit/45732949bfb845df04cbe65292cf48aaa090cb1d;>4573294 start work on 1.2.13-SNAPSHOT https://github.com/qos-ch/logback/commit/a388193052c298ca87cc64192319df723288c6ab;>a388193 Merge branch 'branch_1.2.x' of github.com:qos-ch/logback into branch_1.2.x https://github.com/qos-ch/logback/commit/de44dc422bc3da1d7808283851324d960b492d4d;>de44dc4 prepare release 1.2.12 https://github.com/qos-ch/logback/commit/ca0cf172f680308938515b8a5d69348759ee947c;>ca0cf17 Merge pull request https://redirect.github.com/qos-ch/logback/issues/532;>#532 from joakime/fix-jetty-requestlog https://github.com/qos-ch/logback/commit/e31609b1980b9ba986344aae3cab7275fa2b4935;>e31609b removed unused files https://github.com/qos-ch/logback/commit/21e29efb284766f386781175b2ba18585b690154;>21e29ef Merge pull request https://redirect.github.com/qos-ch/logback/issues/567;>#567 from spliffone/LOGBACK-1633 https://github.com/qos-ch/logback/commit/e869000e1d5901e6aa6f46cc6575ee2137f15b69;>e869000 fix: published POM file contain the wrong scm URL https://github.com/qos-ch/logback/commit/009ea46cb81a015f2ca312bde6e823581b93b37a;>009ea46 version for next dev cycle Additional commits viewable in https://github.com/qos-ch/logback/compare/v_1.2.3...v_1.2.13;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/apache/sling-org-apache-sling-models-jacksonexporter/network/alerts). -- 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] Bump ch.qos.logback:logback-classic from 1.2.3 to 1.3.12 [sling-org-apache-sling-testing-jcr-mock]
dependabot[bot] closed pull request #30: Bump ch.qos.logback:logback-classic from 1.2.3 to 1.3.12 URL: https://github.com/apache/sling-org-apache-sling-testing-jcr-mock/pull/30 -- 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] Bump ch.qos.logback:logback-classic from 1.2.3 to 1.3.12 [sling-org-apache-sling-testing-jcr-mock]
dependabot[bot] commented on PR #30: URL: https://github.com/apache/sling-org-apache-sling-testing-jcr-mock/pull/30#issuecomment-1841738773 Superseded by #31. -- 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] Bump ch.qos.logback:logback-classic from 1.2.3 to 1.2.13 [sling-org-apache-sling-testing-jcr-mock]
dependabot[bot] opened a new pull request, #31: URL: https://github.com/apache/sling-org-apache-sling-testing-jcr-mock/pull/31 Bumps [ch.qos.logback:logback-classic](https://github.com/qos-ch/logback) from 1.2.3 to 1.2.13. Commits https://github.com/qos-ch/logback/commit/2648b9e7fbb47426c89b9c93b411c07484e8f277;>2648b9e prepare release 1.2.13 https://github.com/qos-ch/logback/commit/bb095154be011267b64e37a1d401546e7cc2b7c3;>bb09515 fix CVE-2023-6378 https://github.com/qos-ch/logback/commit/45732949bfb845df04cbe65292cf48aaa090cb1d;>4573294 start work on 1.2.13-SNAPSHOT https://github.com/qos-ch/logback/commit/a388193052c298ca87cc64192319df723288c6ab;>a388193 Merge branch 'branch_1.2.x' of github.com:qos-ch/logback into branch_1.2.x https://github.com/qos-ch/logback/commit/de44dc422bc3da1d7808283851324d960b492d4d;>de44dc4 prepare release 1.2.12 https://github.com/qos-ch/logback/commit/ca0cf172f680308938515b8a5d69348759ee947c;>ca0cf17 Merge pull request https://redirect.github.com/qos-ch/logback/issues/532;>#532 from joakime/fix-jetty-requestlog https://github.com/qos-ch/logback/commit/e31609b1980b9ba986344aae3cab7275fa2b4935;>e31609b removed unused files https://github.com/qos-ch/logback/commit/21e29efb284766f386781175b2ba18585b690154;>21e29ef Merge pull request https://redirect.github.com/qos-ch/logback/issues/567;>#567 from spliffone/LOGBACK-1633 https://github.com/qos-ch/logback/commit/e869000e1d5901e6aa6f46cc6575ee2137f15b69;>e869000 fix: published POM file contain the wrong scm URL https://github.com/qos-ch/logback/commit/009ea46cb81a015f2ca312bde6e823581b93b37a;>009ea46 version for next dev cycle Additional commits viewable in https://github.com/qos-ch/logback/compare/v_1.2.3...v_1.2.13;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/apache/sling-org-apache-sling-testing-jcr-mock/network/alerts). -- 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] Bump ch.qos.logback:logback-classic from 1.2.3 to 1.3.12 [sling-org-apache-sling-hc-support]
dependabot[bot] closed pull request #6: Bump ch.qos.logback:logback-classic from 1.2.3 to 1.3.12 URL: https://github.com/apache/sling-org-apache-sling-hc-support/pull/6 -- 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] Bump ch.qos.logback:logback-classic from 1.2.3 to 1.3.12 [sling-org-apache-sling-hc-support]
dependabot[bot] commented on PR #6: URL: https://github.com/apache/sling-org-apache-sling-hc-support/pull/6#issuecomment-1841735720 Superseded by #7. -- 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] Bump ch.qos.logback:logback-classic from 1.2.3 to 1.2.13 [sling-org-apache-sling-hc-support]
dependabot[bot] opened a new pull request, #7: URL: https://github.com/apache/sling-org-apache-sling-hc-support/pull/7 Bumps [ch.qos.logback:logback-classic](https://github.com/qos-ch/logback) from 1.2.3 to 1.2.13. Commits https://github.com/qos-ch/logback/commit/2648b9e7fbb47426c89b9c93b411c07484e8f277;>2648b9e prepare release 1.2.13 https://github.com/qos-ch/logback/commit/bb095154be011267b64e37a1d401546e7cc2b7c3;>bb09515 fix CVE-2023-6378 https://github.com/qos-ch/logback/commit/45732949bfb845df04cbe65292cf48aaa090cb1d;>4573294 start work on 1.2.13-SNAPSHOT https://github.com/qos-ch/logback/commit/a388193052c298ca87cc64192319df723288c6ab;>a388193 Merge branch 'branch_1.2.x' of github.com:qos-ch/logback into branch_1.2.x https://github.com/qos-ch/logback/commit/de44dc422bc3da1d7808283851324d960b492d4d;>de44dc4 prepare release 1.2.12 https://github.com/qos-ch/logback/commit/ca0cf172f680308938515b8a5d69348759ee947c;>ca0cf17 Merge pull request https://redirect.github.com/qos-ch/logback/issues/532;>#532 from joakime/fix-jetty-requestlog https://github.com/qos-ch/logback/commit/e31609b1980b9ba986344aae3cab7275fa2b4935;>e31609b removed unused files https://github.com/qos-ch/logback/commit/21e29efb284766f386781175b2ba18585b690154;>21e29ef Merge pull request https://redirect.github.com/qos-ch/logback/issues/567;>#567 from spliffone/LOGBACK-1633 https://github.com/qos-ch/logback/commit/e869000e1d5901e6aa6f46cc6575ee2137f15b69;>e869000 fix: published POM file contain the wrong scm URL https://github.com/qos-ch/logback/commit/009ea46cb81a015f2ca312bde6e823581b93b37a;>009ea46 version for next dev cycle Additional commits viewable in https://github.com/qos-ch/logback/compare/v_1.2.3...v_1.2.13;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/apache/sling-org-apache-sling-hc-support/network/alerts). -- 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] Bump ch.qos.logback:logback-classic from 1.2.3 to 1.3.12 [sling-org-apache-sling-sitemap]
dependabot[bot] closed pull request #14: Bump ch.qos.logback:logback-classic from 1.2.3 to 1.3.12 URL: https://github.com/apache/sling-org-apache-sling-sitemap/pull/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] Bump ch.qos.logback:logback-classic from 1.2.3 to 1.3.12 [sling-org-apache-sling-sitemap]
dependabot[bot] commented on PR #14: URL: https://github.com/apache/sling-org-apache-sling-sitemap/pull/14#issuecomment-1841731439 Superseded by #15. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] Bump ch.qos.logback:logback-classic from 1.2.3 to 1.2.13 [sling-org-apache-sling-sitemap]
dependabot[bot] opened a new pull request, #15: URL: https://github.com/apache/sling-org-apache-sling-sitemap/pull/15 Bumps [ch.qos.logback:logback-classic](https://github.com/qos-ch/logback) from 1.2.3 to 1.2.13. Commits https://github.com/qos-ch/logback/commit/2648b9e7fbb47426c89b9c93b411c07484e8f277;>2648b9e prepare release 1.2.13 https://github.com/qos-ch/logback/commit/bb095154be011267b64e37a1d401546e7cc2b7c3;>bb09515 fix CVE-2023-6378 https://github.com/qos-ch/logback/commit/45732949bfb845df04cbe65292cf48aaa090cb1d;>4573294 start work on 1.2.13-SNAPSHOT https://github.com/qos-ch/logback/commit/a388193052c298ca87cc64192319df723288c6ab;>a388193 Merge branch 'branch_1.2.x' of github.com:qos-ch/logback into branch_1.2.x https://github.com/qos-ch/logback/commit/de44dc422bc3da1d7808283851324d960b492d4d;>de44dc4 prepare release 1.2.12 https://github.com/qos-ch/logback/commit/ca0cf172f680308938515b8a5d69348759ee947c;>ca0cf17 Merge pull request https://redirect.github.com/qos-ch/logback/issues/532;>#532 from joakime/fix-jetty-requestlog https://github.com/qos-ch/logback/commit/e31609b1980b9ba986344aae3cab7275fa2b4935;>e31609b removed unused files https://github.com/qos-ch/logback/commit/21e29efb284766f386781175b2ba18585b690154;>21e29ef Merge pull request https://redirect.github.com/qos-ch/logback/issues/567;>#567 from spliffone/LOGBACK-1633 https://github.com/qos-ch/logback/commit/e869000e1d5901e6aa6f46cc6575ee2137f15b69;>e869000 fix: published POM file contain the wrong scm URL https://github.com/qos-ch/logback/commit/009ea46cb81a015f2ca312bde6e823581b93b37a;>009ea46 version for next dev cycle Additional commits viewable in https://github.com/qos-ch/logback/compare/v_1.2.3...v_1.2.13;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/apache/sling-org-apache-sling-sitemap/network/alerts). -- 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] Bump ch.qos.logback:logback-classic from 1.2.3 to 1.3.12 [sling-org-apache-sling-jcr-packageinit]
dependabot[bot] closed pull request #8: Bump ch.qos.logback:logback-classic from 1.2.3 to 1.3.12 URL: https://github.com/apache/sling-org-apache-sling-jcr-packageinit/pull/8 -- 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] Bump ch.qos.logback:logback-classic from 1.2.3 to 1.2.13 [sling-org-apache-sling-jcr-packageinit]
dependabot[bot] opened a new pull request, #9: URL: https://github.com/apache/sling-org-apache-sling-jcr-packageinit/pull/9 Bumps [ch.qos.logback:logback-classic](https://github.com/qos-ch/logback) from 1.2.3 to 1.2.13. Commits https://github.com/qos-ch/logback/commit/2648b9e7fbb47426c89b9c93b411c07484e8f277;>2648b9e prepare release 1.2.13 https://github.com/qos-ch/logback/commit/bb095154be011267b64e37a1d401546e7cc2b7c3;>bb09515 fix CVE-2023-6378 https://github.com/qos-ch/logback/commit/45732949bfb845df04cbe65292cf48aaa090cb1d;>4573294 start work on 1.2.13-SNAPSHOT https://github.com/qos-ch/logback/commit/a388193052c298ca87cc64192319df723288c6ab;>a388193 Merge branch 'branch_1.2.x' of github.com:qos-ch/logback into branch_1.2.x https://github.com/qos-ch/logback/commit/de44dc422bc3da1d7808283851324d960b492d4d;>de44dc4 prepare release 1.2.12 https://github.com/qos-ch/logback/commit/ca0cf172f680308938515b8a5d69348759ee947c;>ca0cf17 Merge pull request https://redirect.github.com/qos-ch/logback/issues/532;>#532 from joakime/fix-jetty-requestlog https://github.com/qos-ch/logback/commit/e31609b1980b9ba986344aae3cab7275fa2b4935;>e31609b removed unused files https://github.com/qos-ch/logback/commit/21e29efb284766f386781175b2ba18585b690154;>21e29ef Merge pull request https://redirect.github.com/qos-ch/logback/issues/567;>#567 from spliffone/LOGBACK-1633 https://github.com/qos-ch/logback/commit/e869000e1d5901e6aa6f46cc6575ee2137f15b69;>e869000 fix: published POM file contain the wrong scm URL https://github.com/qos-ch/logback/commit/009ea46cb81a015f2ca312bde6e823581b93b37a;>009ea46 version for next dev cycle Additional commits viewable in https://github.com/qos-ch/logback/compare/v_1.2.3...v_1.2.13;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/apache/sling-org-apache-sling-jcr-packageinit/network/alerts). -- 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] Bump ch.qos.logback:logback-classic from 1.2.3 to 1.3.12 [sling-org-apache-sling-junit-core]
dependabot[bot] commented on PR #22: URL: https://github.com/apache/sling-org-apache-sling-junit-core/pull/22#issuecomment-1841713412 Superseded by #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
[PR] Bump ch.qos.logback:logback-classic from 1.2.3 to 1.2.13 [sling-org-apache-sling-junit-core]
dependabot[bot] opened a new pull request, #23: URL: https://github.com/apache/sling-org-apache-sling-junit-core/pull/23 Bumps [ch.qos.logback:logback-classic](https://github.com/qos-ch/logback) from 1.2.3 to 1.2.13. Commits https://github.com/qos-ch/logback/commit/2648b9e7fbb47426c89b9c93b411c07484e8f277;>2648b9e prepare release 1.2.13 https://github.com/qos-ch/logback/commit/bb095154be011267b64e37a1d401546e7cc2b7c3;>bb09515 fix CVE-2023-6378 https://github.com/qos-ch/logback/commit/45732949bfb845df04cbe65292cf48aaa090cb1d;>4573294 start work on 1.2.13-SNAPSHOT https://github.com/qos-ch/logback/commit/a388193052c298ca87cc64192319df723288c6ab;>a388193 Merge branch 'branch_1.2.x' of github.com:qos-ch/logback into branch_1.2.x https://github.com/qos-ch/logback/commit/de44dc422bc3da1d7808283851324d960b492d4d;>de44dc4 prepare release 1.2.12 https://github.com/qos-ch/logback/commit/ca0cf172f680308938515b8a5d69348759ee947c;>ca0cf17 Merge pull request https://redirect.github.com/qos-ch/logback/issues/532;>#532 from joakime/fix-jetty-requestlog https://github.com/qos-ch/logback/commit/e31609b1980b9ba986344aae3cab7275fa2b4935;>e31609b removed unused files https://github.com/qos-ch/logback/commit/21e29efb284766f386781175b2ba18585b690154;>21e29ef Merge pull request https://redirect.github.com/qos-ch/logback/issues/567;>#567 from spliffone/LOGBACK-1633 https://github.com/qos-ch/logback/commit/e869000e1d5901e6aa6f46cc6575ee2137f15b69;>e869000 fix: published POM file contain the wrong scm URL https://github.com/qos-ch/logback/commit/009ea46cb81a015f2ca312bde6e823581b93b37a;>009ea46 version for next dev cycle Additional commits viewable in https://github.com/qos-ch/logback/compare/v_1.2.3...v_1.2.13;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/apache/sling-org-apache-sling-junit-core/network/alerts). -- 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] Bump ch.qos.logback:logback-classic from 1.2.3 to 1.3.12 [sling-org-apache-sling-jcr-packageinit]
dependabot[bot] commented on PR #8: URL: https://github.com/apache/sling-org-apache-sling-jcr-packageinit/pull/8#issuecomment-1841714212 Superseded by #9. -- 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] Bump ch.qos.logback:logback-classic from 1.2.3 to 1.2.13 [sling-org-apache-sling-installer-provider-jcr]
dependabot[bot] opened a new pull request, #8: URL: https://github.com/apache/sling-org-apache-sling-installer-provider-jcr/pull/8 Bumps [ch.qos.logback:logback-classic](https://github.com/qos-ch/logback) from 1.2.3 to 1.2.13. Commits https://github.com/qos-ch/logback/commit/2648b9e7fbb47426c89b9c93b411c07484e8f277;>2648b9e prepare release 1.2.13 https://github.com/qos-ch/logback/commit/bb095154be011267b64e37a1d401546e7cc2b7c3;>bb09515 fix CVE-2023-6378 https://github.com/qos-ch/logback/commit/45732949bfb845df04cbe65292cf48aaa090cb1d;>4573294 start work on 1.2.13-SNAPSHOT https://github.com/qos-ch/logback/commit/a388193052c298ca87cc64192319df723288c6ab;>a388193 Merge branch 'branch_1.2.x' of github.com:qos-ch/logback into branch_1.2.x https://github.com/qos-ch/logback/commit/de44dc422bc3da1d7808283851324d960b492d4d;>de44dc4 prepare release 1.2.12 https://github.com/qos-ch/logback/commit/ca0cf172f680308938515b8a5d69348759ee947c;>ca0cf17 Merge pull request https://redirect.github.com/qos-ch/logback/issues/532;>#532 from joakime/fix-jetty-requestlog https://github.com/qos-ch/logback/commit/e31609b1980b9ba986344aae3cab7275fa2b4935;>e31609b removed unused files https://github.com/qos-ch/logback/commit/21e29efb284766f386781175b2ba18585b690154;>21e29ef Merge pull request https://redirect.github.com/qos-ch/logback/issues/567;>#567 from spliffone/LOGBACK-1633 https://github.com/qos-ch/logback/commit/e869000e1d5901e6aa6f46cc6575ee2137f15b69;>e869000 fix: published POM file contain the wrong scm URL https://github.com/qos-ch/logback/commit/009ea46cb81a015f2ca312bde6e823581b93b37a;>009ea46 version for next dev cycle Additional commits viewable in https://github.com/qos-ch/logback/compare/v_1.2.3...v_1.2.13;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/apache/sling-org-apache-sling-installer-provider-jcr/network/alerts). -- 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] Bump ch.qos.logback:logback-classic from 1.2.3 to 1.3.12 [sling-org-apache-sling-junit-core]
dependabot[bot] closed pull request #22: Bump ch.qos.logback:logback-classic from 1.2.3 to 1.3.12 URL: https://github.com/apache/sling-org-apache-sling-junit-core/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
Re: [PR] Bump ch.qos.logback:logback-classic from 1.2.3 to 1.3.12 [sling-org-apache-sling-installer-provider-jcr]
dependabot[bot] closed pull request #7: Bump ch.qos.logback:logback-classic from 1.2.3 to 1.3.12 URL: https://github.com/apache/sling-org-apache-sling-installer-provider-jcr/pull/7 -- 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] Bump ch.qos.logback:logback-classic from 1.2.3 to 1.3.12 [sling-org-apache-sling-installer-provider-jcr]
dependabot[bot] commented on PR #7: URL: https://github.com/apache/sling-org-apache-sling-installer-provider-jcr/pull/7#issuecomment-1841712589 Superseded by #8. -- 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] Bump ch.qos.logback:logback-classic from 1.2.11 to 1.3.12 [sling-org-apache-sling-jcr-repoinit]
dependabot[bot] closed pull request #48: Bump ch.qos.logback:logback-classic from 1.2.11 to 1.3.12 URL: https://github.com/apache/sling-org-apache-sling-jcr-repoinit/pull/48 -- 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] Bump ch.qos.logback:logback-classic from 1.2.11 to 1.3.12 [sling-org-apache-sling-jcr-repoinit]
dependabot[bot] commented on PR #48: URL: https://github.com/apache/sling-org-apache-sling-jcr-repoinit/pull/48#issuecomment-1841708318 Superseded by #49. -- 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] Bump ch.qos.logback:logback-classic from 1.2.11 to 1.2.13 [sling-org-apache-sling-jcr-repoinit]
dependabot[bot] opened a new pull request, #49: URL: https://github.com/apache/sling-org-apache-sling-jcr-repoinit/pull/49 Bumps [ch.qos.logback:logback-classic](https://github.com/qos-ch/logback) from 1.2.11 to 1.2.13. Commits https://github.com/qos-ch/logback/commit/2648b9e7fbb47426c89b9c93b411c07484e8f277;>2648b9e prepare release 1.2.13 https://github.com/qos-ch/logback/commit/bb095154be011267b64e37a1d401546e7cc2b7c3;>bb09515 fix CVE-2023-6378 https://github.com/qos-ch/logback/commit/45732949bfb845df04cbe65292cf48aaa090cb1d;>4573294 start work on 1.2.13-SNAPSHOT https://github.com/qos-ch/logback/commit/a388193052c298ca87cc64192319df723288c6ab;>a388193 Merge branch 'branch_1.2.x' of github.com:qos-ch/logback into branch_1.2.x https://github.com/qos-ch/logback/commit/de44dc422bc3da1d7808283851324d960b492d4d;>de44dc4 prepare release 1.2.12 https://github.com/qos-ch/logback/commit/ca0cf172f680308938515b8a5d69348759ee947c;>ca0cf17 Merge pull request https://redirect.github.com/qos-ch/logback/issues/532;>#532 from joakime/fix-jetty-requestlog https://github.com/qos-ch/logback/commit/e31609b1980b9ba986344aae3cab7275fa2b4935;>e31609b removed unused files https://github.com/qos-ch/logback/commit/21e29efb284766f386781175b2ba18585b690154;>21e29ef Merge pull request https://redirect.github.com/qos-ch/logback/issues/567;>#567 from spliffone/LOGBACK-1633 https://github.com/qos-ch/logback/commit/e869000e1d5901e6aa6f46cc6575ee2137f15b69;>e869000 fix: published POM file contain the wrong scm URL https://github.com/qos-ch/logback/commit/009ea46cb81a015f2ca312bde6e823581b93b37a;>009ea46 version for next dev cycle Additional commits viewable in https://github.com/qos-ch/logback/compare/v_1.2.11...v_1.2.13;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/apache/sling-org-apache-sling-jcr-repoinit/network/alerts). -- 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] Bump ch.qos.logback:logback-classic from 1.2.10 to 1.3.12 [sling-org-apache-sling-commons-log]
dependabot[bot] closed pull request #12: Bump ch.qos.logback:logback-classic from 1.2.10 to 1.3.12 URL: https://github.com/apache/sling-org-apache-sling-commons-log/pull/12 -- 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] Bump ch.qos.logback:logback-classic from 1.2.10 to 1.3.12 [sling-org-apache-sling-commons-log]
dependabot[bot] commented on PR #12: URL: https://github.com/apache/sling-org-apache-sling-commons-log/pull/12#issuecomment-1841699396 Superseded by #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
[PR] Bump ch.qos.logback:logback-classic from 1.2.10 to 1.2.13 [sling-org-apache-sling-commons-log]
dependabot[bot] opened a new pull request, #14: URL: https://github.com/apache/sling-org-apache-sling-commons-log/pull/14 Bumps [ch.qos.logback:logback-classic](https://github.com/qos-ch/logback) from 1.2.10 to 1.2.13. Commits https://github.com/qos-ch/logback/commit/2648b9e7fbb47426c89b9c93b411c07484e8f277;>2648b9e prepare release 1.2.13 https://github.com/qos-ch/logback/commit/bb095154be011267b64e37a1d401546e7cc2b7c3;>bb09515 fix CVE-2023-6378 https://github.com/qos-ch/logback/commit/45732949bfb845df04cbe65292cf48aaa090cb1d;>4573294 start work on 1.2.13-SNAPSHOT https://github.com/qos-ch/logback/commit/a388193052c298ca87cc64192319df723288c6ab;>a388193 Merge branch 'branch_1.2.x' of github.com:qos-ch/logback into branch_1.2.x https://github.com/qos-ch/logback/commit/de44dc422bc3da1d7808283851324d960b492d4d;>de44dc4 prepare release 1.2.12 https://github.com/qos-ch/logback/commit/ca0cf172f680308938515b8a5d69348759ee947c;>ca0cf17 Merge pull request https://redirect.github.com/qos-ch/logback/issues/532;>#532 from joakime/fix-jetty-requestlog https://github.com/qos-ch/logback/commit/e31609b1980b9ba986344aae3cab7275fa2b4935;>e31609b removed unused files https://github.com/qos-ch/logback/commit/21e29efb284766f386781175b2ba18585b690154;>21e29ef Merge pull request https://redirect.github.com/qos-ch/logback/issues/567;>#567 from spliffone/LOGBACK-1633 https://github.com/qos-ch/logback/commit/e869000e1d5901e6aa6f46cc6575ee2137f15b69;>e869000 fix: published POM file contain the wrong scm URL https://github.com/qos-ch/logback/commit/009ea46cb81a015f2ca312bde6e823581b93b37a;>009ea46 version for next dev cycle Additional commits viewable in https://github.com/qos-ch/logback/compare/v_1.2.10...v_1.2.13;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/apache/sling-org-apache-sling-commons-log/network/alerts). -- 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] Bump ch.qos.logback:logback-classic from 1.1.2 to 1.3.12 [sling-org-apache-sling-launchpad-integration-tests]
dependabot[bot] closed pull request #19: Bump ch.qos.logback:logback-classic from 1.1.2 to 1.3.12 URL: https://github.com/apache/sling-org-apache-sling-launchpad-integration-tests/pull/19 -- 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] Bump ch.qos.logback:logback-classic from 1.1.2 to 1.2.13 [sling-org-apache-sling-launchpad-integration-tests]
dependabot[bot] opened a new pull request, #20: URL: https://github.com/apache/sling-org-apache-sling-launchpad-integration-tests/pull/20 Bumps [ch.qos.logback:logback-classic](https://github.com/qos-ch/logback) from 1.1.2 to 1.2.13. Commits See full diff in https://github.com/qos-ch/logback/commits/v_1.2.13;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/apache/sling-org-apache-sling-launchpad-integration-tests/network/alerts). -- 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] Bump ch.qos.logback:logback-classic from 1.1.2 to 1.3.12 [sling-org-apache-sling-launchpad-integration-tests]
dependabot[bot] commented on PR #19: URL: https://github.com/apache/sling-org-apache-sling-launchpad-integration-tests/pull/19#issuecomment-1841675784 Superseded by #20. -- 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] Bump ch.qos.logback:logback-core from 1.2.10 to 1.3.12 [sling-org-apache-sling-commons-log]
dependabot[bot] closed pull request #11: Bump ch.qos.logback:logback-core from 1.2.10 to 1.3.12 URL: https://github.com/apache/sling-org-apache-sling-commons-log/pull/11 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] Bump ch.qos.logback:logback-core from 1.2.10 to 1.2.13 [sling-org-apache-sling-commons-log]
dependabot[bot] opened a new pull request, #13: URL: https://github.com/apache/sling-org-apache-sling-commons-log/pull/13 Bumps [ch.qos.logback:logback-core](https://github.com/qos-ch/logback) from 1.2.10 to 1.2.13. Commits https://github.com/qos-ch/logback/commit/2648b9e7fbb47426c89b9c93b411c07484e8f277;>2648b9e prepare release 1.2.13 https://github.com/qos-ch/logback/commit/bb095154be011267b64e37a1d401546e7cc2b7c3;>bb09515 fix CVE-2023-6378 https://github.com/qos-ch/logback/commit/45732949bfb845df04cbe65292cf48aaa090cb1d;>4573294 start work on 1.2.13-SNAPSHOT https://github.com/qos-ch/logback/commit/a388193052c298ca87cc64192319df723288c6ab;>a388193 Merge branch 'branch_1.2.x' of github.com:qos-ch/logback into branch_1.2.x https://github.com/qos-ch/logback/commit/de44dc422bc3da1d7808283851324d960b492d4d;>de44dc4 prepare release 1.2.12 https://github.com/qos-ch/logback/commit/ca0cf172f680308938515b8a5d69348759ee947c;>ca0cf17 Merge pull request https://redirect.github.com/qos-ch/logback/issues/532;>#532 from joakime/fix-jetty-requestlog https://github.com/qos-ch/logback/commit/e31609b1980b9ba986344aae3cab7275fa2b4935;>e31609b removed unused files https://github.com/qos-ch/logback/commit/21e29efb284766f386781175b2ba18585b690154;>21e29ef Merge pull request https://redirect.github.com/qos-ch/logback/issues/567;>#567 from spliffone/LOGBACK-1633 https://github.com/qos-ch/logback/commit/e869000e1d5901e6aa6f46cc6575ee2137f15b69;>e869000 fix: published POM file contain the wrong scm URL https://github.com/qos-ch/logback/commit/009ea46cb81a015f2ca312bde6e823581b93b37a;>009ea46 version for next dev cycle Additional commits viewable in https://github.com/qos-ch/logback/compare/v_1.2.10...v_1.2.13;>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/apache/sling-org-apache-sling-commons-log/network/alerts). -- 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] Bump ch.qos.logback:logback-core from 1.2.10 to 1.3.12 [sling-org-apache-sling-commons-log]
dependabot[bot] commented on PR #11: URL: https://github.com/apache/sling-org-apache-sling-commons-log/pull/11#issuecomment-1841663500 Superseded by #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
Introduce spotless-maven-plugin
Hi, We never had any formalised code formatting rules nor ever provided any formatters for different IDEs (at least not that I am aware of). That often leads to undesired formatting changes in PRs. I propose to introduce https://github.com/diffplug/spotless/tree/main/plugin-maven to automatically enforce certain formatting rules during build (as well as to optionally apply those). There are quite some built-in rule sets. Apache Maven uses https://github.com/diffplug/spotless/tree/main/plugin-maven#palantir-java-format and https://github.com/diffplug/spotless/tree/main/plugin-maven#maven-pom quite successfully for a while now. I am open to using another rule set, but the important bit is that we can enforce that across different IDEs easily during the build and fixing is easy for contributors/committers as well. WDYT? Konrad
[jira] [Commented] (SLING-12180) Consider ProviderType annotations on package level as well
[ https://issues.apache.org/jira/browse/SLING-12180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17793408#comment-17793408 ] Carsten Ziegeler commented on SLING-12180: -- The mechanism currently used does not have access to package level annotations. This would be a completely new mechanism just for this use case. I haven't seen this annotation being used on the package level yet, and I would bet that there is other tooling out there which does not take it into account. I suggest we look at this, once we have an actual use case. > Consider ProviderType annotations on package level as well > -- > > Key: SLING-12180 > URL: https://issues.apache.org/jira/browse/SLING-12180 > Project: Sling > Issue Type: Bug > Components: Maven Plugins and Archetypes >Affects Versions: OSGi Feature Maven Plugin 1.8.0 >Reporter: Konrad Windszus >Priority: Major > > The annotation > https://docs.osgi.org/javadoc/osgi.annotation/7.0.0/org/osgi/annotation/versioning/ProviderType.html > can be used both on type level as well as on package level. If it is set on > package level that annotation takes precedence over all type level > annotations in that package. > In the context of SLING-12135 only class level annotations are being > considered. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (SLING-12181) Evaluate provider type information also directly from annotations
Konrad Windszus created SLING-12181: --- Summary: Evaluate provider type information also directly from annotations Key: SLING-12181 URL: https://issues.apache.org/jira/browse/SLING-12181 Project: Sling Issue Type: Improvement Affects Versions: Provider Type Checker Bnd Plugin 1.0.0 Reporter: Konrad Windszus Assignee: Konrad Windszus Fix For: Provider Type Checker Bnd Plugin 1.1.0 Currently the check implemented in SLING-12026 only retrieves the provider type information from the META-INF/api-info.json (being generated by SLING-12135). As fallback there should be direct evaluation of the annotations. The logic needs to be the same as in https://github.com/bndtools/bnd/blob/d06df066f402f1433b70c51f568c40a444b4518d/biz.aQute.bndlib/src/aQute/bnd/osgi/Analyzer.java#L1991, i.e. the annotation provider type needs to be evaluated both on package as well as on type level. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (SLING-12026) Check for implementation/extension of provider types
[ https://issues.apache.org/jira/browse/SLING-12026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus resolved SLING-12026. - Resolution: Fixed > Check for implementation/extension of provider types > > > Key: SLING-12026 > URL: https://issues.apache.org/jira/browse/SLING-12026 > Project: Sling > Issue Type: New Feature > Components: Bnd Plugins >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > Fix For: Provider Type Checker Bnd Plugin 1.0.0 > > > OSGi distinguishes between > [consumer|https://docs.osgi.org/javadoc/osgi.annotation/7.0.0/org/osgi/annotation/versioning/ConsumerType.html] > and > [provider|https://docs.osgi.org/javadoc/osgi.annotation/7.0.0/org/osgi/annotation/versioning/ProviderType.html] > types (either interfaces or classes). > Some bundles/features are only supposed to implement/extend consumer types in > order to be more stable against API changes. There should be a -feature model > analyser- bnd plugin enforcing this. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (SLING-12180) Consider ProviderType annotations on package level as well
[ https://issues.apache.org/jira/browse/SLING-12180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17793400#comment-17793400 ] Konrad Windszus commented on SLING-12180: - [~cziegeler] Can you have a look? Currently https://github.com/apache/sling-slingfeature-maven-plugin/blob/96ed3a18bd1b10111f5c92a9046fff19a9f7b7a8/src/main/java/org/apache/sling/feature/maven/mojos/apis/ClassFileProcessor.java#L36 does not consider the annotation on package level (like what is done in https://github.com/bndtools/bnd/blob/d06df066f402f1433b70c51f568c40a444b4518d/biz.aQute.bndlib/src/aQute/bnd/osgi/Analyzer.java#L844C7-L844C7). > Consider ProviderType annotations on package level as well > -- > > Key: SLING-12180 > URL: https://issues.apache.org/jira/browse/SLING-12180 > Project: Sling > Issue Type: Bug > Components: Maven Plugins and Archetypes >Affects Versions: OSGi Feature Maven Plugin 1.8.0 >Reporter: Konrad Windszus >Priority: Major > > The annotation > https://docs.osgi.org/javadoc/osgi.annotation/7.0.0/org/osgi/annotation/versioning/ProviderType.html > can be used both on type level as well as on package level. If it is set on > package level that annotation takes precedence over all type level > annotations in that package. > In the context of SLING-12135 only class level annotations are being > considered. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (SLING-12180) Consider ProviderType annotations on package level as well
Konrad Windszus created SLING-12180: --- Summary: Consider ProviderType annotations on package level as well Key: SLING-12180 URL: https://issues.apache.org/jira/browse/SLING-12180 Project: Sling Issue Type: Bug Components: Maven Plugins and Archetypes Affects Versions: OSGi Feature Maven Plugin 1.8.0 Reporter: Konrad Windszus The annotation https://docs.osgi.org/javadoc/osgi.annotation/7.0.0/org/osgi/annotation/versioning/ProviderType.html can be used both on type level as well as on package level. If it is set on package level that annotation takes precedence over all type level annotations in that package. In the context of SLING-12135 only class level annotations are being considered. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SLING-12026) Check for implementation/extension of provider types
[ https://issues.apache.org/jira/browse/SLING-12026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-12026: Description: OSGi distinguishes between [consumer|https://docs.osgi.org/javadoc/osgi.annotation/7.0.0/org/osgi/annotation/versioning/ConsumerType.html] and [provider|https://docs.osgi.org/javadoc/osgi.annotation/7.0.0/org/osgi/annotation/versioning/ProviderType.html] types (either interfaces or classes). Some bundles/features are only supposed to implement/extend consumer types in order to be more stable against API changes. There should be a -feature model analyser- bnd plugin enforcing this. was: OSGi distinguishes between [consumer|https://docs.osgi.org/javadoc/osgi.annotation/7.0.0/org/osgi/annotation/versioning/ConsumerType.html] and [provider|https://docs.osgi.org/javadoc/osgi.annotation/7.0.0/org/osgi/annotation/versioning/ProviderType.html] types (either interfaces or classes). Some bundles/features are only supposed to implement/extend consumer types in order to be more stable against API changes. There should be a feature model analyser enforcing this. > Check for implementation/extension of provider types > > > Key: SLING-12026 > URL: https://issues.apache.org/jira/browse/SLING-12026 > Project: Sling > Issue Type: New Feature > Components: Bnd Plugins >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > Fix For: Provider Type Checker Bnd Plugin 1.0.0 > > > OSGi distinguishes between > [consumer|https://docs.osgi.org/javadoc/osgi.annotation/7.0.0/org/osgi/annotation/versioning/ConsumerType.html] > and > [provider|https://docs.osgi.org/javadoc/osgi.annotation/7.0.0/org/osgi/annotation/versioning/ProviderType.html] > types (either interfaces or classes). > Some bundles/features are only supposed to implement/extend consumer types in > order to be more stable against API changes. There should be a -feature model > analyser- bnd plugin enforcing this. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SLING-12026) Check for implementation/extension of provider types
[ https://issues.apache.org/jira/browse/SLING-12026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-12026: Fix Version/s: Provider Type Checker Bnd Plugin 1.0.0 > Check for implementation/extension of provider types > > > Key: SLING-12026 > URL: https://issues.apache.org/jira/browse/SLING-12026 > Project: Sling > Issue Type: New Feature > Components: Bnd Plugins >Affects Versions: Provider Type Checker Bnd Plugin 1.0.0 >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > Fix For: Provider Type Checker Bnd Plugin 1.0.0 > > > OSGi distinguishes between > [consumer|https://docs.osgi.org/javadoc/osgi.annotation/7.0.0/org/osgi/annotation/versioning/ConsumerType.html] > and > [provider|https://docs.osgi.org/javadoc/osgi.annotation/7.0.0/org/osgi/annotation/versioning/ProviderType.html] > types (either interfaces or classes). > Some bundles/features are only supposed to implement/extend consumer types in > order to be more stable against API changes. There should be a feature model > analyser enforcing this. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SLING-12026) Check for implementation/extension of provider types
[ https://issues.apache.org/jira/browse/SLING-12026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-12026: Affects Version/s: (was: Provider Type Checker Bnd Plugin 1.0.0) > Check for implementation/extension of provider types > > > Key: SLING-12026 > URL: https://issues.apache.org/jira/browse/SLING-12026 > Project: Sling > Issue Type: New Feature > Components: Bnd Plugins >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > Fix For: Provider Type Checker Bnd Plugin 1.0.0 > > > OSGi distinguishes between > [consumer|https://docs.osgi.org/javadoc/osgi.annotation/7.0.0/org/osgi/annotation/versioning/ConsumerType.html] > and > [provider|https://docs.osgi.org/javadoc/osgi.annotation/7.0.0/org/osgi/annotation/versioning/ProviderType.html] > types (either interfaces or classes). > Some bundles/features are only supposed to implement/extend consumer types in > order to be more stable against API changes. There should be a feature model > analyser enforcing this. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[VOTE] Release Apache Sling Provider Type Checker Bnd Plugin 1.0.0
Hi, We solved 1 issue in this release: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310710=12354002=Text Staging repository: https://repository.apache.org/content/repositories/orgapachesling-2811/ 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 2811 /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 in advance for voting, Konrad
[jira] [Updated] (SLING-12026) Check for implementation/extension of provider types
[ https://issues.apache.org/jira/browse/SLING-12026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-12026: Component/s: Bnd Plugins (was: Feature Model Analyser) > Check for implementation/extension of provider types > > > Key: SLING-12026 > URL: https://issues.apache.org/jira/browse/SLING-12026 > Project: Sling > Issue Type: New Feature > Components: Bnd Plugins >Affects Versions: Feature Model Analyser 2.0.0 >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > > OSGi distinguishes between > [consumer|https://docs.osgi.org/javadoc/osgi.annotation/7.0.0/org/osgi/annotation/versioning/ConsumerType.html] > and > [provider|https://docs.osgi.org/javadoc/osgi.annotation/7.0.0/org/osgi/annotation/versioning/ProviderType.html] > types (either interfaces or classes). > Some bundles/features are only supposed to implement/extend consumer types in > order to be more stable against API changes. There should be a feature model > analyser enforcing this. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SLING-12026) Check for implementation/extension of provider types
[ https://issues.apache.org/jira/browse/SLING-12026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-12026: Affects Version/s: Provider Type Checker Bnd Plugin 1.0.0 > Check for implementation/extension of provider types > > > Key: SLING-12026 > URL: https://issues.apache.org/jira/browse/SLING-12026 > Project: Sling > Issue Type: New Feature > Components: Bnd Plugins >Affects Versions: Provider Type Checker Bnd Plugin 1.0.0 >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > > OSGi distinguishes between > [consumer|https://docs.osgi.org/javadoc/osgi.annotation/7.0.0/org/osgi/annotation/versioning/ConsumerType.html] > and > [provider|https://docs.osgi.org/javadoc/osgi.annotation/7.0.0/org/osgi/annotation/versioning/ProviderType.html] > types (either interfaces or classes). > Some bundles/features are only supposed to implement/extend consumer types in > order to be more stable against API changes. There should be a feature model > analyser enforcing this. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SLING-12026) Check for implementation/extension of provider types
[ https://issues.apache.org/jira/browse/SLING-12026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-12026: Affects Version/s: (was: Feature Model Analyser 2.0.0) > Check for implementation/extension of provider types > > > Key: SLING-12026 > URL: https://issues.apache.org/jira/browse/SLING-12026 > Project: Sling > Issue Type: New Feature > Components: Bnd Plugins >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > > OSGi distinguishes between > [consumer|https://docs.osgi.org/javadoc/osgi.annotation/7.0.0/org/osgi/annotation/versioning/ConsumerType.html] > and > [provider|https://docs.osgi.org/javadoc/osgi.annotation/7.0.0/org/osgi/annotation/versioning/ProviderType.html] > types (either interfaces or classes). > Some bundles/features are only supposed to implement/extend consumer types in > order to be more stable against API changes. There should be a feature model > analyser enforcing this. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: ASM library to parse class files?
Done now: https://github.com/apache/sling-org-apache-sling-providertype-bnd-plugin > On 1. Dec 2023, at 13:26, Stefan Seifert > wrote: > > >> We used different approaches for package and artifact names in >> https://github.com/apache/sling-org-apache-sling-caconfig-bnd- >> plugin/tree/master and https://github.com/apache/sling-org-apache-sling- >> bnd-models. > > yes, that was my fault (i created both artifacts but in quite different > points in time) > >> I would propose to create a dedicated repository for it at >> sling-org-apache-sling-providertype-bnd-plugin > > sounds good to me. > > stefan >
[jira] [Created] (SLING-12179) Make i18n optional
Karl Pauls created SLING-12179: -- Summary: Make i18n optional Key: SLING-12179 URL: https://issues.apache.org/jira/browse/SLING-12179 Project: Sling Issue Type: Improvement Components: Scripting Affects Versions: Scripting HTL Engine 1.4.22-1.4.0 Reporter: Karl Pauls Assignee: Karl Pauls Fix For: Scripting HTL Engine 1.4.24-1.4.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] Make i18n dependency optional [sling-org-apache-sling-scripting-sightly]
karlpauls merged PR #24: URL: https://github.com/apache/sling-org-apache-sling-scripting-sightly/pull/24 -- 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] Make sling models really optional. [sling-org-apache-sling-scripting-sightly]
karlpauls merged PR #25: URL: https://github.com/apache/sling-org-apache-sling-scripting-sightly/pull/25 -- 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-12178 - Make commons metrics optional [sling-org-apache-sling-xss]
rombert commented on PR #41: URL: https://github.com/apache/sling-org-apache-sling-xss/pull/41#issuecomment-1840415648 Thanks! -- 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] Make commons metrics optional [sling-org-apache-sling-xss]
karlpauls commented on PR #41: URL: https://github.com/apache/sling-org-apache-sling-xss/pull/41#issuecomment-1840394665 @rombert, ok, [SLING-12178](https://issues.apache.org/jira/browse/SLING-12178) -- 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-12178) Make commons metrics optional in xss bundle
[ https://issues.apache.org/jira/browse/SLING-12178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls resolved SLING-12178. Resolution: Fixed Done in https://github.com/apache/sling-org-apache-sling-xss/pull/41 > Make commons metrics optional in xss bundle > --- > > Key: SLING-12178 > URL: https://issues.apache.org/jira/browse/SLING-12178 > Project: Sling > Issue Type: Improvement > Components: XSS Protection API >Affects Versions: XSS Protection API 2.4.0 >Reporter: Karl Pauls >Assignee: Karl Pauls >Priority: Major > Fix For: XSS Protection API 2.4.2 > > > Following the pattern we use in the other bundles, it would be good if the > sling metrics would be optional for the xss bundle. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (SLING-12178) Make commons metrics optional in xss bundle
Karl Pauls created SLING-12178: -- Summary: Make commons metrics optional in xss bundle Key: SLING-12178 URL: https://issues.apache.org/jira/browse/SLING-12178 Project: Sling Issue Type: Improvement Components: XSS Protection API Affects Versions: XSS Protection API 2.4.0 Reporter: Karl Pauls Assignee: Karl Pauls Fix For: XSS Protection API 2.4.2 Following the pattern we use in the other bundles, it would be good if the sling metrics would be optional for the xss bundle. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] Make commons metrics optional [sling-org-apache-sling-xss]
rombert commented on PR #41: URL: https://github.com/apache/sling-org-apache-sling-xss/pull/41#issuecomment-1840378110 @karlpauls / @cziegeler - can you please create a Jira for this? Seems a significant enough change. Thanks! -- 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] Make sling models really optional. [sling-org-apache-sling-scripting-sightly]
karlpauls opened a new pull request, #25: URL: https://github.com/apache/sling-org-apache-sling-scripting-sightly/pull/25 (no comment) -- 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] Make commons metrics optional [sling-org-apache-sling-xss]
karlpauls merged PR #41: URL: https://github.com/apache/sling-org-apache-sling-xss/pull/41 -- 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] Make i18n dependency optional [sling-org-apache-sling-scripting-sightly]
cziegeler commented on code in PR #24:
URL:
https://github.com/apache/sling-org-apache-sling-scripting-sightly/pull/24#discussion_r1415084666
##
src/main/java/org/apache/sling/scripting/sightly/impl/engine/extension/I18nRuntimeExtension.java:
##
@@ -61,11 +61,22 @@ public Object call(final RenderContext renderContext,
Object... arguments) {
return get(bindings, text, locale, basename, hint);
}
+private Object getResourceBundleProvider(SlingScriptHelper
slingScriptHelper) {
+Class clazz;
+try {
+clazz =
getClass().getClassLoader().loadClass("org.apache.sling.i18n.ResourceBundleProvider");
+} catch (Throwable t) {
+LOG.warn("i18n package not available");
Review Comment:
I think it would be good to log the warn only once
--
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
