Today, together with Wicket 11.0.0,
we released Apache Wicket 9.25.0 and 8.20.0: the final releases of both lines. Wicket 9 and 8
have now reached end of life. They get no more releases, not even security fixes, and
Wicket’s support for the javax.servlet API ends with them. If your application runs on
Wicket 8 or 9, move to Wicket 10, our long-term support release, supported until July 2027,
or on to Wicket 11 for new features every quarter.
What end of life means
From today:
- no new 8.x or 9.x release ships, for bugs or for vulnerabilities;
- every release stays available: on Maven Central, and in the Apache archives;
- the users list still helps with questions, but a fix for a problem in 8 or 9 only ships in the lines we still support.
Why we stop
We announced this with the new release cadence. Every security report has to be assessed, fixed, backported and released for each line we support. With four lines that work is done four times, and that is time not spent on improving Wicket itself. Retiring 8 and 9 brings it back to two lines: the LTS and the current quarterly release.
Wicket 8 and 9 are also the last lines on javax.servlet. The Java world moved to the
jakarta namespace, and Wicket 10 moved with it.
How to move to Wicket 10
Wicket 10 requires Java 17 and Jakarta Servlet 5.0 or newer, and its integrations move along: Spring 6, Guice 7 and Commons FileUpload 2.
-
From Wicket 9, move to 10 directly with the
migration guide to Wicket 10. The
OpenRewrite recipes of
wicket-migrationdo the repetitive part: thejakartaimports, the Java 17 baseline and the moved Wicket classes. - From Wicket 8, take the Wicket 9 step first, with the migration guide to Wicket 9 and Java 11. Each migration guide covers one major version, so the step to 10 follows from there.
The upgrade paths on the releases page show each step, and the pages of Wicket 9 and Wicket 8 list them as well.
Once on Wicket 10, the step to Wicket 11 is your JDK and your container: it needs Java 21 and Jakarta Servlet 6.1.
Need help?
Ask on the users list when the migration raises questions; include your Wicket and Java versions. If you need more hands or more time, several companies offer training, consulting and development for Wicket applications. The Wicket project does not endorse or rank them.