These are the various dependencies required by Wicket.
If you're using maven to build your project and just want to know what dependencies to add to your POM, just scroll down to the next section.
The following list of JAR dependencies are required in order to be able to use Wicket. These dependencies are also needed in the build process.
| Required JARs | Description |
|---|---|
| wicket-${pom.currentVersion}.jar | The main Wicket classes |
| ${dep.artifact} | ${dep.getProperty('wicket.description')} |
The following JAR dependencies are optional. This means that depending on your situation you might need (one of) these jars to use Wicket to the fullest.
| Optional JARs | Description |
|---|---|
| ${dep.artifact} | ${dep.getProperty('wicket.description')} |
The following depenencies are only used when you are building Wicket yourself. These libraries are not necessary to create Wicket applications.
| JARs for buiding Wicket | Description |
|---|---|
| ${dep.artifact} | ${dep.getProperty('wicket.description')} |
If you are using maven to build your project then you can simply cut and paste the following dependencies into your project.xml.
Note that if you are reading this on the Wicket website then the version numbers reflect what is currently in CVS, not necessarily what versions are in use in the distribution that you have downloaded. In particular, the version number for Wicket itself may not reflect a version currently available in the maven repository.
If you are reading this from the documentation that came bundled with a particular distribution of Wicket then you can use these values without modification.