qwicket: A successful built, and war deployment

The web applications generated by qwicket (0.2) still don’t run out of the box. As I tried to run the build.xml file, which was suppose to download the dependencies and build the war file, the built resulted unsuccessful. So, I had to get my hands dirty, and manually download the jar files and resolve the dependencies (including versoning issues of different jars with each other).

Firstly, I had to turn off the auto jar download during build process. I did it by adding this line in build.properties file:

build.offline=true

And then went through the build process, and resolved the errors by providing required jar files. These are the jar files that I added:

antlr-2.7.5H3.jar
asm-2.2.jar
cglib-2.2_beta1.jar
commons-collections-2.1.1.jar
commons-dbcp-1.2.1.jar
commons-email-1.0.jar
commons-logging-1.0.2.jar
commons-pool-1.2.jar
dom4j-1.4.jar
ehcache-1.2.jar
ejb3-persistence.jar
hibernate-3.2.0.cr1.jar
hibernate-annotations-3.1beta9.jar
jetty.jar (6.0.0beta17)
jta.jar
mysql-connector-java-3.1.12-bin.jar
servlet-api-2.5.jar
spring-1.2.6.jar
wicket-1.2.jar
wicket-extensions-1.2.jar
wicket-spring-1.2.jar
wicket-spring-annot-1.2.jar