maybe you can use a
"-server com.google.gwt.dev.shell.jetty.OurJettyLauncher" argument to launch
gwt.
below is the source of OurJettyLauncher:
package com.google.gwt.dev.shell.jetty;
import com.google.gwt.core.ext.TreeLogger;
import org.mortbay.jetty.webapp.WebAppContext;
import java.io.File;
public class OurJettyLauncher extends JettyLauncher {
protected WebAppContext createWebAppContext(TreeLogger logger, File
appRootDir) {
WebAppContext webAppContext = super.createWebAppContext(logger,
appRootDir);
String webXmlPath = System.getProperty("webXml");
if (webXmlPath != null && !"".equals(webXmlPath)) {
webAppContext.setDescriptor(webXmlPath);
} else {
webAppContext.setDescriptor("WEB-INF/boot.web.xml");
}
return webAppContext;
}
}
On Sat, Apr 23, 2011 at 5:22 PM, Thomas Broyer <[email protected]> wrote:
>
> Why aren't you simply renaming your debug module to the same name as the
"production" one?
>
> --
> You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" 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/google-web-toolkit?hl=en.
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" 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/google-web-toolkit?hl=en.
