> ...and has been compiled with GWT 1.6 ?
> Could it be the hosted.html from a previous GWT 1.5 deployment that's
> cached in the browser? (reported in another thread)
Hi,
the server is a brand new platform that contains just the new project
files.
I'm pretty sure the Eclipse plugin is bound to use GWT 1.6 but I'll
check again
> Do you have an error message ?
No, debugging just doesn't start
> I've added a -whitelist argument to my launch, otherwise I had a
> confirmation from the hosted mode to reach my distant server, could it
> be your problem? (with an additional issue that the prompt do not
> show)
I've added the whitelist option
> > Are you guys finding any problems with it?
>
> No problem at all; works like a charm (both using the Google Plug-in
> for Eclipse and a .launch file that I had for GWT 1.5 and which I've
> adapted for GWT 1.6; this is where my -whitelist lived)
I'll try with a brand new project and I'll try to debug the javascript
in Firefox. It should be easy, shouldn't it? :-)
Thanks,
E.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
