| Apache Wicket > Index > GHOP - quickstart |
This page is a copy of http://cwiki.apache.org/confluence/display/WICKETxSITE/Quickstart and created for a task of the Google GHOP initiative. This page should be edited by the claimant of the GHOP task and provided with a way to generate the maven commandline.
This guide is intended to get you up and running & using Wicket within minutes.
It uses a Maven Archetype to create a Wicket QuickStart project, so requires that Maven 2 be installed & configured beforehand.
This project provides a starting point for your Wicket project. If you are looking for examples, please refer to the wicket-example projects instead!
To create your project, copy and paste the command line generated after typing in the groupId, artifactId and version.
This will produce the following project structure/files
.\myproject
| pom.xml
|
\---src
+---main
| +---java
| | \---com
| | \---mycompany
| | HomePage.html
| | HomePage.java
| | WicketApplication.java
| |
| +---resources
| | log4j.properties
| |
| \---webapp
| \---WEB-INF
| web.xml
|
\---test
\---java
\---com
\---mycompany
Start.java
Change into the project directory, then create a WAR file via mvn package or build the project and run it under Jetty via mvn jetty:run.
This will compile the project then deploy it to an embeded instance of the Jetty servlet engine, which will be use on port 8080, by default. As a result, once running, your application will be available at http:localhost:8080/myproject.
See the Jetty plugin documentation for configuration options, etc.
At present, running mvn package or mvn install will result in a NPE from the Surefire (testing) plugin as the generated pom.xml has no dependency on either JUnit or TestNG, which the plugin appears to expect if a src/test/java path is present. To avoid this issue, simply add the following to the <dependencies> section of the pom.xml.
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>3.8.2</version>
<scope>test</scope>
</dependency>