Re: [PR] Bump jsoup from 1.15.1 to 1.15.3 [sling-org-apache-sling-scripting-core]
cziegeler merged PR #21: URL: https://github.com/apache/sling-org-apache-sling-scripting-core/pull/21 -- 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-12103) Replace usage of commons.osgi with Converter
[ https://issues.apache.org/jira/browse/SLING-12103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-12103. -- Resolution: Fixed https://github.com/apache/sling-org-apache-sling-scripting-core/commit/1f4ff517c39e2f561530da863ab8926d14c96702 > Replace usage of commons.osgi with Converter > > > Key: SLING-12103 > URL: https://issues.apache.org/jira/browse/SLING-12103 > Project: Sling > Issue Type: Improvement > Components: Scripting >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler >Priority: Major > Fix For: Scripting Core 2.4.10 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (SLING-12103) Replace usage of commons.osgi with Converter
Carsten Ziegeler created SLING-12103: Summary: Replace usage of commons.osgi with Converter Key: SLING-12103 URL: https://issues.apache.org/jira/browse/SLING-12103 Project: Sling Issue Type: Improvement Components: Scripting Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Scripting Core 2.4.10 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (SLING-12026) Check for implementation/extension of provider types
[ https://issues.apache.org/jira/browse/SLING-12026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17775869#comment-17775869 ] Konrad Windszus commented on SLING-12026: - A new repository has been created for that check (and potentially others which need to inspect bytecode) in https://github.com/apache/sling-org-apache-sling-feature-analyser-classes. > 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: Feature Model Analyser >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-12056) Add Java 21 as additional default build JDK
[ https://issues.apache.org/jira/browse/SLING-12056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-12056: Summary: Add Java 21 as additional default build JDK (was: Add Java 21 as additional build JDK) > Add Java 21 as additional default build JDK > --- > > Key: SLING-12056 > URL: https://issues.apache.org/jira/browse/SLING-12056 > Project: Sling > Issue Type: Improvement > Components: Build and Source Control >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > > Currently our projects build on Java 11 and 17 by default on Jenkins. We > should include Java 21 as well. This requires a Temurin release though which > did not happen yet: https://github.com/adoptium/adoptium/issues/248. > Compare with > https://cwiki.apache.org/confluence/display/SLING/Hackathon+in+Berlin+-+September+2023 -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] Clarify incoming/outgoing mapping [sling-site]
kwin commented on PR #139: URL: https://github.com/apache/sling-site/pull/139#issuecomment-1764881197 This requires an update to the Javadoc of https://github.com/apache/sling-org-apache-sling-api/blob/e80860eb12dc7314dae1522c9964a4b055d24de3/src/main/java/org/apache/sling/api/resource/mapping/ResourceMapper.java#L84-L86 as well, as that incorrectly states that there is always a full URL (incl. host) being returned. -- 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] Clarify incoming/outgoing mapping [sling-site]
kwin opened a new pull request, #139: URL: https://github.com/apache/sling-site/pull/139 Clarify when a full URL (incl. protocol and host) can be expected as outcome of outgoing mapping call -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (SLING-12089) Jenkins: Generate javadocs to spot illegal javadoc markup in sources
[
https://issues.apache.org/jira/browse/SLING-12089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17775832#comment-17775832
]
Mark Adamcin commented on SLING-12089:
--
[~sseifert] I think another piece of this to look into is a potential
difference in behavior between Eclipse's Organize Imports and IntelliJ's
Optimize Imports. IntelliJ doesn't remove imports that are only used in javadoc
{{{@link}}} macros, but I think Eclipse might be doing that.
{{javadoc:javadoc}} was passing on my branch when I ran it locally, but the
javadoc seems to have needed correction after your "remove unused imports"
commits.
I looked up what can be done for Intellij, and there is this option that I can
change to always use FQNs in javadoc:
!image-2023-10-16-09-24-58-984.png|width=543,height=372!
Maybe there is a setting in Eclipse to retain imports that are referenced in
javadocs, or to modify the link to a fully-qualified form when the import is
removed?
> Jenkins: Generate javadocs to spot illegal javadoc markup in sources
>
>
> Key: SLING-12089
> URL: https://issues.apache.org/jira/browse/SLING-12089
> Project: Sling
> Issue Type: Improvement
> Components: Tooling
>Reporter: Stefan Seifert
>Assignee: Stefan Seifert
>Priority: Major
> Attachments: image-2023-10-16-09-24-58-984.png
>
>
> if often happens that releases fail due to small javadoc errors, which get
> obvious when the "javadoc:javadoc" goal is executed on the command line. but
> this does not fail our CI builds, that's why it often goes unnoticed for
> quite some time (also in PRs).
> we should add that goal to our default build goals in jenkins.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (SLING-12089) Jenkins: Generate javadocs to spot illegal javadoc markup in sources
[ https://issues.apache.org/jira/browse/SLING-12089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Adamcin updated SLING-12089: - Attachment: image-2023-10-16-09-24-58-984.png > Jenkins: Generate javadocs to spot illegal javadoc markup in sources > > > Key: SLING-12089 > URL: https://issues.apache.org/jira/browse/SLING-12089 > Project: Sling > Issue Type: Improvement > Components: Tooling >Reporter: Stefan Seifert >Assignee: Stefan Seifert >Priority: Major > Attachments: image-2023-10-16-09-24-58-984.png > > > if often happens that releases fail due to small javadoc errors, which get > obvious when the "javadoc:javadoc" goal is executed on the command line. but > this does not fail our CI builds, that's why it often goes unnoticed for > quite some time (also in PRs). > we should add that goal to our default build goals in jenkins. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SLING-12038) [osgi-mock] add support for reified OSGi config annotations as test parameters
[ https://issues.apache.org/jira/browse/SLING-12038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert updated SLING-12038: --- Fix Version/s: Testing OSGi Mock 3.4.0 > [osgi-mock] add support for reified OSGi config annotations as test parameters > -- > > Key: SLING-12038 > URL: https://issues.apache.org/jira/browse/SLING-12038 > Project: Sling > Issue Type: Improvement > Components: Testing >Affects Versions: Testing OSGi Mock 3.3.10 >Reporter: Mark Adamcin >Assignee: Stefan Seifert >Priority: Major > Labels: has-pr > Fix For: Testing OSGi Mock 3.4.0 > > > This PR adds a JUnit 5 extension and JUnit 4 rule for unit testing OSGi > components which leverage R7 spec configuration annotations and [Component > Property > Types|https://docs.osgi.org/specification/osgi.cmpn/7.0.0/service.component.html#service.component-component.property.types]. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (SLING-12038) [osgi-mock] add support for reified OSGi config annotations as test parameters
[ https://issues.apache.org/jira/browse/SLING-12038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert resolved SLING-12038. Resolution: Fixed * https://github.com/apache/sling-org-apache-sling-testing-osgi-mock/commit/c55d97ba266e0630200fcbb378b3f102d2dfba90 * https://github.com/apache/sling-site/commit/5ee87a634864aa03f43b1bbda2310ed9a0e70616 > [osgi-mock] add support for reified OSGi config annotations as test parameters > -- > > Key: SLING-12038 > URL: https://issues.apache.org/jira/browse/SLING-12038 > Project: Sling > Issue Type: Improvement > Components: Testing >Affects Versions: Testing OSGi Mock 3.3.10 >Reporter: Mark Adamcin >Assignee: Stefan Seifert >Priority: Major > Labels: has-pr > > This PR adds a JUnit 5 extension and JUnit 4 rule for unit testing OSGi > components which leverage R7 spec configuration annotations and [Component > Property > Types|https://docs.osgi.org/specification/osgi.cmpn/7.0.0/service.component.html#service.component-component.property.types]. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] SLING-12038 add documentation for OSGi Mocks Config Annotations [sling-site]
stefanseifert merged PR #135: URL: https://github.com/apache/sling-site/pull/135 -- 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-12038 add support for reified OSGi config annotations as test parameters [sling-org-apache-sling-testing-osgi-mock]
stefanseifert merged PR #31: URL: https://github.com/apache/sling-org-apache-sling-testing-osgi-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] SLING-12038 add support for reified OSGi config annotations as test parameters [sling-org-apache-sling-testing-osgi-mock]
stefanseifert commented on PR #31: URL: https://github.com/apache/sling-org-apache-sling-testing-osgi-mock/pull/31#issuecomment-1764497387 thanks, i will merge it! (the jenkins CI tests on windows are flaky, but that is not related to this PR, we have to take care of this separately) -- 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-12038 add support for reified OSGi config annotations as test parameters [sling-org-apache-sling-testing-osgi-mock]
sonarcloud[bot] commented on PR #31: URL: https://github.com/apache/sling-org-apache-sling-testing-osgi-mock/pull/31#issuecomment-1764457971 Kudos, SonarCloud Quality Gate passed! [](https://sonarcloud.io/dashboard?id=apache_sling-org-apache-sling-testing-osgi-mock=31) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock=31=false=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock=31=false=BUG) [0 Bugs](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock=31=false=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock=31=false=VULNERABILITY) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock=31=false=VULNERABILITY) [0 Vulnerabilities](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock=31=false=VULNERABILITY) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-testing-osgi-mock=31=false=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-testing-osgi-mock=31=false=SECURITY_HOTSPOT) [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-testing-osgi-mock=31=false=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock=31=false=CODE_SMELL) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock=31=false=CODE_SMELL) [0 Code Smells](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock=31=false=CODE_SMELL) [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-testing-osgi-mock=31=new_coverage=list) [100.0% Coverage](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-testing-osgi-mock=31=new_coverage=list) [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-testing-osgi-mock=31=new_duplicated_lines_density=list) [0.0% Duplication](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-testing-osgi-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
[jira] [Resolved] (SLING-12089) Jenkins: Generate javadocs to spot illegal javadoc markup in sources
[ https://issues.apache.org/jira/browse/SLING-12089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert resolved SLING-12089. Assignee: Stefan Seifert Resolution: Fixed https://github.com/apache/sling-tooling-jenkins/pull/19/commits/8aa2a2a7ce776a2938ea4410dc62b9c61bca4893 > Jenkins: Generate javadocs to spot illegal javadoc markup in sources > > > Key: SLING-12089 > URL: https://issues.apache.org/jira/browse/SLING-12089 > Project: Sling > Issue Type: Improvement > Components: Tooling >Reporter: Stefan Seifert >Assignee: Stefan Seifert >Priority: Major > > if often happens that releases fail due to small javadoc errors, which get > obvious when the "javadoc:javadoc" goal is executed on the command line. but > this does not fail our CI builds, that's why it often goes unnoticed for > quite some time (also in PRs). > we should add that goal to our default build goals in jenkins. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] SLING-12089 Jenkins: Generate javadocs to spot illegal javadoc markup in sources [sling-tooling-jenkins]
stefanseifert merged PR #19: URL: https://github.com/apache/sling-tooling-jenkins/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
Re: [PR] SLING-12080 Update to Bnd 7.0.0 [sling-parent]
sonarcloud[bot] commented on PR #37: URL: https://github.com/apache/sling-parent/pull/37#issuecomment-1764282507 Kudos, SonarCloud Quality Gate passed! [](https://sonarcloud.io/dashboard?id=apache_sling-parent=37) [](https://sonarcloud.io/project/issues?id=apache_sling-parent=37=false=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-parent=37=false=BUG) [0 Bugs](https://sonarcloud.io/project/issues?id=apache_sling-parent=37=false=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-parent=37=false=VULNERABILITY) [](https://sonarcloud.io/project/issues?id=apache_sling-parent=37=false=VULNERABILITY) [0 Vulnerabilities](https://sonarcloud.io/project/issues?id=apache_sling-parent=37=false=VULNERABILITY) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-parent=37=false=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-parent=37=false=SECURITY_HOTSPOT) [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_sling-parent=37=false=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/issues?id=apache_sling-parent=37=false=CODE_SMELL) [](https://sonarcloud.io/project/issues?id=apache_sling-parent=37=false=CODE_SMELL) [0 Code Smells](https://sonarcloud.io/project/issues?id=apache_sling-parent=37=false=CODE_SMELL) [](https://sonarcloud.io/component_measures?id=apache_sling-parent=37) No Coverage information [](https://sonarcloud.io/component_measures?id=apache_sling-parent=37=new_duplicated_lines_density=list) [0.0% Duplication](https://sonarcloud.io/component_measures?id=apache_sling-parent=37=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] SLING-12077: migrate to jakarta.json [sling-org-apache-sling-adapter]
sonarcloud[bot] commented on PR #2: URL: https://github.com/apache/sling-org-apache-sling-adapter/pull/2#issuecomment-1764200119 Kudos, SonarCloud Quality Gate passed! [](https://sonarcloud.io/dashboard?id=apache_sling-org-apache-sling-adapter=2) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-adapter=2=false=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-adapter=2=false=BUG) [0 Bugs](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-adapter=2=false=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-adapter=2=false=VULNERABILITY) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-adapter=2=false=VULNERABILITY) [0 Vulnerabilities](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-adapter=2=false=VULNERABILITY) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-adapter=2=false=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-adapter=2=false=SECURITY_HOTSPOT) [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-adapter=2=false=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-adapter=2=false=CODE_SMELL) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-adapter=2=false=CODE_SMELL) [0 Code Smells](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-adapter=2=false=CODE_SMELL) [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-adapter=2=coverage=list) No Coverage information [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-adapter=2=new_duplicated_lines_density=list) [0.0% Duplication](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-adapter=2=new_duplicated_lines_density=list) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Resolved] (SLING-12102) Content Parser: Update to Parent 52
[ https://issues.apache.org/jira/browse/SLING-12102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert resolved SLING-12102. Resolution: Fixed * https://github.com/apache/sling-org-apache-sling-contentparser-api/commit/78dca0a28e293e3706c5c198d55bd5332671f1d9 * https://github.com/apache/sling-org-apache-sling-contentparser-testutils/commit/3cebf3db2e11af432b1e46e1bf3b9f7819c76a32 * https://github.com/apache/sling-org-apache-sling-contentparser-json/commit/5ebc8223db2ce1981da955c34774f49a63aeb5c5 * https://github.com/apache/sling-org-apache-sling-contentparser-xml/commit/81f9fd2126e1eb56ea7da9c4abcc74f8c7f4d51a * https://github.com/apache/sling-org-apache-sling-contentparser-xml-jcr/commit/13486e2de95ca4caa06aba87e177dd497be2134e > Content Parser: Update to Parent 52 > --- > > Key: SLING-12102 > URL: https://issues.apache.org/jira/browse/SLING-12102 > Project: Sling > Issue Type: Improvement > Components: Content Parser >Affects Versions: Content Parser API 2.0.0, Content Parser JSON 2.0.0, > Content Parser XML 2.0.0, Content Parser XML JCR 2.0.0, Content Parser Test > Utilities 2.0.0 >Reporter: Stefan Seifert >Assignee: Stefan Seifert >Priority: Major > Fix For: Content Parser API 2.0.2, Content Parser Test Utilities > 2.0.2, Content Parser JSON 2.0.2, Content Parser XML 2.0.2, Content Parser > XML JCR 2.0.2 > > > update to latest parent, fix build with java 17 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (SLING-12102) Content Parser: Update to Parent 52
Stefan Seifert created SLING-12102: -- Summary: Content Parser: Update to Parent 52 Key: SLING-12102 URL: https://issues.apache.org/jira/browse/SLING-12102 Project: Sling Issue Type: Improvement Components: Content Parser Affects Versions: Content Parser Test Utilities 2.0.0, Content Parser XML JCR 2.0.0, Content Parser XML 2.0.0, Content Parser JSON 2.0.0, Content Parser API 2.0.0 Reporter: Stefan Seifert Assignee: Stefan Seifert Fix For: Content Parser API 2.0.2, Content Parser Test Utilities 2.0.2, Content Parser JSON 2.0.2, Content Parser XML 2.0.2, Content Parser XML JCR 2.0.2 update to latest parent, fix build with java 17 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[Jenkins] Sling » Modules » sling-org-apache-sling-starter » master #1083 is FIXED
Please see https://ci-builds.apache.org/job/Sling/job/modules/job/sling-org-apache-sling-starter/job/master/1083/ for details. No further emails will be sent until the status of the build is changed.
[jira] [Closed] (SLING-12090) sling-mock: Make compatible with ResourceResolver 1.11.0
[ https://issues.apache.org/jira/browse/SLING-12090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seifert closed SLING-12090. -- > sling-mock: Make compatible with ResourceResolver 1.11.0 > > > Key: SLING-12090 > URL: https://issues.apache.org/jira/browse/SLING-12090 > Project: Sling > Issue Type: Bug > Components: Testing >Affects Versions: Testing Sling Mock 3.4.12 >Reporter: Stefan Seifert >Assignee: Stefan Seifert >Priority: Major > Fix For: Testing Sling Mock 3.4.14 > > > SLING-12019 introduced a change in ResourceResolverFactoryActivator which > changes the registration of ResourceResolverFactory services into an > asynchronous process - which breaks most of the sling-mock based unit tests. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] no-jira / no-merge : only to trigger tests [sling-org-apache-sling-event]
stefan-egli closed pull request #33: no-jira / no-merge : only to trigger tests URL: https://github.com/apache/sling-org-apache-sling-event/pull/33 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[RESULT] [VOTE] Release Apache Sling Testing Sling Mock 3.4.14
Hi, The vote has passed with the following result : +1 (binding): Stefan Seifert, Daniel Klco, Robert Munteanu I will copy this release to the Sling dist directory and promote the artifacts to the central Maven repository. stefan
[jira] [Assigned] (SLING-12098) Update Testing PaxExam to 4.0.0
[ https://issues.apache.org/jira/browse/SLING-12098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler reassigned SLING-12098: Assignee: Carsten Ziegeler > Update Testing PaxExam to 4.0.0 > --- > > Key: SLING-12098 > URL: https://issues.apache.org/jira/browse/SLING-12098 > Project: Sling > Issue Type: Sub-task > Components: Scripting >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler >Priority: Major > Fix For: Scripting Core 2.4.10 > > > In order to make it easier to work on this module, we should update to the > latest testing paxeam 4.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SLING-11900) Provide alternative terminology for inequitable terms
[ https://issues.apache.org/jira/browse/SLING-11900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Egli closed SLING-11900. --- > Provide alternative terminology for inequitable terms > - > > Key: SLING-11900 > URL: https://issues.apache.org/jira/browse/SLING-11900 > Project: Sling > Issue Type: Improvement > Components: Event >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler >Priority: Major > Fix For: Event 4.3.14 > > > The configuration for the jobs is using white/black list which is considered > inequitable terminology. Therefore, some more acceptable equivalents should > be provided for these terms. The proposal is to switch to allow/deny list -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SLING-11923) Sling Events does not Build on Java 17
[
https://issues.apache.org/jira/browse/SLING-11923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Egli closed SLING-11923.
---
> Sling Events does not Build on Java 17
> --
>
> Key: SLING-11923
> URL: https://issues.apache.org/jira/browse/SLING-11923
> Project: Sling
> Issue Type: Bug
> Components: Event
>Affects Versions: Event 4.3.12
>Reporter: Dan Klco
>Assignee: Rishabh Daim
>Priority: Major
> Fix For: Event 4.3.14
>
>
> Attempting to build Sling Events with Java 17 fails with:
> {code:java}
> [main] INFO org.apache.jackrabbit.oak.plugins.index.IndexUpdate - Reindexing
> completed
> [ERROR] Tests run: 4, Failures: 0, Errors: 4, Skipped: 0, Time elapsed: 1.935
> s <<< FAILURE! - in org.apache.sling.event.impl.jobs.queues.TestTopicHalting
> [ERROR]
> org.apache.sling.event.impl.jobs.queues.TestTopicHalting.testUnhalting Time
> elapsed: 1.506 s <<< ERROR!
> java.lang.NoClassDefFoundError: java/security/acl/Group
> at java.base/java.lang.ClassLoader.defineClass1(Native Method)
> at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1012)
> at
> java.base/java.security.SecureClassLoader.defineClass(SecureClassLoader.java:150)
> at
> java.base/jdk.internal.loader.BuiltinClassLoader.defineClass(BuiltinClassLoader.java:862)
> at
> java.base/jdk.internal.loader.BuiltinClassLoader.findClassOnClassPathOrNull(BuiltinClassLoader.java:760)
> at
> java.base/jdk.internal.loader.BuiltinClassLoader.loadClassOrNull(BuiltinClassLoader.java:681)
> at
> java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:639)
>
> {code}
> This class is deprecated for removal in Java 11:
> https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/security/acl/Group.html
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (SLING-12074) ScriptingVariablesConsolePlugin might use wrong security provider
[ https://issues.apache.org/jira/browse/SLING-12074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-12074. -- Resolution: Fixed > ScriptingVariablesConsolePlugin might use wrong security provider > - > > Key: SLING-12074 > URL: https://issues.apache.org/jira/browse/SLING-12074 > Project: Sling > Issue Type: Bug > Components: Scripting >Affects Versions: Scripting Core 2.4.8 >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler >Priority: Major > Fix For: Scripting Core 2.4.10 > > > In order to show the variable bindings, the webconsole plugin introduced with > SLING-3543 and then refined with SLING-10147 uses a "trick" and actually > invokes Sling via a servlet to get the requested information. > The check in the servlet is only checking if there is a > WebConsoleSecurityProvider2 registered - it is not checking whether it is the > correct one, nor whether that is actually using Sling authentication. > With new features added to the Sling API we can completely remove that > default servlet and let the plugin directly call into Sling. This gives a > "correct" check, removes the unneeded default servlet and reduces the > dependency on the web console. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SLING-11918) GaugeSupport has infinite recursion in registerWithSuffix
[
https://issues.apache.org/jira/browse/SLING-11918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Egli closed SLING-11918.
---
> GaugeSupport has infinite recursion in registerWithSuffix
> -
>
> Key: SLING-11918
> URL: https://issues.apache.org/jira/browse/SLING-11918
> Project: Sling
> Issue Type: Bug
> Components: Event
>Affects Versions: Event 4.3.8
>Reporter: Patrique Legault
>Priority: Critical
> Fix For: Event 4.3.14
>
>
> This exception occurs on a system with an unknown but particular
> configuration but none the less causes the system to become unusable.
>
> {code:java}
> (java.lang.StackOverflowError: Delayed StackOverflowError due to
> ReservedStackAccess annotated method)
> at
> java.base/java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1239)
> at
> java.base/java.util.concurrent.locks.ReentrantReadWriteLock$WriteLock.lock(ReentrantReadWriteLock.java:959)
> at
> java.management/com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:415)
> at
> java.management/com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerWithRepository(DefaultMBeanServerInterceptor.java:1855)
> at
> java.management/com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(DefaultMBeanServerInterceptor.java:955)
> at
> java.management/com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:890)
> at
> java.management/com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:320)
> at
> java.management/com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:522)
> at
> com.codahale.metrics.JmxReporter$JmxListener.registerMBean(JmxReporter.java:510)
> [io.dropwizard.metrics.core:3.2.4]
> at
> com.codahale.metrics.JmxReporter$JmxListener.onGaugeAdded(JmxReporter.java:535)
> [io.dropwizard.metrics.core:3.2.4]
> at
> com.codahale.metrics.MetricRegistry.notifyListenerOfAddedMetric(MetricRegistry.java:454)
> [io.dropwizard.metrics.core:3.2.4]
> at
> com.codahale.metrics.MetricRegistry.onMetricAdded(MetricRegistry.java:448)
> [io.dropwizard.metrics.core:3.2.4]
> at com.codahale.metrics.MetricRegistry.register(MetricRegistry.java:89)
> [io.dropwizard.metrics.core:3.2.4]
> at
> org.apache.sling.event.impl.jobs.stats.GaugeSupport.registerWithSuffix(GaugeSupport.java:150)
> [org.apache.sling.event:4.3.8]
> at
> org.apache.sling.event.impl.jobs.stats.GaugeSupport.registerWithSuffix(GaugeSupport.java:154)
> [org.apache.sling.event:4.3.8] {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[PR] chore(deps): update dependency org.apache.sling:org.apache.sling.event to v4.3.14 [sling-org-apache-sling-starter]
renovate-bot opened a new pull request, #259: URL: https://github.com/apache/sling-org-apache-sling-starter/pull/259 [](https://renovatebot.com) This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [org.apache.sling:org.apache.sling.event](https://sling.apache.org) ([source](https://gitbox.apache.org/repos/asf?p=sling-org-apache-sling-event.git)) | `4.3.12` -> `4.3.14` | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | --- ### Configuration **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://developer.mend.io/github/apache/sling-org-apache-sling-starter). -- 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-12074 : ScriptingVariablesConsolePlugin might use wrong security provider [sling-org-apache-sling-scripting-core]
cziegeler merged PR #26: URL: https://github.com/apache/sling-org-apache-sling-scripting-core/pull/26 -- 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] chore(deps): update dependency org.apache.jackrabbit:oak-api to v1.58.0 [sling-org-apache-sling-starter]
rombert merged PR #258: URL: https://github.com/apache/sling-org-apache-sling-starter/pull/258 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (SLING-12074) ScriptingVariablesConsolePlugin might use wrong security provider
[ https://issues.apache.org/jira/browse/SLING-12074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17775638#comment-17775638 ] Carsten Ziegeler commented on SLING-12074: -- PR in https://github.com/apache/sling-org-apache-sling-scripting-core/pull/26 which uses Sling API for an internal request. This avoids checking for a WebConsoleSecurityProvider2 (which was buggy anyway) and a default servlet being registered just for the console > ScriptingVariablesConsolePlugin might use wrong security provider > - > > Key: SLING-12074 > URL: https://issues.apache.org/jira/browse/SLING-12074 > Project: Sling > Issue Type: Bug > Components: Scripting >Affects Versions: Scripting Core 2.4.8 >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler >Priority: Major > Fix For: Scripting Core 2.4.10 > > > In order to show the variable bindings, the webconsole plugin introduced with > SLING-3543 and then refined with SLING-10147 uses a "trick" and actually > invokes Sling via a servlet to get the requested information. > The check in the servlet is only checking if there is a > WebConsoleSecurityProvider2 registered - it is not checking whether it is the > correct one, nor whether that is actually using Sling authentication. > With new features added to the Sling API we can completely remove that > default servlet and let the plugin directly call into Sling. This gives a > "correct" check, removes the unneeded default servlet and reduces the > dependency on the web console. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] SLING-12070: migrate to jakarta.json [sling-org-apache-sling-xss]
rombert commented on PR #35: URL: https://github.com/apache/sling-org-apache-sling-xss/pull/35#issuecomment-1764092377 @apelluru - yes, fallout from https://issues.apache.org/jira/browse/INFRA-25083, should be fixed now. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] SLING-12074 : ScriptingVariablesConsolePlugin might use wrong security provider [sling-org-apache-sling-scripting-core]
cziegeler opened a new pull request, #26: URL: https://github.com/apache/sling-org-apache-sling-scripting-core/pull/26 (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] ScriptingVariablesConsolePlugin might use wrong security provider [sling-org-apache-sling-scripting-core]
cziegeler closed pull request #24: ScriptingVariablesConsolePlugin might use wrong security provider URL: https://github.com/apache/sling-org-apache-sling-scripting-core/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
[RESULT][Vote] Release Apache Sling Event 4.3.14
|Hi, The vote has passed with the following result : +1 (binding): Carsten Ziegeler, Robert Munteanu, Daniel Klco and Andrei Dulvac +1 (non binding): none I will copy this release to the Sling dist directory and promote the artifacts to the central Maven repository. Cheers, Stefan | On 09.10.23 13:27, Stefan Egli wrote: Hi, We solved 3 issues in this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12353217 ** Bug * [SLING-11918] - GaugeSupport has infinite recursion in registerWithSuffix * [SLING-11923] - Sling Events does not Build on Java 17 ** Improvement * [SLING-11900] - Provide alternative terminology for inequitable terms Staging repository: https://repository.apache.org/content/repositories/orgapachesling-2793/ 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 2793 /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. Cheers, Stefan
[jira] [Resolved] (SLING-12098) Update Testing PaxExam to 4.0.0
[ https://issues.apache.org/jira/browse/SLING-12098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-12098. -- Resolution: Fixed Thanks [~olli] ! I've disabled the failing test for now, will be fixed with SLING-12074 > Update Testing PaxExam to 4.0.0 > --- > > Key: SLING-12098 > URL: https://issues.apache.org/jira/browse/SLING-12098 > Project: Sling > Issue Type: Sub-task > Components: Scripting >Reporter: Carsten Ziegeler >Priority: Major > Fix For: Scripting Core 2.4.10 > > > In order to make it easier to work on this module, we should update to the > latest testing paxeam 4.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] Migrate to Sling Testing paxexam 4.0 [sling-org-apache-sling-scripting-core]
cziegeler merged PR #25: URL: https://github.com/apache/sling-org-apache-sling-scripting-core/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
[jira] [Commented] (SLING-12098) Update Testing PaxExam to 4.0.0
[
https://issues.apache.org/jira/browse/SLING-12098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17775615#comment-17775615
]
Oliver Lietz commented on SLING-12098:
--
[~cziegeler], fixed in
[3f43dfe|https://github.com/apache/sling-org-apache-sling-scripting-core/commit/3f43dfe32083e3602b4cd35f337a8679b0b7d210].
{noformat}
[INFO] Running org.apache.sling.scripting.core.it.HtmlScriptingIT
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 13.524 s
- in org.apache.sling.scripting.core.it.HtmlScriptingIT
[INFO]
[INFO] Results:
[INFO]
[ERROR] Failures:
[ERROR]
SLING_10147IT$HasNoWebConsoleSecurityProvider2IT.testGetSlingBindingsVariablesListJsonWithoutWebConsoleSecurityProvider2:319
expected:<403> but was:<200>
[ERROR]
SLING_10147IT$NotAuthorizedIT.testGetSlingBindingsVariablesListJsonWithNotAuthorizedUser:261
expected:<403> but was:<500>
[INFO]
[ERROR] Tests run: 17, Failures: 2, Errors: 0, Skipped: 0
{noformat}
> Update Testing PaxExam to 4.0.0
> ---
>
> Key: SLING-12098
> URL: https://issues.apache.org/jira/browse/SLING-12098
> Project: Sling
> Issue Type: Sub-task
> Components: Scripting
>Reporter: Carsten Ziegeler
>Priority: Major
> Fix For: Scripting Core 2.4.10
>
>
> In order to make it easier to work on this module, we should update to the
> latest testing paxeam 4.0
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (SLING-12098) Update Testing PaxExam to 4.0.0
[ https://issues.apache.org/jira/browse/SLING-12098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz updated SLING-12098: - Parent: SLING-11472 Issue Type: Sub-task (was: Improvement) > Update Testing PaxExam to 4.0.0 > --- > > Key: SLING-12098 > URL: https://issues.apache.org/jira/browse/SLING-12098 > Project: Sling > Issue Type: Sub-task > Components: Scripting >Reporter: Carsten Ziegeler >Priority: Major > Fix For: Scripting Core 2.4.10 > > > In order to make it easier to work on this module, we should update to the > latest testing paxeam 4.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SLING-12098) Update Testing PaxExam to 4.0.0
[ https://issues.apache.org/jira/browse/SLING-12098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oliver Lietz updated SLING-12098: - Summary: Update Testing PaxExam to 4.0.0 (was: Update to Sling Testing Pax 4.0) > Update Testing PaxExam to 4.0.0 > --- > > Key: SLING-12098 > URL: https://issues.apache.org/jira/browse/SLING-12098 > Project: Sling > Issue Type: Improvement > Components: Scripting >Reporter: Carsten Ziegeler >Priority: Major > Fix For: Scripting Core 2.4.10 > > > In order to make it easier to work on this module, we should update to the > latest testing paxeam 4.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] chore(deps): update dependency org.apache.jackrabbit:oak-api to v1.58.0 [sling-org-apache-sling-starter]
renovate-bot opened a new pull request, #258: URL: https://github.com/apache/sling-org-apache-sling-starter/pull/258 [](https://renovatebot.com) This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [org.apache.jackrabbit:oak-api](http://jackrabbit.apache.org/) | `1.56.0` -> `1.58.0` | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | --- ### Configuration **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://developer.mend.io/github/apache/sling-org-apache-sling-starter). -- 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-12070: migrate to jakarta.json [sling-org-apache-sling-xss]
apelluru commented on PR #35: URL: https://github.com/apache/sling-org-apache-sling-xss/pull/35#issuecomment-1763927764 > LGTM, thanks. Hi @rombert Is it known issue? https://ci-builds.apache.org/job/Sling/job/modules/job/sling-org-apache-sling-xss/job/master/218/console ```[Pipeline] isUnix [Pipeline] sh + mvn -U -B -e clean compile /home/jenkins/jenkins-agent/workspace/ling-org-apache-sling-xss_master@tmp/durable-378778c7/script.sh: 1: /home/jenkins/jenkins-agent/workspace/ling-org-apache-sling-xss_master@tmp/durable-378778c7/script.sh: mvn: not found [Pipeline] } [Pipeline] // withMaven``` -- 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-12070) Migrate sling.xss to jakarta.json
[ https://issues.apache.org/jira/browse/SLING-12070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashok Pelluru resolved SLING-12070. --- Resolution: Fixed > Migrate sling.xss to jakarta.json > - > > Key: SLING-12070 > URL: https://issues.apache.org/jira/browse/SLING-12070 > Project: Sling > Issue Type: Sub-task >Reporter: Ashok Pelluru >Assignee: Ashok Pelluru >Priority: Minor > Fix For: XSS Protection API 2.3.10 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SLING-12070) Migrate sling.xss to jakarta.json
[ https://issues.apache.org/jira/browse/SLING-12070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashok Pelluru updated SLING-12070: -- Fix Version/s: XSS Protection API 2.3.10 > Migrate sling.xss to jakarta.json > - > > Key: SLING-12070 > URL: https://issues.apache.org/jira/browse/SLING-12070 > Project: Sling > Issue Type: Sub-task >Reporter: Ashok Pelluru >Assignee: Ashok Pelluru >Priority: Minor > Fix For: XSS Protection API 2.3.10 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] SLING-12070: migrate to jakarta.json [sling-org-apache-sling-xss]
apelluru merged PR #35: URL: https://github.com/apache/sling-org-apache-sling-xss/pull/35 -- 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
[Jenkins] Sling » Modules » sling-org-apache-sling-starter » master #1082 is BROKEN
Please see
https://ci-builds.apache.org/job/Sling/job/modules/job/sling-org-apache-sling-starter/job/master/1082/
for details.
No further emails will be sent until the status of the build is changed.
Build log follows below:
Push event to branch master
Connecting to https://api.github.com using Personal access token for Github
repository access. Use with Apache Sling jobs only.
Obtained Jenkinsfile from 60b8977b6919dd1bbbdb9c31175c7af48261f7b8
Loading library sling@master
Examining apache/sling-tooling-jenkins
Attempting to resolve master as a branch
Resolved master as branch master at revision
77cc9bce6d10c2f40323721f37b098990f666b90
The recommended git tool is: NONE
using credential sling-github-token
> git rev-parse --resolve-git-dir
> /home/jenkins/jenkins-home/workspace/_org-apache-sling-starter_master@libs/49d08ddfb93f639f0f78b5baa5d40a7562d5f564b88912f54ee7352d957a47e1/.git
> # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url
> https://github.com/apache/sling-tooling-jenkins.git # timeout=10
Fetching without tags
Fetching upstream changes from
https://github.com/apache/sling-tooling-jenkins.git
> git --version # timeout=10
> git --version # 'git version 2.25.1'
using GIT_ASKPASS to set credentials Personal access token for Github
repository access. Use with Apache Sling jobs only.
> git fetch --no-tags --force --progress --
> https://github.com/apache/sling-tooling-jenkins.git
> +refs/heads/master:refs/remotes/origin/master # timeout=10
Checking out Revision 77cc9bce6d10c2f40323721f37b098990f666b90 (master)
> git config core.sparsecheckout # timeout=10
> git checkout -f 77cc9bce6d10c2f40323721f37b098990f666b90 # timeout=10
Commit message: "SLING-12006 Run Sonar analysis with Java 17 (#18)"
> git rev-list --no-walk 77cc9bce6d10c2f40323721f37b098990f666b90 # timeout=10
[Pipeline] Start of Pipeline
[Pipeline] node
Running on builds30 in
/home/jenkins/jenkins-agent/workspace/_org-apache-sling-starter_master
[Pipeline] {
[Pipeline] timeout
Timeout set to expire in 5 min 0 sec
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Init)
[Pipeline] checkout
The recommended git tool is: NONE
using credential sling-github-token
Fetching changes from the remote Git repository
Fetching without tags
> git rev-parse --resolve-git-dir
> /home/jenkins/jenkins-agent/workspace/_org-apache-sling-starter_master/.git
> # timeout=10
> git config remote.origin.url
> https://github.com/apache/sling-org-apache-sling-starter.git # timeout=10
Fetching upstream changes from
https://github.com/apache/sling-org-apache-sling-starter.git
> git --version # timeout=10
> git --version # 'git version 2.17.1'
using GIT_ASKPASS to set credentials Personal access token for Github
repository access. Use with Apache Sling jobs only.
> git fetch --no-tags --progress --
> https://github.com/apache/sling-org-apache-sling-starter.git
> +refs/heads/master:refs/remotes/origin/master # timeout=10
Checking out Revision 60b8977b6919dd1bbbdb9c31175c7af48261f7b8 (master)
Commit message: "chore(deps): update dependency
org.apache.sling:org.apache.sling.commons.mime to v2.2.4 (#256)"
> git config core.sparsecheckout # timeout=10
> git checkout -f 60b8977b6919dd1bbbdb9c31175c7af48261f7b8 # timeout=10
> git rev-list --no-walk fee1c6a58414e8f52ae1a585d1c6ef422e307542 # timeout=10
Cleaning workspace
> git rev-parse --verify HEAD # timeout=10
Resetting working tree
> git reset --hard # timeout=10
> git clean -fdx # timeout=10
[Pipeline] isUnix
[Pipeline] sh
+ git clean -fdx
Skipping repository jdk_1.8_latest/
Skipping repository jdk_11_latest/
Skipping repository jdk_17_latest/
Skipping repository jdk_21_latest/
[Pipeline] sh
+ git config remote.origin.url
[Pipeline] fileExists
[Pipeline] readJSON
[Pipeline] echo
Jenkins overrides: [emailRecipients:[dev@sling.apache.org],
sonarQubeEnabled:false, jdks:[11, 17, 21], operatingSystems:[linux],
rebuildFrequency:@daily, additionalMavenParams:-Dit.startTimeoutSeconds=120,
archivePatterns:[**/logs/*.log]]
[Pipeline] echo
Final job config: [jdks:[11, 17, 21], operatingSystems:[linux],
upstreamProjects:[], archivePatterns:[**/logs/*.log], mavenGoal:,
additionalMavenParams:-Dit.startTimeoutSeconds=120, rebuildFrequency:@daily,
enabled:true, emailRecipients:[dev@sling.apache.org], sonarQubeEnabled:false,
sonarQubeUseAdditionalMavenParams:true, sonarQubeAdditionalParams:,
repoName:sling-org-apache-sling-starter]
[Pipeline] readMavenPom
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // timeout
[Pipeline] }
[Pipeline] // node
[Pipeline] node
Running on builds30 in
/home/jenkins/jenkins-agent/workspace/_org-apache-sling-starter_master
[Pipeline] {
[Pipeline] timeout
Timeout set to expire after 30 min without activity
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Configure Job)
[Pipeline] properties
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // timeout
[Pipeline] }
[Pipeline] // node
[Pipeline] echo
Using
Re: [PR] chore(deps): update dependency org.apache.sling:org.apache.sling.commons.mime to v2.2.4 [sling-org-apache-sling-starter]
rombert merged PR #256: URL: https://github.com/apache/sling-org-apache-sling-starter/pull/256 -- 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-12101 - Remove Guava from the Starter [sling-org-apache-sling-starter]
rombert commented on PR #257: URL: https://github.com/apache/sling-org-apache-sling-starter/pull/257#issuecomment-1763887402 Looks like a Jenkins config problem, will retry later ``` + mvn -U -B -e clean compile -Dit.startTimeoutSeconds=120 /home/jenkins/jenkins-agent/workspace/_org-apache-sling-starter_PR-257@tmp/durable-c3b4c0a0/script.sh: 1: /home/jenkins/jenkins-agent/workspace/_org-apache-sling-starter_PR-257@tmp/durable-c3b4c0a0/script.sh: mvn: not found ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] SLING-12101 - Remove Guava from the Starter [sling-org-apache-sling-starter]
rombert opened a new pull request, #257: URL: https://github.com/apache/sling-org-apache-sling-starter/pull/257 Remove the bundle from the Starter and drop the no longer needed Renovate config. Oak now uses its own private copy of Guava. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (SLING-12101) Remove Guava from the Starter
[ https://issues.apache.org/jira/browse/SLING-12101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-12101: Labels: Sling-13-Release-Notes (was: ) > Remove Guava from the Starter > - > > Key: SLING-12101 > URL: https://issues.apache.org/jira/browse/SLING-12101 > Project: Sling > Issue Type: Improvement > Components: Starter >Reporter: Robert Munteanu >Assignee: Robert Munteanu >Priority: Major > Labels: Sling-13-Release-Notes > Fix For: Starter 13 > > > With the latest changes to Oak, Sling Oak Server and Sling JCR Maintenance we > no longer need to include Guava in the Sling Starter. > We should drop it since it is unused and allow consumers to deploy any > version they need. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (SLING-12101) Remove Guava from the Starter
Robert Munteanu created SLING-12101: --- Summary: Remove Guava from the Starter Key: SLING-12101 URL: https://issues.apache.org/jira/browse/SLING-12101 Project: Sling Issue Type: Improvement Components: Starter Reporter: Robert Munteanu Assignee: Robert Munteanu Fix For: Starter 13 With the latest changes to Oak, Sling Oak Server and Sling JCR Maintenance we no longer need to include Guava in the Sling Starter. We should drop it since it is unused and allow consumers to deploy any version they need. -- This message was sent by Atlassian Jira (v8.20.10#820010)
