kwin commented on code in PR #248: URL: https://github.com/apache/sling-site/pull/248#discussion_r2604155351
########## 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 for Java 17+ 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. + + +## Drop support for Java 11 + +Some of the Sling modules and their dependencies started to switch to Java 17 as minimum version, so Java 11 is no longer supported for the Sling Starter. + + +## 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. Review Comment: Isn't this Jetty 12.1 which supports Servlet 6.1? ########## 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 for Java 17+ 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. Review Comment: I think we can leave out the "for Java 17+" part now that we require 17+ ########## 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 for Java 17+ 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. + + +## Drop support for Java 11 + +Some of the Sling modules and their dependencies started to switch to Java 17 as minimum version, so Java 11 is no longer supported for the Sling Starter. Review Comment: Just curious: Which modules are those? Just Jetty 12.1 or something else as well? -- 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]
