Have you tried the "gwt:debug" goal? That should work just fine to debug the client side (if you use noserver then the server side is up to you, but can also be debugged the same way, connecting to a remote process).
On Oct 4, 5:28 pm, Edoardo Ceccarelli <[EMAIL PROTECTED]> wrote: > Hi, > > I have managed to configure the gwt-maven plugin under eclipse, with > the latest version of the gwt-maven archetype (1.0.1) > I use jetty setting the "noserver" option in the pom. > From eclipse I first launch the goal jetty:run-war and then gwt:gwt > The gwt shell pops up and is properly linked to the source (if I edit > the client side of the app I get instant changes in the gwt shell), > what I really cannot manage to do in this configuration is to debug > the gwt side of the app (debugger simply doesn't stop at the > breakpoints) . > > I have tried both with external maven and with m2 plugin in eclipse, > result doesn't change > > Maybe there is a place in the plugin where to set the -out ./ > WebContent parameter? > > Any help appreciated > Edoardo --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "gwt-maven" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/gwt-maven?hl=en -~----------~----~----~----~------~----~------~--~---
