THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
The current distribution packages of webwork contain all sources, as well as all needed libraries for building jars and running. Distribution packages are found here.
The dependency resolution via Ivy is disabled by default for build from distribution package (> Webwork 2.2 Beta 4). If you need to work with the Clover and Ivy related buildfile tasks, you might want to follow the instructions below.
...
The installation is quite trivial: Put a copy of the ivy-1.x.jar found in the common directory of the opensymphony module in your $ANT_HOME/lib directory.
If you want to test the Ivy functionality, ensure you have an internet connection. Change into the webwork module directory and execute ant init (as you might guess, any other task depends on init). Ivy will now resolv all dependencies and (hopefully) download all required jars and put it into the lib directory.
See Dependencies for informations on how to integrate Ivy in your own Webwork2 based projects.
| Note | ||
|---|---|---|
| ||
Build now knows the property "skip.ivy". May be specified from build.properties file or from commandline ant execution with -Dskip.ivy=true. If set to true, dependency resolution via Ivy is omitted and build is done with current jars found in lib directory. |
JUnit and Clover
The full build process will require JUnit and Clover.
Place a copy of junit.jar (>= 3.8.1) and clover.jar (>= 1.3.9) into your $ANT_HOME/lib directory (if not already exists). If you haven't got these jars at hand, look into the lib/build directory of your webwork module after you called ant init in the step before...
Opensymphony Clover license is found in the common directory of the opensymphony module. Place the clover-license.jar into your $ANT_HOME/lib directory as well. Now you are ready to ...
...