cziegeler opened a new pull request, #473:
URL: https://github.com/apache/sling-org-apache-sling-starter/pull/473
(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
Hi,
if we want to support Jakarta Servlet API we need to update to Apache
Felix Jetty12. We should do this independent of Sling supporting Jakarta
Servlet API to have a clearer changeset if regressions occur.
The update to Apache Felix Jetty12 comes with the requirement of Java 17
at runtime
Carsten Ziegeler created SLING-12812:
Summary: Update to SLF4J 2
Key: SLING-12812
URL: https://issues.apache.org/jira/browse/SLING-12812
Project: Sling
Issue Type: Improvement
C
Hi,
those two rules sound reasonable and is probably the only check that the
resource resolver itself could do.
I don't think that a general escaping method helps as providers usually
do their own escaping already today. If these providers do not switch to
the general one, it does not help.
renovate-bot closed pull request #301: chore(deps): update dependency
org.slf4j:slf4j-api to v2 - autoclosed
URL: https://github.com/apache/sling-org-apache-sling-starter/pull/301
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub a
[
https://issues.apache.org/jira/browse/SLING-12812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-12812.
--
Resolution: Fixed
https://github.com/apache/sling-org-apache-sling-starter/commit/75ab