Wicket manages bug reports via the Apache Jira site
It requires you to register with the site, to avoid spamming, and attribute credit where its due. It's relatively painless. Much harder is writing a clear and concise bug report.
Etiquette for a bug report is:
You will be rewarded with subtle kudos and the bug is much more likely to be fixed promptly.
See getting started for a good introduction to building a barebone Wicket project from one command. There is even a tool to let you customise the command for your project.
Or you can watch Al Maw's excellent screencast covering the whole process of installing and running Maven, and getting your Eclipse workspace set up.
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.
This is the most involved, but the most rewarding route ;-). In a nutshell this involves:
This guide will outline how to do it with Eclipse + Subclipse + m2eclipse. If you prefer the command line, then start here: building from source If you can provide a walk through for your IDE of choice then please do add it.
Using an Eclipse 3.4.x flavour of your choice add install the following plugins
I usually install the entire Subclipse plugin, and all of m2eclipse except the Project configurators unless I am using a J2EE version of Eclipse. I had a spurious error when adding the m2eclipse update site, “No repository found at http://www.md.pp.ru/~eu/12/” but it didn't cause any problems with the install.
Add the Wicket Subversion repository - Navigate to Window > Show Perspective > Other... > SVN Repository Exploring (eclipse uses the term perspective to mean a collection of views, and a view is one single panel with some specific function like the navigator view or the editor view) In the SVN Repositories tab on the left, right click > New > Repository Location... and paste in the repository url: http://svn.apache.org/repos/asf/wicket
Checkout the code - Click on the new Repository and navigate to: trunk
right click > checkout as maven project. Some serious churning will now occur as you download of Wicket source, and then maven crawls the internet for all the required libraries. Seriously, go for a stroll in the sunshine; the checkout and build took about 6minutes on my machine, and thats without maven needing to download anything.
Building Wicket - All that waiting wasn't in vain, as you should now have a fully checked out, dependency managed, built, possibly working, Wicket code base.
Extract your changeset into a patch file - As we don't all have commit access to the svn repository, we need some other way of getting our changes to the developers. This is done by making an svn patch file, essentially a plain text diff, with some subversion specific formatting. With the Subclipse plug-in creating a patch file is as simple as:
Team > Create Patch...
Next >