I can confirm absolutely that swapping the GWT settings does not alter
the gwt-servlet.jar file on 3 computers I've tested it on (all winxp).

For example, trying to roll back to GWT 1.7 will result in this error
when you attempt to launch hosted mode:
[ERROR] Invalid version number "2.0" passed to external.gwtOnLoad(),
expected "1.6"; your hosted mode bootstrap file may be out of date; if
you are using -noserver try recompiling and redeploying your app

This is again fixed by replacing the gwt-servlet.jar file.

Looks like this might be the plugin eclipse failing to do something,
but I don't see any errors in the logs.

I'd expect something like this, which is what you'd get if you set the
file to read only:
eclipse.buildId=M20090211-1700
java.version=1.6.0_13
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments:  -os win32 -ws win32 -arch x86

Error
Sat Oct 17 13:45:41 WST 2009
Unexpected Exception

org.eclipse.core.internal.resources.ResourceException: Problems
encountered while deleting resources.
at org.eclipse.core.internal.resources.Resource.delete(Resource.java:
724)
at org.eclipse.core.internal.resources.Resource.delete(Resource.java:
670)
at com.google.gdt.eclipse.core.sdk.UpdateWebInfFolderCommand.execute
(UpdateWebInfFolderCommand.java:65)
at com.google.gdt.eclipse.core.sdk.UpdateProjectSdkCommand.execute
(UpdateProjectSdkCommand.java:67)
at
com.google.gwt.eclipse.core.properties.ui.GWTProjectPropertyPage.addGWT
(GWTProjectPropertyPage.java:186)
at
com.google.gwt.eclipse.core.properties.ui.GWTProjectPropertyPage.saveProjectProperties
(GWTProjectPropertyPage.java:132)
at com.google.gdt.eclipse.core.ui.AbstractProjectPropertyPage.performOk
(AbstractProjectPropertyPage.java:78)
at org.eclipse.jface.preference.PreferenceDialog$13.run
(PreferenceDialog.java:931)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at org.eclipse.core.runtime.Platform.run(Platform.java:880)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:48)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
at org.eclipse.jface.preference.PreferenceDialog.okPressed
(PreferenceDialog.java:911)
at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.okPressed
(FilteredPreferenceDialog.java:456)
at org.eclipse.jface.preference.PreferenceDialog.buttonPressed
(PreferenceDialog.java:233)
at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624)
at org.eclipse.swt.widgets.TypedListener.handleEvent
(TypedListener.java:228)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:
3823)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3422)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
at org.eclipse.jface.window.Window.open(Window.java:801)
at
com.google.gdt.eclipse.core.actions.AbstractProjectPropertiesAction.run
(AbstractProjectPropertiesAction.java:56)
at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:
251)
at
org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection
(ActionContributionItem.java:583)
at org.eclipse.jface.action.ActionContributionItem.access$2
(ActionContributionItem.java:500)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent
(ActionContributionItem.java:411)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:
3823)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3422)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2384)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2348)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2200)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:495)
at org.eclipse.core.databinding.observable.Realm.runWithDefault
(Realm.java:288)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench
(Workbench.java:490)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:
149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start
(IDEApplication.java:113)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run
(EclipseAppHandle.java:193)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication
(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start
(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run
(EclipseStarter.java:386)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run
(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
Contains: Could not delete 'C:\Workspace\UnitTest\war\WEB-INF\lib\gwt-
servlet.jar'.

The issue you've mentioned doesn't seem to be directly related
(although it is also an  issue when you swap over to 2.0 ms 1);
cleaning the project (removing all files) and rebuilding fixes any
issues with the nocache.js files in the project for me... but I guess
that's what I'd expect to have to do once I change libraries...

On Oct 15, 9:29 pm, Rajeev Dayal <rda...@google.com> wrote:
> Hey dougx,
> Are you using the Google Plugin for Eclipse? If so, switching the SDK should
> update the gwt-servlet.jar in your war/WEB-INF/lib folder. However, there is
> another issue that you'd run into:
>
> http://code.google.com/p/google-web-toolkit/issues/detail?id=4126
>
>  <http://code.google.com/p/google-web-toolkit/issues/detail?id=4126>Rajeev
>
> On Thu, Oct 15, 2009 at 6:16 AM, dougx <douglas.lin...@gmail.com> wrote:
>
> > Seems that because I was trying to switch an existing eclipse project
> > over to the new version my war/WEB-INF/lib/gwt-servlet.jar was still
> > the 1.7 version; replacing it with the same file from 2.0 ms1 archive
> > fixed the problems I was having.
>
> > (Well... the browser still doesn't launch automatically, but if you
> > start it manually it'll actually connect and do debugging, etc. now.)
>
> > Kind of lame that doing a project-clean in eclipse doesn't clear and
> > redeploy those files; and that the browser plugin doesn't seem to
> > output any kind of debug log / warning that you're being a dork (there
> > should always be dork warnings... :D); this is a problem that a
> > looooooooooooooooot of people seem to be running into (according to
> > the comments here anyway:
> >http://code.google.com/p/google-web-toolkit/wiki/UsingOOPHM)
>
> > Still, it's early release. Just glad I got it working!
>
> > ~
> > Doug.
>
> > On Oct 15, 3:21 pm, Paul Robinson <ukcue...@gmail.com> wrote:
> > > It used to be the case that the server would start firefox with the
> > > appropriate URL for you, but that didn't always work too well. They
> > > fixed this by removing the attempt to start firefox altogether - you
> > > have to start the browser yourself and point it at the URL you're given.
>
> > > dougx wrote:
> > > > Just installed the GWT 2.0 MS1 && OOPHM plugin for firefox, and I
> > > > can't get it to work in development mode.
>
> > > > The webserver simply sits there and reports:
> > > > 00:00:02.844 [INFO] Waiting for browser connection to
> > > >http://localhost:8080/Demo.html?gwt.hosted=10.12.18.76:9997
>
> > > > This is odd, because I've tried with the chrome and ie plugins as
> > > > well, and get the same thing.
>
> > > > I've tried adding 10.12.18.76 and localhost to the list of accepted
> > > > servers in the plugin options, but that doesn't seem to do anything...
>
> > > > I've also tried telnet'ing into 10.12.18.76:9997 and the server
> > > > reports:
> > > > 00:02:11.797 [INFO] Connection received from ws211.win2k.intranet.org:
> > > > 4140
>
> > > > So it seems the server is up and listening; the plugin just isn't
> > > > talking to it...?
> > > > Anyone had similar troubles?
>
> > > > ~
> > > > D.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to