Releases

Apache Wicket 9.x

One more Wicket 9 release follows 9.24.0; after it the line reaches end of life. Its date will be on the blog; subscribe to the announce list to hear it first.

Latest release
9.24.0
Status
Last release coming
Supported
Until its final release
Java
11 or newer
Servlet API
Servlet 3.1 or newer

Wicket 9 reaches end of life with its final release

Wicket 8 and 9 reach end of life soon: what end of life means, why, and how to move.

Plan the move to Wicket 10 LTS. It is supported until Jul 2027.

Migrating from Wicket 9 to 10

For the step to 10, the OpenRewrite recipes of wicket-migration do the repetitive part: the jakarta imports, the Java 17 baseline and the moved Wicket classes.

The upgrade paths explain each step and what changes in Java and the Servlet API. If you need help or more time, companies that offer Wicket support are listed on the wiki.

Maven dependency

<!-- Apache Wicket 9.x: Java 11+, Servlet 3.1+ -->
<dependency>
    <groupId>org.apache.wicket</groupId>
    <artifactId>wicket-core</artifactId>
    <version>9.24.0</version>
</dependency>

Download the source and binaries

New in Wicket 9

  • Modern Java

    Wicket 9 requires Java 11, supports the Java module system, and moves WicketTester to JUnit 5.

    Java
    11
    Servlet
    3.1
    JUnit
    5

  • Content Security Policy

    Wicket 9 ships a content security policy that needs no unsafe-inline: every header contribution gets a nonce, and the policy allows exactly that nonce. You can add directives to the policy or switch it off.

  • Keeping up with Java

    Wicket takes part in the OpenJDK Quality Outreach, so every new Java release and early-access build is tested against it.

Documentation

Blog posts about Wicket 9

All posts on the blog

Download

Source and binaries

Most projects get Wicket through Maven or Gradle, with the dependency at the top of this page. To build Wicket yourself, or to use it without a build tool, download the source:

Or the binaries:

Neither package contains the libraries Wicket depends on; a build tool such as Maven or Gradle brings those in.

Verify a download

Check its PGP signature with the keys in the KEYS file, as the ASF explains.

Older releases

The mirrors carry only the latest release of each line in service. Every older release is in the Apache archives.

Change log

What changed in each release of this line is in the change log.

Requirements

The Java and Servlet API versions this line needs are at the top of the page. Some modules need more libraries, such as file upload, date and time APIs or the CDI specification; each module’s POM lists them.

Logging

Wicket logs through SLF4J, so your application needs an SLF4J implementation on the classpath. The SLF4J manual lists them.

Don’t mix Wicket versions

Use one Wicket version for every Wicket module in a project: wicket-core, wicket-extensions, wicket-spring and the others are released together and only work with the same version. Libraries built on Wicket are made for one Wicket line; use the version made for yours.