Apache Wicket 1.4.x
End of life: no more releases, not even security fixes.
- Latest release
- 1.4.23
- Status
- End of life
- Supported
- No longer supported
- Java
- 5 or newer
- Servlet API
- Servlet 2.3 or newer
Wicket 1.4 gets no more releases, not even security fixes
Plan the move to Wicket 10 LTS. It is supported until Jul 2027.
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 1.4.x: Java 5+, Servlet 2.3+ -->
<dependency>
<groupId>org.apache.wicket</groupId>
<artifactId>wicket-core</artifactId>
<version>1.4.23</version>
</dependency>Documentation
-
Docs
Wicket 1.4 has no reference guide of its own; the wiki and the books cover it.
-
Migration guide
Migrating from Wicket 1.3 to 1.4: what changed and what to adjust in your application.
-
API documentation
The Javadoc for Wicket 1.4 ships in the binary download.
Blog posts about Wicket 1.4
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:
- Download source apache-wicket-1.4.23.tar.gz (PGP, MD5, SHA )
Or the binaries:
- Download binaries apache-wicket-1.4.23-bin.tar.gz (PGP, MD5, SHA )
- Download binaries apache-wicket-1.4.23-bin.zip (PGP, MD5, SHA )
Neither package contains the libraries Wicket depends on; a build tool such as Maven or Gradle brings those in.
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.