To update this one, it seems a bug in the GWT Eclipse plugin was getting
me. I had several projects with GWT modules open. When making a new
WebApplication launch config, setting the Project: to say Project A,
Main Class: to DevMode, selecting module A in GWT Available Modules
and hitting
On Monday, September 24, 2012 9:59:00 PM UTC+2, Joseph Lust wrote:
We've been working with *rename-to* so that our apps (many submodules)
don't all have ugly, huge urls with the full package name in them. This is
working well, however when we switch to DevMode, it won't run. DevMode
We've been working with *rename-to* so that our apps (many submodules)
don't all have ugly, huge urls with the full package name in them. This is
working well, however when we switch to DevMode, it won't run. DevMode
appears highly dependent on guessing the location of the X.gwt.xml file
based
On 24 September 2012 12:59, Joseph Lust lifeofl...@gmail.com wrote:
We've been working with rename-to so that our apps (many submodules) don't
all have ugly, huge urls with the full package name in them. This is working
well, however when we switch to DevMode, it won't run. DevMode appears
Thanks Hilco,
We run via the *RunAsWebApplication *option which uses the Eclipse GWT
Plugin to run it. This throws various errors, though I don't have the
output with me. It is to the extent of cannot find X.gwt.xml on
classpath. You can start grafting things onto the classpath, but I assumed
Hm we use DevMode and rename-to and never had any problems with it. We have
something like App.gwt.xml, DevApp.gwt.xml (contains logging and inherits
App.gwt.xml), DevAppGecko.gwt.xml (contains use.agent and inherits
DevApp.gwt.xml) and all have the same rename-to=app attribute, so we
don't
