[
http://jira.codehaus.org/browse/MGWT-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nicolas de loof closed MGWT-139.
--------------------------------
Resolution: Won't Fix
Assignee: nicolas de loof
Sorry, the gwt hosted mode design simply makes impossible to embedd into the
same JVM. GWT code requires a flat Classloader structure and does a
System.exit() at end, killing the host process
> Improve debugging in eclipse
> ----------------------------
>
> Key: MGWT-139
> URL: http://jira.codehaus.org/browse/MGWT-139
> Project: Maven 2.x GWT Plugin
> Issue Type: Improvement
> Affects Versions: 1.1
> Environment: windows xp, Java 1.6, eclipse, GWT 1.7.1
> Reporter: Gergely Kiss
> Assignee: nicolas de loof
>
> Currently the gwt:debug goal only supports remote debugging in eclipse. I
> have to specify a port number, start the m2eclipse launch config, create
> another launch config for remote debugging and start that as well.
> I believe this is quite cumbersome - not to mention whenever I stop the
> gwt:debug process (using eclipse's red button), the forked hosted browser
> continues to run, and I have to manually kill the java process.
> I wonder if running the hosted browser in the same process as maven (ie not
> forking) is a feasible solution?
> Anyways, I would really appreciate some more options (a fork=false, and maybe
> overriding the GWT command line) in the gwt:debug and gwt:run goals, so I can
> configure them to match our development use cases.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
