I want to start using JPA with Wicket, and the quickest way was to start with Qwicket, a project that already has done the heavy lifting. I wanted to be able to build and run my maven-managed application from eclipse. And lastly, I wanted to use MySQL. Qwicket does come with maven support, but it's managed from an ant script. I wanted native maven support. Here's what I did to change qwicket so it fits my requirements:
Generic Debugging
Select break points in the code you're are going to run.
Run Maven in debug mode, e.g mvn-debug install
Attach the debugger to the running maven by selecting the "Maven" debug configuration created above.
Eclipse will now stop Maven at the breakpoints you have enabled.
This article show you how you can fix bugs for maven-plugins (eclipse setup for hacking the code, debugging etc.) with a concrete project: maven-eclipse-plugin. Lets start …