Release lines

Apache Wicket 8.x

One final release, then end of life: supported until 11.0.0, Oct 2026.

Latest release
8.19.0
Status
In service
Supported
Until 11.0.0, Oct 2026
Java
8 or newer
Servlet API
Servlet 3.1 or newer

Maven dependency

<dependency>
    <groupId>org.apache.wicket</groupId>
    <artifactId>wicket-core</artifactId>
    <version>8.19.0</version>
</dependency>

New project? Generate one with the quick start.

New in Wicket 8

  • Java 8

    Wicket 8 requires Java 8 and Servlet 3.1, so it runs on Tomcat 8, Jetty 9.1 or any Java EE 7 server.

    Java
    8
    Servlet
    3.1

  • Models as lambdas

    IModel is a functional interface: a method reference or a lambda is a model. LambdaModel replaces string-based property expressions with type-safe, refactoring-safe bindings that also run faster.

    PersonPanel.java

    add(new Label("name1", person::getName));
add(new Label("name2", () -> person.getName()));
add(new Label("name3", LambdaModel.of(personModel, Person::getName)));

  • Optional where null was possible

    The API uses Optional where a value may be absent. An AjaxFallbackLink now tells you whether it was clicked through Ajax.

    HomePage.java

    add(new AjaxFallbackLink<Void>("link") {
    @Override
    public void onClick(Optional<AjaxRequestTarget> target) {
        target.ifPresent(t -> t.add(counter));
    }
});

  • Java date and time

    The java.time types are converted, validated and bound to components out of the box.

Documentation

News about Wicket 8

All posts on the blog

Download

The most recent release in this branch is: 8.19.0. You can get the release using Maven or download it manually.

Download manually

Use the following links to download Wicket manually to build Wicket from source:

Or use the following links to get the pre-packaged binaries instead:

Note that the binary packages and the source packages don’t contain any dependencies necessary to have your project working out of the box. We strongly urge you to use Maven (or Buildr, or Gradle) as your dependency management system.

Verify distribution’s signature

PGP signatures can be verified as described on this page. The public key used to sign Wicket distributions can be found in the KEYS file.

Older releases

The Apache mirroring system only hosts the latest version of each actively supported branch. When you need to download an older release you can find them in the archives.

Go to the Apache archives to find your specific version.

Change log

To see what changed in these releases you can read the change log.

Requirements

Apache Wicket has few requirements in order to work properly. In this section you’ll find the minimum requirements for all Wicket modules. Specific modules may need additional libraries, such as file upload, date time APIs, CDI specifications, and more. See the module’s POM for more details on the necessary libraries.

Java version

This Wicket version requires at least the following Java version: JDK 8.0 or newer.

Not only is a particular version of Java necessary, Wicket also needs access to specific APIs.

Servlet API

This Wicket version requires at least the following Servlet API version: Servlet API 3.1 or newer. This is provided by your container, please see the documentation of your container to see which version of the Servlet specification is supported.

In addition to the Servlet API, Wicket uses SLF4J to let you choose your own implementation of a logging framework.

Logging

You cannot use Wicket without adding an SLF4J logging implementation to your classpath. Most people use log4j.

If you do, just include slf4j-log4j12.jar on your classpath to get Wicket to use log4j too. If you want to use commons-logging or JDK14 logging or something else, please see the SLF4J site for more information.

Don’t mix Wicket versions

You cannot mix different Wicket versions in your project. You should always use the artifacts from a particular release. For example it is not possible to use Wicket Extensions 1.5 in a Wicket 6 project, or Wicket CDI 7.x in a Wicket 8 project. The same goes for 3rd party libraries: make sure you always use a compatible version of your 3rd party library.

Migrating from earlier versions

If you are migrating an existing application from earlier versions of Wicket you may find our migration guides invaluable: