Getting Wicket

There are a couple of things to consider when downloading Wicket for your project. Do you use Maven? Do you need to run on Java 1.4?

Here's a matrix for picking the right Wicket version:

Wicket versions

Here's a small description of the different Wicket releases.

...

Wicket 1.2.5

Wicket 1.2.5 is our stable release and is available from SourceForge.net. This is often referred to as wicket-1.2.x

The Wicket 1.2.x releases are not endorsed by, approved by, nor affiliated with the Apache Software Foundation in any way.

Wicket 1.3

Wicket 1.3 is currently under development at the Apache Software Foundation, while inside the Incubator. When projects first move to Apache, they are housed at the Apache Incubator. The Incubator helps incoming projects migrate to the vibrant Apache community.

Currently there is no release available for Wicket 1.3. The only way to get at the code is to use our development snapshot releases, or build it yourself from subversion.

You can see the status of Wicket's incubation process on this page.

Getting Wicket using Maven

When you use Maven version 2, getting Wicket releases is very easy. For our stable release you can use the default maven repositories. For development snapshots you will need to specify our snapshot repository for maven to find the generated jar files.

Apache Wicket 1.4.8 is the current stable release.

Download

We recommend you start with our latest 1.4 release. If you are migrating an existing application from Wicket 1.3 to 1.4, you may find the migration guide invaluable.

Apache Wicket 1.4.x lines require JDK 1.5 or newer

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

Important note about logging dependencies for 1.3.0 and later.

As of Wicket 1.3.0, Wicket uses the SLF4J project for logging. 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 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.

Maven 2

Add the following snippet to your Maven project descriptor (pom.xml):

<dependency>
    <groupId>org.apache.wicket</groupId>
    <artifactId>wicket</artifactId>
    <version>1.4.8</version>
</dependency>

For the SLF4J log4j binding:

<dependency>
    <groupId>org.slf4j</groupId>
    <artifactId>slf4j-log4j12</artifactId>
    <version>1.4.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:

<repositories>
    <repository>
        <id>org.wicketstuff</id>
        <name>Wicket Stuff Repository</name>
        <url>http://wicketstuff.org/maven/repository</url>
    </repository>
</repositories>

...

Getting Wicket 1.2.5 using Maven

...