In some few situations (like adding/removing modules in the run configuration) I remember that the command line parameters for DevMode were messed up by the Google Eclipse Plugin and you had to correct them manually. But that has happened quite some time ago and it never happened again since then. It's pretty much what has been said in comment 6 in your linked bug report I guess. Have you carefully checked the command line parameters for DevMode in your run configuration?
-- J.
Thanks Hilco,We run via the RunAs>WebApplication 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 the Google Plugin would be smart enough to work with it's own rename-to configuration.Also, we use DevMode in a remote (aka external) tomcat setup. We have the UI calls sent to the DevMode plugin, but the RPC's go to the running tomcat. That way we don't need to bring the whole system up and down to just mess with the UI (OSGi implementation of GWT/Spring backend with 30 subapps). However, this just won't jive using rename and the only option we see at the moment is to keep using the old/nasty long urls. :(Thanks for any insights.Sincerely,Joseph
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/gXUjW2YtB7gJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
No comments:
Post a Comment