Yeah thats my preferred approach also.
Timo Rantalaiho wrote:
On Thu, 21 Aug 2008, Oleg Taranenko wrote:
Eclipse Ganymede JEE (3.4) + m2eclipse 0.9.5 works perfect!
I can now under eclipse launch mvn jetty:run and comfortable
debugging all sources including the wicket core.
One
On Fri, Aug 22, 2008 at 5:04 AM, Timo Rantalaiho [EMAIL PROTECTED] wrote:
I don't really see why would you want to have Maven in
between your IDE and the servlet container.
I Agree. Just use the wicket quickstart archetype generator and look
at the Start class in the src/test/java directory
Hi,
On Fri, Aug 22, 2008 at 9:49 AM, Martijn Dashorst
[EMAIL PROTECTED] wrote:
On Fri, Aug 22, 2008 at 5:04 AM, Timo Rantalaiho [EMAIL PROTECTED]
wrote:
I don't really see why would you want to have Maven in
between your IDE and the servlet container.
I Agree. Just use the wicket
I use NetBeans and have written a custom Maven plugin that converts a POM to
a NetBeans project, works well with the Wicket quickstart, Start class,
hot-deploy and all. Also generates a build.xml file for those who miss using
Ant instead of Maven. No Maven IDE plugin required.
Details here:
Hello all,
sorry for reviving archaic thread, but right now i've tried the
combinamtion eclipse + m2eclipse again.
Eclipse Ganymede JEE (3.4) + m2eclipse 0.9.5 works perfect!
I can now under eclipse launch mvn jetty:run and comfortable
debugging all sources including the wicket core.
One
On Thu, 21 Aug 2008, Oleg Taranenko wrote:
Eclipse Ganymede JEE (3.4) + m2eclipse 0.9.5 works perfect!
I can now under eclipse launch mvn jetty:run and comfortable
debugging all sources including the wicket core.
One suggestion, may establish the maven archetype to generate the
m2eclipse
Helloall,
Sorry for bothering, may be somebody could help. I'm developing web apps under Eclipse. Early I'm using the mvn eclipse:eclipse + jetty launcher plugn. Now i try to use m2eclipse plugin and webapp is started using m2's goal mvn jetty:run. The application works, but when I want to
You don't need the jetty launcher plugin, in fact I'd recommend using the
embedded jetty starter we provide with the quickstarts.
Right click the start class, select debug as application and go...
Also the mvn jetty:run plugin is not really useful for development in my
opinion. It is a nice maven
Hello Martijn,
Jetty launcher has some advantages though, i.e. it allows to set up different context path/port for the projects without changing source code. Thus i can simultaneously run and debug its. If not this annoying bug, i found development with m2eclipse more convenient. I hope the
