On Monday, April 20, 2015 at 12:34:08 AM UTC+2, Anderson Vasconcelos Pires wrote: > > This problem is happening with me too. Should we give up of GWT? >
Obviously not! “Just” update to 2.7 and use SuperDevMode. (SuperDevMode can be used since 2.5, but is really *usable* since 2.7) I must say I don't quite understand: the plugin no longer works in Firefox for more than a year now, and you only notice *now* that "classic" DevMode is "deprecated"?! > > Em sexta-feira, 17 de abril de 2015 12:17:44 UTC-3, Thomas Broyer escreveu: >> >> >> On Friday, April 17, 2015 at 5:12:09 PM UTC+2, Chad Baker wrote: >>> >>> I've been working with this plugin, using Dev Mode Classic for several >>> weeks without issues. All of a sudden, this morning, it now continually >>> prompts me to install the plugin, even though it already has been. I have >>> rebooted, uninstalled/re-installed first the plugin, then Chrome itself. Is >>> it possible a recent plugin update broke the plugin? Does anyone have any >>> ideas? Thank you in advance! >>> >> >> A recent plugin update? The plugin hasn't been updated for a while (since >> Classic DevMode is deprecated, and even before that: >> https://gwt.googlesource.com/gwt-plugins/ ) and the Chrome Web Store no >> longer accepts extensions with NPAPI plugins for about a year already. >> >> No, what happened is a Chrome update: >> http://googlechromereleases.blogspot.fr/2015/04/stable-channel-update_14.html >> >> (see the comments, there's a temporary workaround… until September…) >> > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
