rombert commented on code in PR #248: URL: https://github.com/apache/sling-site/pull/248#discussion_r2610722956
########## src/main/jbake/content/news/sling-14-released.md: ########## @@ -0,0 +1,390 @@ +title=Apache Sling 14 released +type=page +status=published +tags=launchpad +~~~~~~ + +The Sling 14 release contains numerous improvements, such as official Java 25 Support and supporting the Jakarta Servlet API, and various performance improvements and updates. + +Read on to see more details about the individual improvements. To find out more about running Sling, see our [getting started page](/documentation/getting-started.html). + +## Official support for Java 25 + +The Sling Starter and included modules are validated to work on Java 17, 21 and 25. + +Note that the `org.apache.sling.commons.threads` will not clean up leftover `ThreadLocal` instances unless the `--add-opens java.base/java.lang=ALL-UNNAMED` is passed to the JVM. This fix is already applied to the [official Sling Starter Docker image](https://hub.docker.com/r/apache/sling) and we anticipate further fixes in this area. + + +## Support Jakarta Servlet API 6.1 and switch to Jetty 12 + +Sling Starter 14 runs on Jetty 12 and fully supports Jakarta Servlet API 6.1. However, OSGi bundles implemented against the old Servlet API 4 are still supported as well. You don't have to update your application code. New projects should start using the latest Servlet API right away. + +See this talk for more details: [adaptTo() 2025 - Seamless Transition: Apache Sling's Adoption of Jakarta Servlet API](https://adapt.to/2025/schedule/seamless-transition-apache-slings-adoption-of-jakarta-servlet-api) + + +## Drop support for Java 11 + +All Sling modules that have been migrated to Jakarta Servlet API 6.1 have Java 17 as minimum version, so Java 11 is no longer supported for the Sling Starter. + + +## Switch to jakarta.json completed + +All modules have been migrated from `org.json` to `jakarta.json` and the Sling Starter 14 only comes with [Apache Johnzon](https://johnzon.apache.org/) 2.x. If you still have modules using `org.json`, you can continue to use them, but you have to deploy a 1.x version of `org.apache.sling.commons.json` in addition to the 2.x version. + + +## Switch to SLF4J 2 + +The Sling starter and a couple of core modules have switched to SLF4J 2. Apache Sling Commons Log 6 is included in Sling Starter 14 and comes with an updated logback implementation and full support for SLF4J 2. Bundles using SLF4J 1 are still supported. + + +## Separate Bundle for Sling Event API + +The Sling Event API, which was exported by the implementation bundle before, is now deployed as separate bundle `org.apache.sling.event.api` - ensuring a proper separation of API and implementation. + + +## Sling Starter + +Sling Starter now registers by default an JMX MBean platform powered by [Apache Aries JMX](https://aries.apache.org/documentation/modules/jmx.html). + + +## Sling API + +Two small additions to Sling API: + +* [SLING-12815](https://issues.apache.org/jira/browse/SLING-12815) Expose methods to escape/unescape characters which are invalid in Sling Resource names +* [SLING-12441](https://issues.apache.org/jira/browse/SLING-12441) Support InputStream based request parameters in Builders + + +## Version updates + +All bundles have been updated to the latest versions. + +New bundles added to Sling Starter: + +* `org.apache.aries.jmx.mbeanserver-platform` +* `org.apache.sling.event.api` Review Comment: I think this can be omitted because it was already covered in https://github.com/apache/sling-site/pull/248/files#diff-b79c54260aec87c02a37b4bbcb09c5c42000d20bfbb62d9643292a3db3b1be53R40-R42 ########## src/main/jbake/content/news.md: ########## @@ -5,6 +5,7 @@ tags=news tableOfContents=false ~~~~~~ +* Released [Apache Sling 14](/news/sling-14-released.html) (Dezember ???, 2025). Review Comment: December :-) -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
