Getting Wicket

Wicket used to live at SourceForge. We recently joined the Apache Software Foundation and have graduated to a top-level project. We don't have any stable releases under Apache yet, but 1.3.0 will be released soon. In the meantime, Wicket 1.24.x is still hosted on SourceForge, and Wicket 1.3.0 beta releases are available on Apache.8 is the current stable release.

DownloadDownload 

Download latest stable release:
Download latest beta release: 

For new projects, we We recommend you start with our latest beta 1.4 release. Lots of people are using it on live production sites with no issues, so it's fairly stable. We will release If you are migrating an existing application from Wicket 1.3 to 1.0 final shortly4, so if you're just starting out it's definitely the one to go for.you may find the migration guide invaluable.

Apache Wicket 1.4.x lines require JDK 1.5 or newer

Apache Wicket Both the 1.2.x and the 1.3.x lines require JDK 1.4 or newer, although there are some non-core modules which take advantage of JDK 5 features.

The core framework will switch to JDK5 for the next major version (1.4.x or 2.x, we haven't decided the numbering scheme quite yet).

...

Important note about logging dependencies for 1.3.0 and later.

As of Wicket 1.3.0, Wicket uses the SLF4J project for logging. To make this work in your application, you need to pick a static binding to use. Most people will want to SLF4J is similar to commons-logging, in that it allows libraries/frameworks like Wicket to avoid forcing a choice of logging framework on their users.

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 .SLF4J is similar to commons-logging, in that it allows libraries/frameworks like Wicket to avoid forcing a choice of logging framework on their users. For more information, see the SLF4J FAQto 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.

Maven 2

For 1.2.6, add Add the following snippet to your Maven project descriptor (pom.xml):

...

<dependency>
    <groupId>wicket</groupId>
    <artifactId>wicket</artifactId>
    <version>1.2.6</version>
</dependency>

Or for 1.3.0-beta2:

<dependency>
    <groupId>org.apache.wicket</groupId>
    <artifactId>wicket</artifactId>
    <version>1.34.0-beta2<8</version>
</dependency>

For the SLF4J log4j binding (see above):

<dependency>
    <groupId>org.slf4j</groupId>
    <artifactId>slf4j-log4j12</artifactId>
    <version>1.4.0<2</version>
</dependency>

SNAPSHOTs and latest bleeding-edge code

If you wish to build the latest code from scratch, the two branches live in the following places in Subversion:

• 1.5.x: http://svn.apache.org/repos/asf/wicket/trunk
• 1.4.x: http://svn.apache.org/repos/asf/wicket/branches/wicket-1.4.x
• 1.3.x: http://svn.apache.org/repos/asf/wicket/branches/wicket-1.3.x
• 1.2.x: http://svn.apache.org/repos/asf/wicket/branches/wicket-1.2.x

There's also a Maven 2 repository providing SNAPSHOTs available here:

...