IDE Support for Wicket development
For all leading IDE’s support is under development. Here’s a list of efforts for the major IDE’s.
- Eclipse: Qwickie, Wicket Source
- Netbeans: NB Wicket Support
- IntelliJ IDEA: Wicket Forge, Wicket Source
These projects are not maintained or supported by the core Wicket team, but by their respective development teams.
Setting up your IDE
Taking Maven, project configuration files for Eclipse can be generated with:
Maven will add all the necessary JAR files to the project’s classpath. Now the sources can be imported in Eclipse using the “Existing Projects into Workspace” wizard.
If not already present the
M2_REPO classpath variable has to point to your local Maven repository. The repository is typically found in
C:\Documents and Settings\<username>\.m2\repo or (for unix buffs)
~/.m2/repo. It can be set within Eclipse (Preferences->Java->Build Path->Classpath Variables) or with the help of Maven:
mvn -Declipse.workspace=<path-to-eclipse-workspace> eclipse:add-maven-repo
If you want to go along with the Wicket way of code formatting you should import the Wicket code format profile into your workspace (Preferences->Java->Code Style->Formatter), found in:
Finally configure the editor to automatically format all edited lines and organize imports on save (Preferences->Java->Editor->Save Actions).
NetBeans comes with Maven integration. Further help can be found at their Wiki
IntelliJ IDEA comes with Maven support too.
With the Eclipse Code Formatter plugin the Wicket format profile can be used in IntelliJ IDEA too. Configure the IDE to prevent star imports (Settings->Code Style->Imports).