Jetty 9, 10 and 11 stopped being published to Maven Central on 1 January 2026 — see jetty/jetty.project#13918. Estate-wide context and the shared constraints are in apache/maven#12768; this issue covers maven-dependency-plugin only.
Filing this for the record rather than as work to schedule: the honest answer here is that there is nothing to do yet, and it is worth writing down why so the next person to notice the EOL announcement does not have to re-derive it.
Where we stand
pom.xml sets <jettyVersion>9.4.58.v20250814</jettyVersion> and takes jetty-server, jetty-util and jetty-security at test scope, for the local test servers.
Test scope, so nothing ships and nothing breaks. And 9.4.58.v20250814 is already the final release of the Jetty 9.4 line, so unlike maven-javadoc-plugin there is not even a patch bump available. We are as current as that line will ever get.
What would unblock a move
Jetty 12 requires Java 17. This plugin builds at javaVersion 8 and inherits the shared CI matrix default of [ "21", "25", "8" ]. Test code can compile at a different level than the shipped baseline via maven.compiler.testRelease, but it still has to run on every JDK in the matrix, so JDK 8 has to leave the matrix before Jetty 12 can enter the build in any scope.
When that happens, the test servers are a candidate for org.apache.maven.resolver:maven-resolver-test-http (published on Central at 2.0.21, already Java 17) instead of a hand-rolled Jetty 12 harness.
Until then: no action, and no cause for alarm.
This issue was created with AI assistance.
Jetty 9, 10 and 11 stopped being published to Maven Central on 1 January 2026 — see jetty/jetty.project#13918. Estate-wide context and the shared constraints are in apache/maven#12768; this issue covers maven-dependency-plugin only.
Filing this for the record rather than as work to schedule: the honest answer here is that there is nothing to do yet, and it is worth writing down why so the next person to notice the EOL announcement does not have to re-derive it.
Where we stand
pom.xmlsets<jettyVersion>9.4.58.v20250814</jettyVersion>and takesjetty-server,jetty-utilandjetty-securityat test scope, for the local test servers.Test scope, so nothing ships and nothing breaks. And 9.4.58.v20250814 is already the final release of the Jetty 9.4 line, so unlike maven-javadoc-plugin there is not even a patch bump available. We are as current as that line will ever get.
What would unblock a move
Jetty 12 requires Java 17. This plugin builds at
javaVersion8 and inherits the shared CI matrix default of[ "21", "25", "8" ]. Test code can compile at a different level than the shipped baseline viamaven.compiler.testRelease, but it still has to run on every JDK in the matrix, so JDK 8 has to leave the matrix before Jetty 12 can enter the build in any scope.When that happens, the test servers are a candidate for
org.apache.maven.resolver:maven-resolver-test-http(published on Central at 2.0.21, already Java 17) instead of a hand-rolled Jetty 12 harness.Until then: no action, and no cause for alarm.
This issue was created with AI assistance.