Upgrade Jetty

[kurtostfeld]

This slack sdk uses Jetty 9.x which is wildly out of date and EOL. Jetty 12.1 is the current version; that would be best.

[hello-ashleyintech]

Hi, @kurtostfeld! Thank you so much for raising this to our attention. 😄 I will let our internal dev expert for the Java SDK know, but I have also tagged this as a good first issue if you or any other community member would like to give upgrading this a shot!

[github-actions]

👋 It looks like this issue has been open for 30 days with no activity. We'll mark this as stale for now, and wait 10 days for an update or for further comment before closing this issue out. If you think this issue needs to be prioritized, please comment to get the thread going again! Maintainers also review issues marked as stale on a regular basis and comment or adjust status if the issue needs to be reprioritized.

[seratch]

While bolt-jetty is a legacy one that is still compatible with javax servlet interface, bolt-jakarta-jetty supports 11.x. The Jetty version bolt-jakarta-jetty relies on can be upgraded to 12.x and it shouldn't take much time.

[skrcode]

I would be happy to work on this. Before I start, would the following scope be acceptable?

• Leave the legacy bolt-jetty / javax.servlet module unchanged.
• Upgrade only bolt-jakarta-jetty from Jetty 11 to Jetty 12.1, including the required Jetty artifact and API changes.
• Make the Java 17 runtime requirement explicit for that module, since Jetty 12 requires Java 17.
• Add or update focused server coverage and run the relevant module build plus the repository CI-safe test suite.

The remaining compatibility choice is whether this module should stay aligned with Jakarta EE 9/10 or move to Jakarta EE 11 while adopting Jetty 12.1. If you confirm the preferred target, I can send a focused PR.