[GitHub] [sling-org-apache-sling-caconfig-integration-tests] sonarcloud[bot] commented on pull request #1: SLING-11114 update SLING API to 2.21.0

sonarcloud[bot] commented on PR #1: URL: https://github.com/apache/sling-org-apache-sling-caconfig-integration-tests/pull/1#issuecomment-1287558756 Kudos, SonarCloud Quality Gate passed!    [![Quality Gate passed](https://sonarsource.github.io/sonarcloud-github-static-resources/v2/checks/Qu

Re: Discuss policy for updating dependencies

I would also like to reiterate that if what you depend on is using proper semantic package versioning and the version numbers you depend on have not changed, then there would be no harm in updating the minimum version in your pom to the newer one. The output in your manifest would be identical. Ho

[GitHub] [sling-org-apache-sling-models-impl] sonarcloud[bot] commented on pull request #38: Add missing test case for AnnotationConflictsTest

sonarcloud[bot] commented on PR #38: URL: https://github.com/apache/sling-org-apache-sling-models-impl/pull/38#issuecomment-1287536875 Kudos, SonarCloud Quality Gate passed!    [![Quality Gate passed](https://sonarsource.github.io/sonarcloud-github-static-resources/v2/checks/QualityGateBadg

[jira] [Updated] (SLING-11633) ClientSideTeleporter throwing illegal argument when target byte code is > 1.8

[ https://issues.apache.org/jira/browse/SLING-11633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Scott Yuan updated SLING-11633: --- Attachment: (was: mylab-1.zip) > ClientSideTeleporter throwing illegal argument when target byte

[jira] [Created] (SLING-11633) ClientSideTeleporter throwing illegal argument when target byte code is > 1.8

Scott Yuan created SLING-11633: -- Summary: ClientSideTeleporter throwing illegal argument when target byte code is > 1.8 Key: SLING-11633 URL: https://issues.apache.org/jira/browse/SLING-11633 Project: Sl

[jira] [Resolved] (SLING-11632) Update to Sling Bundle Parent 49

[ https://issues.apache.org/jira/browse/SLING-11632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz resolved SLING-11632. -- Resolution: Done > Update to Sling Bundle Parent 49 > > >

[jira] [Created] (SLING-11632) Update to Sling Bundle Parent 49

Oliver Lietz created SLING-11632: Summary: Update to Sling Bundle Parent 49 Key: SLING-11632 URL: https://issues.apache.org/jira/browse/SLING-11632 Project: Sling Issue Type: Task C

[GitHub] [sling-org-apache-sling-scripting-sightly] kwin commented on pull request #20: SLING-11538 add output context for JSON string

kwin commented on PR #20: URL: https://github.com/apache/sling-org-apache-sling-scripting-sightly/pull/20#issuecomment-1286608565 @raducotescu I will merge beginning of next week. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitH

Re: Discuss policy for updating dependencies

> > >> For Sling Starter this is obviously us. >> >> I would recommend to introduce some automated means (apart from >> dependabot) to check for vulnerabilities on all Maven projects which are >> not OSGi bundles. >> Something like >> https://jeremylong.github.io/DependencyCheck/dependency-check

Re: Discuss policy for updating dependencies

Am Mi., 19. Okt. 2022 um 20:05 Uhr schrieb Konrad Windszus : > Hi, > There are lots of vulnerabilities reported which do not affect our usage > of dependencies. > Therefore I am still in favour of putting the responsibility towards those > who build applications/distributions out of Sling bundles.