THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
When you build from SVN you will need to should check out a the whole branch, because our project of trunk or the selected branch as the project consists of various modules that may depend on one another. For Wicket the current (1.x 4) development branch, you will need to check out:
svn co http://svn.apache.org/repos/asf/wicket/trunk
This will give you a directory structure like the following directory tree:
- wicket-1.x
- wicket-1.x/wicket
- wicket-1.x/wicket-extensions
- wicket-1.x/wicket-spring
- wicket-1.x/wicket-auth-roles
- wicket-1.x/wicket-examples
- wicket-1.x/wicket-spring-annot
- ...
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 top-level project doesn't have sources for itself.
...
The current development version of Wicket requires at least jdk 1.5.
svn co http://svn.apache.org/repos/asf/wicket/trunk
If you want to ensure that your Wicket version is built using JDK-1.5 and fully compatible with that Java version, you will need to build it with a Java 1.5 compiler and runtime library.
...
Commandline | Description |
|---|---|
mvn clean | cleans up build artifacts |
mvn compile | compiles the projects |
mvn package | creates the jar files in the target/ subdirectories |
mvn install | installs the jar files in your local repository |
mvn -Prelease package | generates the javadoc/source jars as well |
You can just run the install target, as Maven will build the previous stages automatically.
...
| Code Block |
|---|
mvn -Dmaven.test.skip=true install |
Of course, all limits bets are off then and your mileage may vary if you use such a built jar.
...