Page History

...

• The good news, all that waiting wasn't in vain, as you should now have a fully checked out, dependency managed, built, possibly working, Wicket code base. You can sanity test it by running the unit tests (how?)
  or building a quickstart. (more)

Kick the tires

• Crate a Quickstart via the wicket-archetype-quickstart
• Navigate to the pom.xml in your Quickstart project.
• Set version element to the same value as the one found in the Wicket project pom.xml (e.g. 1.4-SNAPSHOT)
• The plugin should automagically resolve the quickstart's Wicket dependency from the project rather than a .jar
• Find WicketApplication.java
• Click through to WebApplication class from the extends section of the class definition.
• If all is well, you should be taken to the Wicket project .java version of WebApplication rather than a .class file from a .jar

Proving a bug exists

• Writing a unit test with WicketTester

...