So I figured out the answers to my issues.
For issue #2 (skipping gwt-compile if only my client-side classes have
changed), I created a new variant of DebugMojo called
DebugSkipCompileMojo with @goal set to debugskipcompile. I had to set
the superclass to AbstractGWTMojo and stick most of the code from
GWTMojo and DebugMojo into my new class because the gwt-compile goal
was being run based on annotations in GWTMojo. If other people like
this idea, this should probably be refactored a little bit.
For issue #1, I had to make another change to the code - I changed the
command line options in AbstractScriptWriter.writeRunnableScript to
this:
"-Xdebug -Xnoagent -Djava.compiler=NONE -
Xrunjdwp:transport=dt_socket,server=n,address="
Previously, it was "server=y". And this is probably something that
should be a parameter.
Back in NetBeans, in Project -> Properties -> Actions, I added an
action "Debug GWT Shell" with the following parameters:
Execute Goals: compile com.totsp.gwt:maven-googlewebtoolkit2-
plugin:debugskipcompile
Set Properties: debugPort=${jpda.address}
jpda.listen=true
debugSuspend=true
The NetBeans debugger automatically connects once the GWT Shell is up.
I've done this based on the code in the 2.0-mr-beta1 branch. If others
would like these changes I'm happy to contribute them. However... is
this project still in active development?
- CC
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
