So you chose not to use one of the ready to use Maven archetypes, but rather roll things on your own. While possible, it needs some close attention to make things work properly. Most notable things you need to take care of are:
While we are adamant users of Apache Maven and its build infrastructure, this may not be to everyone's liking. However, if you wish to learn all about which dependencies you need for your Wicket project, we ask you to learn to read the POM file format and retrieve the required versions stated there. We take great care to keep the POM files up to date with the latest and greatest of each dependency.
At a minimum a vanilla Wicket application requires for compilation:
WicketTester
to test your pages and componentsAt a minimum a barebones Wicket application requires the following at runtime:
As of Wicket 1.3.0, Wicket uses the SLF4J project for logging. SLF4J is similar to commons-logging, in that it allows libraries/frameworks like Wicket to avoid forcing a choice of logging framework on their users.
You cannot use Wicket without adding an SLF4J logging implementation to your classpath. Most people use log4j. If you do, just include slf4j-log4j12.jar
on your classpath to get Wicket to use log4j too. If you want to use commons-logging or JDK14 logging or something else, please see the SLF4J site for more information.