Versions Compared

Key

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

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 

Latest stable release

1.24.68

(from SourceForge; this release is neither affiliated with nor endorsed by Apache in any way) the Apache Software Foundation)

Archived Latest beta release

1.3.0-beta-27

(from the Apache Software Foundation)

For new projects, we We recommend you start with our latest beta 1.4 release. It's pretty stable - lots of people are using it on live production sites with no issues. 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.0.x, we haven't decided the numbering scheme quite yet).

Important note about logging dependencies for 1.3.0 and later.

...

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

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

Code Block
xml
xml
<dependency>
    <groupId>wicket</groupId>
    <artifactId>wicket</artifactId>
    <version>1.2.6</version>
</dependency>

Or for 1.3.0-beta2:

Code Block
xmlxml

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

For the SLF4J log4j binding (you don't need this for 1.2.x; see above):

Code Block
xml
xml
<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:

...