Page History

...

• 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

seeThis guide will outline how to do it with Eclipse + Subclipse + m2eclipse.
If you prefer the command line, then start here: http://wicket.apache.org/building-from-svn.html
If you can provide a walk through for your IDE of choice then please do add it.

Setting up

Using an Eclipse 3.4.x flavour of your choice add install the following plugins

• Subclipse for accessing Subversion - Eclipse update site URL http://subclipse.tigris.org/update_1.6.x^{Image Added}
• m2eclipse for maven support - Eclipse update site: http://m2eclipse.sonatype.org/update/^{Image Added}

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/^{Image Added}" but it didn't cause any problems with the install.

Checking out Wicket from Subversion

• 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^{Image Added}

Building Wicket

Proving a bug exists

...