slachiewicz opened a new issue, #760: URL: https://github.com/apache/maven-indexer/issues/760
Jetty 9, 10 and 11 stopped being published to Maven Central on 1 January 2026 — see [jetty/jetty.project#13918](https://github.com/jetty/jetty.project/issues/13918). Estate-wide context and the shared constraints are in [apache/maven#12768](https://github.com/apache/maven/issues/12768); this issue covers maven-indexer only. ## Where we stand The root `pom.xml` manages `org.eclipse.jetty:jetty-webapp` at `10.0.24`, test scope, used by `indexer-core` and `indexer-cli`. The usage is a local server for the remote-index download tests — `DownloadRemoteIndexerManagerTest` and `ServerTestFixture` build a `Server` with `ResourceHandler`, `HandlerList` and `ConstraintMapping`. Test scope, so the exposure is limited to our own build. Nothing breaks and no release is blocked. ## Why this one is different from the rest of the estate maven-indexer is the only affected repository that can act today. Everywhere else the blocker is JDK 8 sitting in the CI matrix, which stops Jetty 12 from entering the build in any scope. This repository pins `jdk-matrix: '[ "17", "21" ]'` — no JDK 8 — so the Java 17 requirement of Jetty 12 is not in the way of test code. The main baseline is `javaVersion` 11, and `maven.compiler.release` applies to test compilation too by default, so a move needs `maven.compiler.testRelease` set to 17 (or a baseline bump, which is a bigger conversation and not needed for this). ## Two options 1. **Bump to 10.0.26** — the last release of the Jetty 10 line. One coordinate change, no code change, picks up the remaining fixes. It leaves us on an EOL line, so it is a stopgap. 2. **Move the test harness to Jetty 12.** `org.eclipse.jetty:jetty-webapp` does not exist above the 11 line; the equivalent is `org.eclipse.jetty.ee10:jetty-ee10-webapp` at 12.1.12. This is a rewrite of the fixtures rather than a version bump — `HandlerList` is gone in Jetty 12, replaced by `Handler.Sequence`, and the security configuration moved with it. There is also a third path worth considering if the fixtures get rewritten anyway: `org.apache.maven.resolver:maven-resolver-test-http` is published on Central (2.0.21), already targets Java 17, and exists to be exactly this kind of test HTTP server. Reusing it would remove the Jetty dependency from this repository entirely rather than moving it forward one line. Doing option 1 now and deciding between 2 and 3 separately seems reasonable. *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]
