i created https://issues.apache.org/jira/browse/SLING-13029 with two integration tests specific to new stuff added in servlet api 6.1 and not preset in 6.0: https://github.com/apache/sling-org-apache-sling-starter-test-services/pull/19 https://github.com/apache/sling-org-apache-sling-starter-integration-tests/pull/40
the integration tests are running fine on all platform - so although i do not exactly understand why it's working with jetty 12.0.30, it seems to work in practices. in my pov this is not blocking our sling starter 14 release - we can always make a new release when felix comes around with a new http release featuring jetty 12.1. stefan > -----Original Message----- > From: Stefan Seifert <[email protected]> > Sent: Wednesday, December 10, 2025 10:36 AM > To: [email protected] > Subject: Sling Starter: Jetty 12.0 vs. Jakarta Servlet 6.1 > > bringing the discussion that started in [1] on the mailing list: > > - we currently have Jetty 12.0.30 in Sling Starter, which comes with > Jakarta Servlet 6.0 [2] > - however, we have Jakarta Servlet 6.1 as part of Sling Starter, via > dependency [3] > - with SLING-12752 [4] we have migrated a couple of core modules to > Jakarta Servlet 6.1 > - but it seems that only Jetty 12.1 is fully compatible with Jakarta > Servlet 6.1? at least according to https://jetty.org/download.html > - but Jetty 12.1 is not yet available as part of a Felix HTTP release, > it's still in progress FELIX-6750 [5] > > are we save to ship Starter 14 with this combination of Jetty 12.0 and > Jakarta Servlet 6.1? > > stefan > > > [1] https://github.com/apache/sling-site/pull/248#discussion_r2605848511 > [2] https://felix.apache.org/documentation/news.html > [3] > https://repo1.maven.org/maven2/org/apache/felix/org.apache.felix.http.serv > let-api/6.1.0/ > [4] https://issues.apache.org/jira/browse/SLING-12752 > [5] https://issues.apache.org/jira/browse/FELIX-6750
