Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

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:

Version

Java version

Code status

Apache status

Maven

Download

Subversion

1.2.5

>= 1.4

Stable

n/a

maven

sourceforge

releases/wicket-1.2.5

1.2.x

>= 1.4

Stable

n/a

snapshot

n/a

branches/wicket-1.2.x

1.3

>= 1.4

Beta

incubating

snapshot

n/a

branches/wicket-1.x

2.0

>= 1.5

Alpha

incubating

snapshot

n/a

trunk

Wicket versions

Here's a small description of the different Wicket releases. Our current stable release is Wicket 1.2.5, which is released outside the Apache Software Foundation. Development within the Apache Software Foundation is ongoing on Wicket 1.3 and 2.0. Wicket 2.0 was scheduled as our next major release, but considering that it requires Java 1.5 or newer, the Wicket team decided to backport some major features into our Wicket 1 stream. The result of this effort is the upcoming Wicket 1.3.

...

Apache Wicket 1.4.8 is the current stable release.

Download

Latest stable release

1.4.8

(from the Apache Software Foundation)

Archived release

1.3.7

(from the Apache Software Foundation)

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):

Code Block
xml
xml

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

For the SLF4J log4j binding:

Code Block
xml
xml

<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:

...

Wicket 1.2.5

Wicket 1.2.5 is our stable release and is available from SourceForge.net and through the Maven central repository. It is the release version of the maintenance branch wicket-1.2.x. 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.

...

Subversion

  • 1.5.x:

...

...

...

  • 4.x

...

Snapshot repository

...

...

Central repository

...

http://repo1.maven.org

...

Group id

...

wicket

...

Artifact id

...

wicket

...

Version

...

1.2.5

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.

The Wicket team considers Wicket 1.3 to be of beta quality. We don't expect any big API changes and are currently working to release our first beta.

Currently there is no official release available for Wicket 1.3. The only way to get to 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.

...

Subversion

...

...

Snapshot repository

...

...

Central repository

...

n/a

...

Group id

...

org.apache.wicket

...

Artifact id

...

wicket

...

Version

...

1.3-incubating-SNAPSHOT

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

Code Block
xml
xml

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

Wicket 2.0

Wicket 2.0 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.

The Wicket team considers Wicket 2.0 to be of alpha quality. We expect minor API changes while we are adding new features. Currently we are trying to get our first beta release of Wicket 1.3 out, so development on 2.0 has slowed down, but is still ongoing.

Currently there is no official release available for Wicket 1.3. The only way to get to 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.

...

Getting Wicket 1.2.5 using Maven

...