Report a Bug
Wicket manages bug reports via the Apache Jira site:
http://issues.apache.org/jira/browse/WICKET
Build a Quickstart
See http://wicket.apache.org/quickstart.html
The maven command provided there is the quickest way to get a working Wicket project that you can use to clearly demonstrate a bug.
Once you have an example that shows the minimum conditions under which the issue occurs, then you can zip up the project and attach it to the relevant issue.
When a Wicket dev asks you to submit a quickstart, that is what they mean.
That is far more useful than posting reams of your application code and telling everyone it doesn't work. The former will help diagnose the problem, the latter will mainly get you abused on the mailing list.
Submit a patch
This is the most involved, but the most rewarding route .
In a nutshell this involves:
- Checking out the Wicket source code from the Subversion repository.
- Building it via mvn or IDE plugin.
- Proving the bug exists, either via a Quickstart, or writing a unit test.
- Submitting your fix as a Subversion patch file.
Checking out Wicket from Subversion
see: http://wicket.apache.org/building-from-svn.html