slachiewicz opened a new issue, #3437: URL: https://github.com/apache/maven-surefire/issues/3437
Registering this so the maintainers can decide rather than proposing a change. It came out of the estate-wide Jetty review in [apache/maven#12768](https://github.com/apache/maven/issues/12768), triggered by the Jetty 9/10/11 end-of-life announcement in [jetty/jetty.project#13918](https://github.com/jetty/jetty.project/issues/13918). ## Where we stand `maven-failsafe-plugin/src/it/jetty-war-test-passing` and `.../jetty-war-test-failing` both set: ```xml <jetty-version>9.2.2.v20140723</jetty-version> ``` and run `org.eclipse.jetty:jetty-maven-plugin` at that version to prove failsafe behaves correctly for tests running inside a servlet container. Two things worth knowing about that version: - 9.2.2.v20140723 is from July 2014, and the 9.2 line went on to finish at `9.2.30.v20200428`. So this is not even the end of its own line — it is 28 releases short of it. - With the end-of-life announcement, the whole Jetty 9 line is now closed. The last release anywhere on it is `9.4.58.v20250814`. These are integration-test fixtures. Nothing ships, nothing is exposed, and the artifacts stay on Central, so nothing breaks either. They do run on every JDK in the matrix (`[ "8", "11", "17", "21" ]`) — `invoker.properties` carries only `invoker.buildResult`, with no JDK guard — so whatever version is chosen has to keep working from JDK 8 through 21. ## The decision, as I see it **Leave it.** The fixture's job is to prove failsafe works inside a container; which container and which version is incidental, and it evidently still works across the whole matrix. There is a real argument that a frozen fixture is a feature. **Bump to 9.2.30.v20200428.** End of the same line, so configuration should carry over unchanged, and it picks up six years of fixes for free. **Bump to 9.4.58.v20250814.** End of the Jetty 9 line entirely. More likely to need configuration changes, and it still lands on an end-of-life line, so it buys tidiness rather than a future. Jetty 12 is not an option while JDK 8 is in the matrix — it requires Java 17. No urgency from my side. Recording it so it is a decision rather than an oversight. *This issue was created with AI assistance.* -- 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]
