[GitHub] [sling-org-apache-sling-testing-osgi-mock] adamcin commented on pull request #31: SLING-12038 add support for reified OSGi config annotations as test parameters
adamcin commented on PR #31: URL: https://github.com/apache/sling-org-apache-sling-testing-osgi-mock/pull/31#issuecomment-1734778670 @rombert can you review this as well, please? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [VOTE] Release Apache Sling Commons Prometheus Metrics Exporter 0.1.0
+1 On Sun, Sep 24, 2023 at 2:13 PM Robert Munteanu wrote: > Hi, > > We solved 1 issue in this release: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310710&version=12353664&styleName=Text > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-2788/ > > 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 2788 /tmp/sling-staging > > Please vote to approve this release: > > [ ] +1 Approve the release > [ ] 0 Don't care > [ ] -1 Don't release, because ... > > This majority vote is open for at least 72 hours. > > Regards, > Robert Munteanu >
[GitHub] [sling-org-apache-sling-testing-osgi-mock] sonarcloud[bot] commented on pull request #31: SLING-12038 add support for reified OSGi config annotations as test parameters
sonarcloud[bot] commented on PR #31: URL: https://github.com/apache/sling-org-apache-sling-testing-osgi-mock/pull/31#issuecomment-1734674688 Kudos, SonarCloud Quality Gate passed! [](https://sonarcloud.io/dashboard?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=BUG) [0 Bugs](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=VULNERABILITY) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=VULNERABILITY) [0 Vulnerabilities](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=VULNERABILITY) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=SECURITY_HOTSPOT) [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=CODE_SMELL) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=CODE_SMELL) [3 Code Smells](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=CODE_SMELL) [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&metric=new_coverage&view=list) [100.0% Coverage](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&metric=new_coverage&view=list) [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&metric=new_duplicated_lines_density&view=list) [0.0% Duplication](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&metric=new_duplicated_lines_density&view=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] [Commented] (SLING-12027) GraphQL core fails to build with Java 17
[ https://issues.apache.org/jira/browse/SLING-12027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17768921#comment-17768921 ] Andreas Schaefer commented on SLING-12027: -- [~radu] Does not do the trick. I upgraded to the latest Engine, Servlets Resolver and some more and it still breaks the same way. It actually makes it even rose because now additional IT tests fail. > GraphQL core fails to build with Java 17 > > > Key: SLING-12027 > URL: https://issues.apache.org/jira/browse/SLING-12027 > Project: Sling > Issue Type: Bug > Components: GraphQL >Reporter: Robert Munteanu >Assignee: Robert Munteanu >Priority: Major > Fix For: GraphQL Core 0.0.26 > > > 1. Mockito fails to create mocks, probably due to old version > 2. Pax-Exam tests time out -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [sling-org-apache-sling-jcr-maintenance] klcodanr closed pull request #4: SLING-12035: Using a permissive version range for org.apache.jackrabbit.oak.commons.jmx to enable update to latest Oa
klcodanr closed pull request #4: SLING-12035: Using a permissive version range for org.apache.jackrabbit.oak.commons.jmx to enable update to latest Oak version URL: https://github.com/apache/sling-org-apache-sling-jcr-maintenance/pull/4 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [sling-org-apache-sling-jcr-maintenance] klcodanr commented on pull request #4: SLING-12035: Using a permissive version range for org.apache.jackrabbit.oak.commons.jmx to enable update to lat
klcodanr commented on PR #4: URL: https://github.com/apache/sling-org-apache-sling-jcr-maintenance/pull/4#issuecomment-1734438976 Agh! Sorry @enapps-enorman! My bad as well, I should have looked to see if there was another relevant PR. Closing this issue since your fix seems better. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [sling-org-apache-sling-testing-osgi-mock] sonarcloud[bot] commented on pull request #31: SLING-12038 add support for reified OSGi config annotations as test parameters
sonarcloud[bot] commented on PR #31: URL: https://github.com/apache/sling-org-apache-sling-testing-osgi-mock/pull/31#issuecomment-1734381705 Kudos, SonarCloud Quality Gate passed! [](https://sonarcloud.io/dashboard?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=BUG) [0 Bugs](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=VULNERABILITY) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=VULNERABILITY) [0 Vulnerabilities](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=VULNERABILITY) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=SECURITY_HOTSPOT) [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=CODE_SMELL) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=CODE_SMELL) [10 Code Smells](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=CODE_SMELL) [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&metric=new_coverage&view=list) [100.0% Coverage](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&metric=new_coverage&view=list) [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&metric=new_duplicated_lines_density&view=list) [0.0% Duplication](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&metric=new_duplicated_lines_density&view=list) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [sling-org-apache-sling-jcr-maintenance] rombert commented on pull request #4: SLING-12035: Using a permissive version range for org.apache.jackrabbit.oak.commons.jmx to enable update to late
rombert commented on PR #4: URL: https://github.com/apache/sling-org-apache-sling-jcr-maintenance/pull/4#issuecomment-1734337223 > @klcodanr @rombert Are my pull requests and jira records invisible to you guys? I already worked on this for #3 and was tracking it with [SLING-12034](https://issues.apache.org/jira/browse/SLING-12034) > > It's super annonying to see no feedback for my PR and then you start an another one to solve the same problem. @enapps-enorman - oh, sorry, I did not see your PR. I am subscribed to all Jira issues and GitHub PRs, but somehow I managed to miss this one. Absolutely no intention to ignore your work, your contributions to Sling are very much appreciated. I only pinged @klcodanr on the Starter issue, without looking at the PRs, because I knew he contributed that module. I am of course fine and would encourage you to merge your PR since it solves the problem that we have. On the topic of reviews - I personally try to review contributions from non-committers with priority and assume that if no feedback is explicitly requested for a PR we are working in a 'lazy consensus' mode. But if you prefer a second pair of eyes on the review please @-mention me or add me as a reviewer and I'd be happy to review. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [sling-org-apache-sling-jcr-maintenance] enapps-enorman commented on pull request #4: SLING-12035: Using a permissive version range for org.apache.jackrabbit.oak.commons.jmx to enable update
enapps-enorman commented on PR #4: URL: https://github.com/apache/sling-org-apache-sling-jcr-maintenance/pull/4#issuecomment-1734305470 @klcodanr @rombert Are my pull requests and jira records invisible to you guys? I already worked on this for https://github.com/apache/sling-org-apache-sling-jcr-maintenance/pull/3 and was tracking it with SLING-12034 It's super annonying to see no feedback for my PR and then you start an another one to solve the same problem. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [sling-org-apache-sling-starter] klcodanr commented on pull request #221: chore(deps): update apache jackrabbit and jackrabbit oak
klcodanr commented on PR #221: URL: https://github.com/apache/sling-org-apache-sling-starter/pull/221#issuecomment-1734276769 @rombert looks like an easy fix: https://github.com/apache/sling-org-apache-sling-jcr-maintenance/pull/4 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [sling-org-apache-sling-jcr-maintenance] klcodanr opened a new pull request, #4: SLING-12035: Using a permissive version range for org.apache.jackrabbit.oak.commons.jmx to enable update to la
klcodanr opened a new pull request, #4: URL: https://github.com/apache/sling-org-apache-sling-jcr-maintenance/pull/4 Using a permissive version range for org.apache.jackrabbit.oak.commons.jmx to enable update to latest Oak version Tested by: - building snapshot of this bundle - applying the changes here: https://github.com/apache/sling-org-apache-sling-starter/pull/221/files and updating to use this bundle's snapshot version to starter - Running `mvn clean install` and verifying it failed with a message about the version range for `org.apache.jackrabbit.oak.commons.jmx` - Applying the change in this PR - building snapshot of this bundle - Running `mvn clean install` and verifying that the error message for this bundle no longer appeared -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [sling-org-apache-sling-testing-osgi-mock] adamcin commented on pull request #31: SLING-12038 add support for reified OSGi config annotations as test parameters
adamcin commented on PR #31: URL: https://github.com/apache/sling-org-apache-sling-testing-osgi-mock/pull/31#issuecomment-1734265467 @klcodanr Could I trouble you for a review? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [sling-org-apache-sling-testing-osgi-mock] sonarcloud[bot] commented on pull request #31: SLING-12038 add support for reified OSGi config annotations as test parameters
sonarcloud[bot] commented on PR #31: URL: https://github.com/apache/sling-org-apache-sling-testing-osgi-mock/pull/31#issuecomment-1734258999 Kudos, SonarCloud Quality Gate passed! [](https://sonarcloud.io/dashboard?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=BUG) [0 Bugs](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=VULNERABILITY) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=VULNERABILITY) [0 Vulnerabilities](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=VULNERABILITY) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=SECURITY_HOTSPOT) [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=CODE_SMELL) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=CODE_SMELL) [10 Code Smells](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=CODE_SMELL) [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&metric=new_coverage&view=list) [100.0% Coverage](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&metric=new_coverage&view=list) [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&metric=new_duplicated_lines_density&view=list) [0.0% Duplication](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&metric=new_duplicated_lines_density&view=list) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [sling-org-apache-sling-testing-osgi-mock] sonarcloud[bot] commented on pull request #31: SLING-12038 add support for reified OSGi config annotations as test parameters
sonarcloud[bot] commented on PR #31: URL: https://github.com/apache/sling-org-apache-sling-testing-osgi-mock/pull/31#issuecomment-1734248702 Kudos, SonarCloud Quality Gate passed! [](https://sonarcloud.io/dashboard?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=BUG) [0 Bugs](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=VULNERABILITY) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=VULNERABILITY) [0 Vulnerabilities](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=VULNERABILITY) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=SECURITY_HOTSPOT) [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=CODE_SMELL) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=CODE_SMELL) [10 Code Smells](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=CODE_SMELL) [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&metric=new_coverage&view=list) [99.8% Coverage](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&metric=new_coverage&view=list) [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&metric=new_duplicated_lines_density&view=list) [0.0% Duplication](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&metric=new_duplicated_lines_density&view=list) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [sling-org-apache-sling-testing-osgi-mock] sonarcloud[bot] commented on pull request #31: SLING-12038 add support for reified OSGi config annotations as test parameters
sonarcloud[bot] commented on PR #31: URL: https://github.com/apache/sling-org-apache-sling-testing-osgi-mock/pull/31#issuecomment-1734217287 Kudos, SonarCloud Quality Gate passed! [](https://sonarcloud.io/dashboard?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=BUG) [0 Bugs](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=VULNERABILITY) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=VULNERABILITY) [0 Vulnerabilities](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=VULNERABILITY) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=SECURITY_HOTSPOT) [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=CODE_SMELL) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=CODE_SMELL) [10 Code Smells](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=CODE_SMELL) [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&metric=new_coverage&view=list) [99.6% Coverage](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&metric=new_coverage&view=list) [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&metric=new_duplicated_lines_density&view=list) [0.0% Duplication](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&metric=new_duplicated_lines_density&view=list) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [sling-org-apache-sling-testing-osgi-mock] sonarcloud[bot] commented on pull request #31: SLING-12038 add support for reified OSGi config annotations as test parameters
sonarcloud[bot] commented on PR #31: URL: https://github.com/apache/sling-org-apache-sling-testing-osgi-mock/pull/31#issuecomment-1734080284 Kudos, SonarCloud Quality Gate passed! [](https://sonarcloud.io/dashboard?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=BUG) [0 Bugs](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=VULNERABILITY) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=VULNERABILITY) [0 Vulnerabilities](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=VULNERABILITY) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=SECURITY_HOTSPOT) [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=CODE_SMELL) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=CODE_SMELL) [6 Code Smells](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=CODE_SMELL) [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&metric=new_coverage&view=list) [99.8% Coverage](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&metric=new_coverage&view=list) [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&metric=new_duplicated_lines_density&view=list) [0.0% Duplication](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&metric=new_duplicated_lines_density&view=list) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [sling-org-apache-sling-testing-osgi-mock] sonarcloud[bot] commented on pull request #31: SLING-12038 add support for reified OSGi config annotations as test parameters
sonarcloud[bot] commented on PR #31: URL: https://github.com/apache/sling-org-apache-sling-testing-osgi-mock/pull/31#issuecomment-1734069500 Kudos, SonarCloud Quality Gate passed! [](https://sonarcloud.io/dashboard?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=BUG) [0 Bugs](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=BUG) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=VULNERABILITY) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=VULNERABILITY) [0 Vulnerabilities](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=VULNERABILITY) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=SECURITY_HOTSPOT) [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=SECURITY_HOTSPOT) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=CODE_SMELL) [](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=CODE_SMELL) [6 Code Smells](https://sonarcloud.io/project/issues?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&resolved=false&types=CODE_SMELL) [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&metric=new_coverage&view=list) [99.8% Coverage](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&metric=new_coverage&view=list) [](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&metric=new_duplicated_lines_density&view=list) [0.0% Duplication](https://sonarcloud.io/component_measures?id=apache_sling-org-apache-sling-testing-osgi-mock&pullRequest=31&metric=new_duplicated_lines_density&view=list) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [sling-org-apache-sling-starter] rombert commented on pull request #147: chore(deps): update apache felix http (major)
rombert commented on PR #147: URL: https://github.com/apache/sling-org-apache-sling-starter/pull/147#issuecomment-1733989827 We have some fallout regarding error handling, so 50 tests are failing with `expected:<404> but was:<500>` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [sling-org-apache-sling-starter] rombert merged pull request #213: chore(deps): update apache felix http
rombert merged PR #213: URL: https://github.com/apache/sling-org-apache-sling-starter/pull/213 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [sling-org-apache-sling-starter] rombert commented on pull request #213: chore(deps): update apache felix http
rombert commented on PR #213: URL: https://github.com/apache/sling-org-apache-sling-starter/pull/213#issuecomment-1733962381 That fixed it, thanks for the hint @cziegeler ! -- 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-12027) GraphQL core fails to build with Java 17
[ https://issues.apache.org/jira/browse/SLING-12027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17768749#comment-17768749 ] Radu Cotescu commented on SLING-12027: -- [~andysch], could it be that the tests are running with relatively old Sling Engine and Sling Servlet Resolver bundles? Have you tried updating those? > GraphQL core fails to build with Java 17 > > > Key: SLING-12027 > URL: https://issues.apache.org/jira/browse/SLING-12027 > Project: Sling > Issue Type: Bug > Components: GraphQL >Reporter: Robert Munteanu >Assignee: Robert Munteanu >Priority: Major > Fix For: GraphQL Core 0.0.26 > > > 1. Mockito fails to create mocks, probably due to old version > 2. Pax-Exam tests time out -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (SLING-12027) GraphQL core fails to build with Java 17
[ https://issues.apache.org/jira/browse/SLING-12027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17768746#comment-17768746 ] Robert Munteanu commented on SLING-12027: - Thanks for looking in-depth [~andysch]. I am afraid I can't help any longer right now, but maybe someone with both core Sling and GraphQL knowledge, like [~radu] or [~bdelacretaz], can help. > GraphQL core fails to build with Java 17 > > > Key: SLING-12027 > URL: https://issues.apache.org/jira/browse/SLING-12027 > Project: Sling > Issue Type: Bug > Components: GraphQL >Reporter: Robert Munteanu >Assignee: Robert Munteanu >Priority: Major > Fix For: GraphQL Core 0.0.26 > > > 1. Mockito fails to create mocks, probably due to old version > 2. Pax-Exam tests time out -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (SLING-10000) Switch to Jakarta APIs
[
https://issues.apache.org/jira/browse/SLING-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17768741#comment-17768741
]
Carsten Ziegeler commented on SLING-1:
--
There are many details on this - we also should separate between updating the
Servlet api and any other api - the servlet API is special as that is the one
we are using in our APIs. Every other API is most likely less complicated.
Now, when it comes to the servlet API, Apache Felix Http Jetty 5.x is based on
Jetty 11 and it supports jakarta servlet 5 and javax servlet 3. So that version
is one way to start support Jakarta Servlet API.
But as we are using the javax servlet api in our Sling API, it is way more
difficult. We can't simply make a major version change for all Sling API as
this would break all current users. The Apache Felix Webconsole had a similar
problem. There we established a *new* API using Jakarta servlet next to the
existing one. The latest webconsole supports both APIs. But again, for Sling
this would have a way larger impact.
> Switch to Jakarta APIs
> --
>
> Key: SLING-1
> URL: https://issues.apache.org/jira/browse/SLING-1
> Project: Sling
> Issue Type: Task
> Components: API
>Reporter: Oliver Lietz
>Priority: Major
>
> Java EE APIs are switching from {{javax}} to {{jakarta}}.
> Jakarta Specifications: [https://jakarta.ee/specifications/]
> *Candidates*
> * {{javax.activation}}
> * {{javax.servlet}}
> * {{javax.mail}}
> *Discovery*
> * Should we have branch {{jakarta}} in each module which needs to switch?
> * Should we use the breaking change (major version increase in most APIs) to
> clean up and improve our current API or limit it to the package switch?
> *Tooling*
> * [Eclipse Transformer|https://github.com/eclipse/transformer]
> * [Tomcat Migration Tool for Jakarta EE
> software|https://tomcat.apache.org/download-migration.cgi]
> * [JetBrains IntelliJ IDEA – Automatic migration from Java EE to Jakarta
> EE|https://blog.jetbrains.com/idea/2021/06/intellij-idea-eap-6/#automatic_migration_from_java_ee_to_jakarta_ee]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [VOTE] Release Apache Sling org.apache.sling.distribution.journal.messages 0.5.4, org.apache.sling.distribution.journal 0.2.0
Hi, The vote has passed with the following result: +1 (binding): Christian Schneider, Timothé Maret, Jörg Hoh +1 (non-binding): none I will copy this release to the Sling dist directory and promote the artifacts to the central Maven repository. Regards, Christian Am Fr., 22. Sept. 2023 um 14:37 Uhr schrieb Christian Schneider < ch...@die-schneider.net>: > Release Notes - Sling - Version Content Distribution Journal Messages 0.5.4 > ** Improvement > * [SLING-11255] - Update to parent bundle 47 > * [SLING-11914] - Accept initial offset via OffsetMessage > > https://issues.apache.org/jira/projects/SLING/versions/12351666 > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-2785 > > Release Notes - Sling - Version Content Distribution Journal Core 0.2.0 > ** Bug > * [SLING-9321] - Update to declarative services 1.4 > * [SLING-9403] - Filter status messages by subscriber agent > * [SLING-11560] - Vault error when importing a node with the same name > and UUID as a pre-existing non-sibling node > * [SLING-11809] - Disable "overwritePrimaryTypesOfFolders" in the > distribution journal > * [SLING-11990] - Fix TEST distribution requests > ** Improvement > * [SLING-11365] - Improve the exception handling of the > DistributionPublisher.execute > * [SLING-11607] - Emit metric on the time that a package spends in the > journal > * [SLING-11914] - Accept initial offset via OffsetMessage > * [SLING-11986] - Bundle relies on Guava (15) > > https://issues.apache.org/jira/projects/SLING/versions/12351663 > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-2786/ > > 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 [YOUR REPOSITORY ID] /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. > > Christian Schneider > > -- -- Christian Schneider http://www.liquid-reality.de Computer Scientist http://www.adobe.com
[GitHub] [sling-org-apache-sling-starter] cziegeler commented on pull request #213: chore(deps): update apache felix http
cziegeler commented on PR #213: URL: https://github.com/apache/sling-org-apache-sling-starter/pull/213#issuecomment-1733913384 @rombert Yes, this is unfortunately a known problem - the jetty update brings in a bug fix and unfortunately the web console depends on that bug. you need to update the webconsole to 4.9.4 at the same time -- 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-10405) Update embedded jackrabbit vault to version 3.5.0
[ https://issues.apache.org/jira/browse/SLING-10405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17768723#comment-17768723 ] Konrad Windszus commented on SLING-10405: - Alternatively the release notes of all versions are maintained at https://github.com/apache/jackrabbit-filevault/blob/master/RELEASE-NOTES.txt. > Update embedded jackrabbit vault to version 3.5.0 > - > > Key: SLING-10405 > URL: https://issues.apache.org/jira/browse/SLING-10405 > Project: Sling > Issue Type: Improvement > Components: Feature Model >Affects Versions: Feature Model Content Extension 1.0.10 >Reporter: Karl Pauls >Assignee: Konrad Windszus >Priority: Major > Fix For: Feature Model Content Extension 1.0.12 > > > The extension currently uses (and embeds) an old version of vault - namely, > 3.2.6. We should update to a newer version. > https://github.com/apache/sling-org-apache-sling-feature-extension-content/blob/master/pom.xml#L104 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SLING-12032) Slf4j classes included and not relocated in the final jar
[
https://issues.apache.org/jira/browse/SLING-12032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu closed SLING-12032.
---
> Slf4j classes included and not relocated in the final jar
> -
>
> Key: SLING-12032
> URL: https://issues.apache.org/jira/browse/SLING-12032
> Project: Sling
> Issue Type: Bug
> Components: Feature Model
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>Priority: Major
> Fix For: Feature Model Content Extension 1.0.12
>
>
> For some reason the following jars are pulled in and not relocated
> {noformat}
> [INFO] Including org.slf4j:slf4j-api:jar:1.7.25 in the shaded jar.
> [INFO] Including org.slf4j:jcl-over-slf4j:jar:1.7.25 in the shaded jar.
> {noformat}
> This can lead to classpath conflicts and must be avoided. Relocating might
> work, but right now I don't see a good reason for shipping a copy of the
> slf4j so we should just filter out these packages.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (SLING-12030) Invalid class name when trying to execute extension
[
https://issues.apache.org/jira/browse/SLING-12030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu closed SLING-12030.
---
> Invalid class name when trying to execute extension
>
>
> Key: SLING-12030
> URL: https://issues.apache.org/jira/browse/SLING-12030
> Project: Sling
> Issue Type: Bug
> Components: Feature Model
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>Priority: Major
> Fix For: Feature Model Content Extension 1.0.12
>
>
> When trying to run a the latest master version I get the following error
> {noformat}ception in thread "Thread-39" java.lang.ClassFormatError: Illegal
> class name "relocated-for-contentpackage/javax/jcr/RepositoryException" in
> class file relocated-for-contentpackage/javax/jcr/RepositoryException
> at java.base/java.lang.ClassLoader.defineClass1(Native Method)
> at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1022)
> at
> java.base/java.security.SecureClassLoader.defineClass(SecureClassLoader.java:174)
> at
> java.base/jdk.internal.loader.BuiltinClassLoader.defineClass(BuiltinClassLoader.java:800)
> at
> java.base/jdk.internal.loader.BuiltinClassLoader.findClassOnClassPathOrNull(BuiltinClassLoader.java:698)
> at
> java.base/jdk.internal.loader.BuiltinClassLoader.loadClassOrNull(BuiltinClassLoader.java:621)
> at
> java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:579)
> at
> java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)
> at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:527)
> at
> org.apache.sling.feature.extension.content.ContentHandler.buildExecutionPlan(ContentHandler.java:74)
> at
> org.apache.sling.feature.extension.content.ContentHandler.handle(ContentHandler.java:118)
> at
> org.apache.sling.feature.launcher.impl.FeatureProcessor.prepareLauncher(FeatureProcessor.java:196)
> at
> org.apache.sling.feature.launcher.impl.Bootstrap.runWithException(Bootstrap.java:157)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (SLING-12028) Content Deployment Extension tests fail on Windows
[
https://issues.apache.org/jira/browse/SLING-12028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu closed SLING-12028.
---
> Content Deployment Extension tests fail on Windows
> --
>
> Key: SLING-12028
> URL: https://issues.apache.org/jira/browse/SLING-12028
> Project: Sling
> Issue Type: Bug
> Components: Feature Model
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>Priority: Major
> Fix For: Feature Model Content Extension 1.0.12
>
>
> {noformat}
> [ERROR]
> org.apache.sling.feature.extension.content.ContentHandlerTest.testMultipleStartOrders
> Time elapsed: 0.617 s <<< FAILURE!
> org.junit.ComparisonFailure:
> expected:<...t5731559958083209794[\]executedplans.file> but
> was:<...t5731559958083209794[/]executedplans.file>
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (SLING-10417) Create execution plans with "strict" import option
[ https://issues.apache.org/jira/browse/SLING-10417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-10417. --- > Create execution plans with "strict" import option > -- > > Key: SLING-10417 > URL: https://issues.apache.org/jira/browse/SLING-10417 > Project: Sling > Issue Type: Improvement > Components: Feature Model >Affects Versions: Feature Model Content Extension 1.0.10 >Reporter: Konrad Windszus >Assignee: Konrad Windszus >Priority: Major > Fix For: Feature Model Content Extension 1.0.12 > > > The execution plans created by the ContentHandler should enforce installation > in strict mode. This is possible since JCRVLT-511 and requires FileVault > 3.5.0 (compare with SLING-10405). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SLING-10405) Update embedded jackrabbit vault to version 3.5.0
[ https://issues.apache.org/jira/browse/SLING-10405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-10405. --- > Update embedded jackrabbit vault to version 3.5.0 > - > > Key: SLING-10405 > URL: https://issues.apache.org/jira/browse/SLING-10405 > Project: Sling > Issue Type: Improvement > Components: Feature Model >Affects Versions: Feature Model Content Extension 1.0.10 >Reporter: Karl Pauls >Assignee: Konrad Windszus >Priority: Major > Fix For: Feature Model Content Extension 1.0.12 > > > The extension currently uses (and embeds) an old version of vault - namely, > 3.2.6. We should update to a newer version. > https://github.com/apache/sling-org-apache-sling-feature-extension-content/blob/master/pom.xml#L104 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SLING-11995) Update to Feature Model 2.0
[ https://issues.apache.org/jira/browse/SLING-11995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-11995. --- > Update to Feature Model 2.0 > --- > > Key: SLING-11995 > URL: https://issues.apache.org/jira/browse/SLING-11995 > Project: Sling > Issue Type: New Feature > Components: Feature Model, Installer >Affects Versions: Feature Model Content Extension 1.0.10, Feature Model > Unpack Extension 0.3.0, Installer Factory Feature Model 0.7.0 >Reporter: Carsten Ziegeler >Assignee: Carsten Ziegeler >Priority: Major > Fix For: Feature Model Content Extension 1.0.12, Feature Model > Unpack Extension 0.3.2, Installer Factory Feature Model 0.8.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (SLING-12029) Make strictMode configurable
[ https://issues.apache.org/jira/browse/SLING-12029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu closed SLING-12029. --- > Make strictMode configurable > > > Key: SLING-12029 > URL: https://issues.apache.org/jira/browse/SLING-12029 > Project: Sling > Issue Type: Improvement > Components: Feature Model >Reporter: Robert Munteanu >Assignee: Robert Munteanu >Priority: Major > Fix For: Feature Model Content Extension 1.0.12 > > > With SLING-10417 we always install the content packages in strict mode. To > ease transition, we should default to strictMode = false and make this an > opt-in. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[RESULT] [VOTE] Release Feature Model Content Extension 1.0.12
Hi, The vote has passed with the following result: +1 (binding): Dan Klco, Carsten Ziegeler, Joerg Hoh +1 (non-binding): none I will copy this release to the Sling dist directory and promote the artifacts to the central Maven repository. Regards, Robert Munteanu
[jira] [Commented] (SLING-12042) Slings Models Export Servlet: Never return 200 status in case of exceptions
[ https://issues.apache.org/jira/browse/SLING-12042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17768699#comment-17768699 ] Konrad Windszus commented on SLING-12042: - [~sseifert] Can you provide a real use case for exporting nested models as JSON where an exception didn't lead to a 200? > Slings Models Export Servlet: Never return 200 status in case of exceptions > --- > > Key: SLING-12042 > URL: https://issues.apache.org/jira/browse/SLING-12042 > Project: Sling > Issue Type: Improvement > Components: Sling Models >Affects Versions: Sling Models Impl 1.4.0, Sling Models Jackson Exporter > 1.0.2 >Reporter: Konrad Windszus >Priority: Major > > Especially for JSON exporters it doesn't make sense to render incomplete JSON > with a 200 status code. All exception which may happen somewhere during the > rendering should lead to a 4xx/5xx status code (and should not be caught > prior to > https://github.com/apache/sling-org-apache-sling-models-impl/blob/0b4f64e167a3999f2835de878191ef1f2b5b4938/src/main/java/org/apache/sling/models/impl/ExportServlet.java#L89) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (SLING-12042) Slings Models Export Servlet: Never return 200 status in case of exceptions
Konrad Windszus created SLING-12042: --- Summary: Slings Models Export Servlet: Never return 200 status in case of exceptions Key: SLING-12042 URL: https://issues.apache.org/jira/browse/SLING-12042 Project: Sling Issue Type: Improvement Components: Sling Models Affects Versions: Sling Models Jackson Exporter 1.0.2, Sling Models Impl 1.4.0 Reporter: Konrad Windszus Especially for JSON exporters it doesn't make sense to render incomplete JSON with a 200 status code. All exception which may happen somewhere during the rendering should lead to a 4xx/5xx status code (and should not be caught prior to https://github.com/apache/sling-org-apache-sling-models-impl/blob/0b4f64e167a3999f2835de878191ef1f2b5b4938/src/main/java/org/apache/sling/models/impl/ExportServlet.java#L89) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (SLING-12041) Slings Models Export Servlet: Never return 200 status in case of exceptions
Konrad Windszus created SLING-12041: --- Summary: Slings Models Export Servlet: Never return 200 status in case of exceptions Key: SLING-12041 URL: https://issues.apache.org/jira/browse/SLING-12041 Project: Sling Issue Type: Improvement Components: Sling Models Affects Versions: Sling Models Jackson Exporter 1.0.2, Sling Models Impl 1.4.0 Reporter: Konrad Windszus Especially for JSON exporters it doesn't make sense to render incomplete JSON with a 200 status code. All exception which may happen somewhere during the rendering should lead to a 4xx/5xx status code (and should not be caught prior to https://github.com/apache/sling-org-apache-sling-models-impl/blob/0b4f64e167a3999f2835de878191ef1f2b5b4938/src/main/java/org/apache/sling/models/impl/ExportServlet.java#L89) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [sling-org-apache-sling-starter] rombert merged pull request #240: chore(deps): update dependency com.composum.nodes:composum-nodes-commons to v4.2.2
rombert merged PR #240: URL: https://github.com/apache/sling-org-apache-sling-starter/pull/240 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [sling-org-apache-sling-starter] rombert commented on pull request #213: chore(deps): update apache felix http
rombert commented on PR #213: URL: https://github.com/apache/sling-org-apache-sling-starter/pull/213#issuecomment-1733687046 @cziegeler - our ITs fail with this update, and this seems to happen when trying to install a bundle using the WebConsole. I can reproduce this locally by running `mvn package sling:install` with a regular Sling bundle. The minimal change to to reproduce this problem updating org.apache.felix:org.apache.felix.http.jetty from 4.2.14 to 4.2.16. Looking at the changes, I see - https://issues.apache.org/jira/browse/FELIX-6620 : https://github.com/apache/felix-dev/commit/8fb0ec2d38fdbd06730e11cdb1150f41614a0237 (unlikely) - Use released http.base 4.2.10 : https://github.com/apache/felix-dev/commit/98760fd4d1f46252e688d0748f7715837ea8ee2b That second commit points to https://github.com/apache/felix-dev/commits/http-4.x/http/base and maybe https://issues.apache.org/jira/browse/FELIX-6625 . But I'm out of ideas no what to check/try next, maybe you have an idea? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [sling-org-apache-sling-starter] renovate-bot opened a new pull request, #240: chore(deps): update dependency com.composum.nodes:composum-nodes-commons to v4.2.2
renovate-bot opened a new pull request, #240: URL: https://github.com/apache/sling-org-apache-sling-starter/pull/240 [](https://renovatebot.com) This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [com.composum.nodes:composum-nodes-commons](https://togithub.com/ist-dresden/composum) | `4.2.1` -> `4.2.2` | [](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
[GitHub] [sling-org-apache-sling-starter] forking-renovate[bot] commented on pull request #235: chore(deps): update dependency org.apache.felix:org.apache.felix.healthcheck.core to v2.2.0
forking-renovate[bot] commented on PR #235: URL: https://github.com/apache/sling-org-apache-sling-starter/pull/235#issuecomment-1733650900 ### Renovate Ignore Notification Because you closed this PR without merging, Renovate will ignore this update (2.2.0). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the `ignoreDeps` array of your Renovate config. If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [sling-org-apache-sling-starter] rombert closed pull request #235: chore(deps): update dependency org.apache.felix:org.apache.felix.healthcheck.core to v2.2.0
rombert closed pull request #235: chore(deps): update dependency org.apache.felix:org.apache.felix.healthcheck.core to v2.2.0 URL: https://github.com/apache/sling-org-apache-sling-starter/pull/235 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [sling-org-apache-sling-starter] rombert opened a new pull request, #239: SLING-12040 - Support Jakarta Servlet APIs
rombert opened a new pull request, #239: URL: https://github.com/apache/sling-org-apache-sling-starter/pull/239 PR that aggregates all the work done to support the Jakarta Servlet APIs. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [sling-org-apache-sling-starter] forking-renovate[bot] commented on pull request #226: chore(deps): update dependency org.apache.felix:org.apache.felix.webconsole.plugins.memoryusage to v1.1.
forking-renovate[bot] commented on PR #226: URL: https://github.com/apache/sling-org-apache-sling-starter/pull/226#issuecomment-1733644911 ### Renovate Ignore Notification Because you closed this PR without merging, Renovate will ignore this update (1.1.0). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the `ignoreDeps` array of your Renovate config. If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [sling-org-apache-sling-starter] rombert closed pull request #226: chore(deps): update dependency org.apache.felix:org.apache.felix.webconsole.plugins.memoryusage to v1.1.0
rombert closed pull request #226: chore(deps): update dependency org.apache.felix:org.apache.felix.webconsole.plugins.memoryusage to v1.1.0 URL: https://github.com/apache/sling-org-apache-sling-starter/pull/226 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [sling-org-apache-sling-starter] forking-renovate[bot] commented on pull request #223: chore(deps): update dependency org.apache.felix:org.apache.felix.healthcheck.webconsoleplugin to v2.2.0
forking-renovate[bot] commented on PR #223: URL: https://github.com/apache/sling-org-apache-sling-starter/pull/223#issuecomment-1733636702 ### Renovate Ignore Notification Because you closed this PR without merging, Renovate will ignore this update (2.2.0). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the `ignoreDeps` array of your Renovate config. If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [sling-org-apache-sling-starter] rombert closed pull request #223: chore(deps): update dependency org.apache.felix:org.apache.felix.healthcheck.webconsoleplugin to v2.2.0
rombert closed pull request #223: chore(deps): update dependency org.apache.felix:org.apache.felix.healthcheck.webconsoleplugin to v2.2.0 URL: https://github.com/apache/sling-org-apache-sling-starter/pull/223 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [sling-org-apache-sling-starter] forking-renovate[bot] commented on pull request #224: chore(deps): update dependency org.apache.felix:org.apache.felix.webconsole.plugins.ds to v2.3.0
forking-renovate[bot] commented on PR #224: URL: https://github.com/apache/sling-org-apache-sling-starter/pull/224#issuecomment-1733635074 ### Renovate Ignore Notification Because you closed this PR without merging, Renovate will ignore this update (2.3.0). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the `ignoreDeps` array of your Renovate config. If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [sling-org-apache-sling-starter] rombert closed pull request #224: chore(deps): update dependency org.apache.felix:org.apache.felix.webconsole.plugins.ds to v2.3.0
rombert closed pull request #224: chore(deps): update dependency org.apache.felix:org.apache.felix.webconsole.plugins.ds to v2.3.0 URL: https://github.com/apache/sling-org-apache-sling-starter/pull/224 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [sling-org-apache-sling-starter] forking-renovate[bot] commented on pull request #225: chore(deps): update dependency org.apache.felix:org.apache.felix.webconsole.plugins.event to v1.2.0
forking-renovate[bot] commented on PR #225: URL: https://github.com/apache/sling-org-apache-sling-starter/pull/225#issuecomment-1733632660 ### Renovate Ignore Notification Because you closed this PR without merging, Renovate will ignore this update (1.2.0). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the `ignoreDeps` array of your Renovate config. If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [sling-org-apache-sling-starter] rombert closed pull request #225: chore(deps): update dependency org.apache.felix:org.apache.felix.webconsole.plugins.event to v1.2.0
rombert closed pull request #225: chore(deps): update dependency org.apache.felix:org.apache.felix.webconsole.plugins.event to v1.2.0 URL: https://github.com/apache/sling-org-apache-sling-starter/pull/225 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [sling-org-apache-sling-starter] forking-renovate[bot] commented on pull request #227: chore(deps): update dependency org.apache.felix:org.apache.felix.webconsole.plugins.obr to v1.1.0
forking-renovate[bot] commented on PR #227: URL: https://github.com/apache/sling-org-apache-sling-starter/pull/227#issuecomment-1733629508 ### Renovate Ignore Notification Because you closed this PR without merging, Renovate will ignore this update (1.1.0). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the `ignoreDeps` array of your Renovate config. If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [sling-org-apache-sling-starter] rombert closed pull request #227: chore(deps): update dependency org.apache.felix:org.apache.felix.webconsole.plugins.obr to v1.1.0
rombert closed pull request #227: chore(deps): update dependency org.apache.felix:org.apache.felix.webconsole.plugins.obr to v1.1.0 URL: https://github.com/apache/sling-org-apache-sling-starter/pull/227 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [sling-org-apache-sling-starter] forking-renovate[bot] commented on pull request #228: chore(deps): update dependency org.apache.felix:org.apache.felix.webconsole.plugins.packageadmin to v1.1
forking-renovate[bot] commented on PR #228: URL: https://github.com/apache/sling-org-apache-sling-starter/pull/228#issuecomment-1733626779 ### Renovate Ignore Notification Because you closed this PR without merging, Renovate will ignore this update (1.1.0). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the `ignoreDeps` array of your Renovate config. If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [sling-org-apache-sling-starter] rombert closed pull request #228: chore(deps): update dependency org.apache.felix:org.apache.felix.webconsole.plugins.packageadmin to v1.1.0
rombert closed pull request #228: chore(deps): update dependency org.apache.felix:org.apache.felix.webconsole.plugins.packageadmin to v1.1.0 URL: https://github.com/apache/sling-org-apache-sling-starter/pull/228 -- 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-12040) Support Jakarta Servlet APIs
[ https://issues.apache.org/jira/browse/SLING-12040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-12040: Description: Third party library updates branch: https://github.com/apache/sling-org-apache-sling-starter/tree/issue/SLING-12040 > Support Jakarta Servlet APIs > > > Key: SLING-12040 > URL: https://issues.apache.org/jira/browse/SLING-12040 > Project: Sling > Issue Type: Sub-task > Components: API, Engine >Reporter: Robert Munteanu >Priority: Major > > Third party library updates branch: > https://github.com/apache/sling-org-apache-sling-starter/tree/issue/SLING-12040 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [sling-org-apache-sling-starter] forking-renovate[bot] commented on pull request #220: chore(deps): update dependency org.apache.felix:org.apache.felix.webconsole to v4.9.4
forking-renovate[bot] commented on PR #220: URL: https://github.com/apache/sling-org-apache-sling-starter/pull/220#issuecomment-1733621628 ### Renovate Ignore Notification Because you closed this PR without merging, Renovate will ignore this update (4.9.4). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the `ignoreDeps` array of your Renovate config. If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [sling-org-apache-sling-starter] rombert closed pull request #220: chore(deps): update dependency org.apache.felix:org.apache.felix.webconsole to v4.9.4
rombert closed pull request #220: chore(deps): update dependency org.apache.felix:org.apache.felix.webconsole to v4.9.4 URL: https://github.com/apache/sling-org-apache-sling-starter/pull/220 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [sling-org-apache-sling-starter] forking-renovate[bot] commented on pull request #222: chore(deps): update dependency org.apache.felix:org.apache.felix.inventory to v2
forking-renovate[bot] commented on PR #222: URL: https://github.com/apache/sling-org-apache-sling-starter/pull/222#issuecomment-1733618254 ### Renovate Ignore Notification Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for *any* future 2.x releases. But if you manually upgrade to 2.x then Renovate will re-enable `minor` and `patch` updates automatically. If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [sling-org-apache-sling-starter] rombert closed pull request #222: chore(deps): update dependency org.apache.felix:org.apache.felix.inventory to v2
rombert closed pull request #222: chore(deps): update dependency org.apache.felix:org.apache.felix.inventory to v2 URL: https://github.com/apache/sling-org-apache-sling-starter/pull/222 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (SLING-12040) Support Jakarta Servlet APIs
Robert Munteanu created SLING-12040: --- Summary: Support Jakarta Servlet APIs Key: SLING-12040 URL: https://issues.apache.org/jira/browse/SLING-12040 Project: Sling Issue Type: Sub-task Components: API, Engine Reporter: Robert Munteanu -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (SLING-10000) Switch to Jakarta APIs
[
https://issues.apache.org/jira/browse/SLING-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17768668#comment-17768668
]
Robert Munteanu commented on SLING-1:
-
I think [~cziegeler] has been doing a lot of work on the Felix side for the
jakarta.servlet migration. What is not clear to me is whether we can support
javax.servlet and jakarta.servlet at the same time. Otherwise it's going to be
a very hard sell for our users.
> Switch to Jakarta APIs
> --
>
> Key: SLING-1
> URL: https://issues.apache.org/jira/browse/SLING-1
> Project: Sling
> Issue Type: Task
> Components: API
>Reporter: Oliver Lietz
>Priority: Major
>
> Java EE APIs are switching from {{javax}} to {{jakarta}}.
> Jakarta Specifications: [https://jakarta.ee/specifications/]
> *Candidates*
> * {{javax.activation}}
> * {{javax.servlet}}
> * {{javax.mail}}
> *Discovery*
> * Should we have branch {{jakarta}} in each module which needs to switch?
> * Should we use the breaking change (major version increase in most APIs) to
> clean up and improve our current API or limit it to the package switch?
> *Tooling*
> * [Eclipse Transformer|https://github.com/eclipse/transformer]
> * [Tomcat Migration Tool for Jakarta EE
> software|https://tomcat.apache.org/download-migration.cgi]
> * [JetBrains IntelliJ IDEA – Automatic migration from Java EE to Jakarta
> EE|https://blog.jetbrains.com/idea/2021/06/intellij-idea-eap-6/#automatic_migration_from_java_ee_to_jakarta_ee]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
