Running Maven-based Wicket projects in Eclipse

After you have created a new Wicket project according to the Wicket QuickStart instructions, you might wonder how to setup and run the project in Eclipse. There are two ways:

Using m2eclipse and WTP

Use Eclipse IDE for Java EE Developers
Install the Maven integration for Eclipse according to m2eclipse installation guide. Maven Integration for Eclipse and Maven Integration for WTP are essential, installing the Maven POM (XML) Editor is recommended.
Import the project using File > Import > Maven projects.
Go to the Servers list (Window > Show View > Servers) and add a new server. I’m using Tomcat 6.0, but any server type should be fine:
Specify the path to your server installation and add the project to the server configuration. You need to have the Maven Integration for WTP plug-in installed, otherwise the project will not be available here:
You can run and debug the application from the servers view:

Manually without m2eclipse tooling

Create a new Eclipse configuration for your project using:
```
mvn eclipse:eclipse -DdownloadSources=true
```
Go to Preferences > Java > Build Path > Classpath Variables and configure a variable M2_REPO pointing to the Maven repository (~/.m2/repository).
Import the project using File > Import > General > Existing Projects into Workspace.
Your project should have a class Start in the test source folder (this is created by the Wicket quickstart archetype). Run this as Java application to run and debug with an embedded Jetty server.

Dominique Kraus-Ahma, 06. Februar, 18:38 Uhr

Thanks a lot,

always seeked for a way of comfortably using a maven project the "Dynamic Web Project" way and your tutorial helped a lot. Find it much more comfortable then using jetty as an embedded server.

Best whishes,

D.

J Dijkmeijer, 10. Februar, 15:14 Uhr

Hi thanks for the explanation, I'm currently running the m2 / wtp alternative, but I would like to add the wicket for debugging, setting breakpoints adding log stmts etc. What would be the quick way to do this? I failed to add wicket as a module to my parent project, because wicket has its own parent project already. Downloading the sources doesn't give me the opportunity to set breakpoints in the wicket code does it?

regards,
Jeroen

I'm looking forward to your comments:

Running Maven-based Wicket projects in Eclipse

Using m2eclipse and WTP

Manually without m2eclipse tooling

Schulungen