The status for Wicket 10.x is: in development.
This is the development version, NOT production-ready release of Wicket. All projects intended for production use should use version 9.x.
These releases follow semantic versioning so upgrades between minor releases will not break compatibility.
To see what changed in these releases you can read the change log.
Using Apache Maven
Use the following Maven dependency to use Wicket in your project:
Add the snippet above to your project’s POM in the dependency (management) section.
You can add more Wicket modules to your project by adding more
dependencies (copy above snippet and change the
If you are not a Maven user, you can download the Wicket release manually.
Use the following links to download Wicket manually to build Wicket from source:
- Download source apache-wicket-10.0.0-M1.tar.gz (PGP, SHA-256 )
- Download source apache-wicket-10.0.0-M1.zip (PGP, SHA-256 )
Or use the following links to get the pre-packaged binaries instead:
- Download binaries apache-wicket-10.0.0-M1-bin.tar.gz (PGP, SHA-256 )
- Download binaries apache-wicket-10.0.0-M1-bin.zip (PGP, SHA-256 )
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
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.
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.
This Wicket version requires at least the following Java version: JDK 17.0 or newer.
Not only is a particular version of Java necessary, Wicket also needs access to specific APIs.
This Wicket version requires at least the following Servlet API version: Servlet API 5.0 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.
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:
- Migrating from Wicket 1.2 to Wicket 1.3
- Migrating from Wicket 1.3 to Wicket 1.4
- Migrating from Wicket 1.4 to Wicket 1.5
- Migrating from Wicket 1.5 to Wicket 6.x
- Migrating from Wicket 6.x to Wicket 7.x
- Migrating from Wicket 7.x to Wicket 8.x
- Migrating from Wicket 8.x to Wicket 9.x
- Migrating from Wicket 9.x to Wicket 10.x