Page History

...

For more information on the project structure, please read the 'Better Builds With Maven'
book which has a detailed description on how to structure a maintainable, enterprise ready
build. The book is available for free from the Mergere website.

...

When you build from SVN you will need to check out a whole branch, because our project depend
on one another. For Wicket 1.x you will need to check out:

...

In this document we focus at the maven project descriptor located in the top level directory,
which enforces default settings for all Wicket projects such as plug-in settings, versioning
of the Wicket projects, managing the various dependencies and more.

The artifacts in this project are there only for having a consistent build. This project
doesn't have sources for itself.

...

The build has two parts: a Java 1.4 part for the projects that are Java 1.4 based and
a Java 5 part, specific for the projects that are Java 5 based. The corresponding projects
reside (you guessed it!) in the jdk-1.4 and jdk-1.5 sub directories.

...

If you want to ensure that your Wicket version is built using JDK-1.4 and fully compatible with that Java version,
you will need to build is it with a Java 1.4 compiler and runtime library. Maven is set up so that it will only build
the JDK-1.4 projects when it is started using a 1.4 Java version.

...

This will compile, test, package and install all Wicket projects. Installation means putting the jar files into your
local Maven repository, including the source and javadoc jars.

...

Now you have built your own fresh Wicket jar you must be anxious to use it. This is now as simple as adding
a snapshot dependency on the specific Wicket version. So in your pom.xml you can use:

...

One thing you need to make sure is that you have set the M2_REPO classpath variable in
Eclipse (or a similar construct in Netbeans), and point it to your local repository, typically found in
C:\Documents and Settings\username\.m2\repo or (for unix buffs) ~/.m2/repo

...