Closed GoogleCodeExporter closed 8 years ago
Original comment by rdayal@google.com
on 31 Oct 2013 at 6:02
It appears that you can work around this by ... ignoring it.
From the Preferences, go to Google > Errors/Warnings. Under Project Structure
and SDKs, set Invalid SDK to either Ignore or Warning.
Of course, this is just a workaround, and may skip other important warnings,
but it does permit Dev Mode and the GWT Compile operations to behave correctly.
Original comment by niloc132@gmail.com
on 11 Nov 2013 at 6:33
Rajeev: What are the chances of this being fixed in the near future? Should we
add About.GWT_VERSION_NUM back for the 2.6 release? (We're hoping to release
GWT 2.6.0 in the next few weeks.)
Original comment by mdemp...@google.com
on 13 Nov 2013 at 11:55
They are good. I'm aiming to put a release out towards the middle of next week.
Original comment by rdayal@google.com
on 14 Nov 2013 at 5:53
Original comment by rdayal@google.com
on 25 Nov 2013 at 3:52
Any idea when this will appear on the update sites? This was marked fixed on
Monday, but Eclipse Juno is still not showing an available GPE update.
Original comment by jdou...@basis.com
on 29 Nov 2013 at 6:19
Getting ready to try and use 2.6.0 RC1 here on Eclipse on a new project and
have run into this issue. I also currently use JUNO because Kepler does "window
to front on mouse focus" behavior when my desktop is configured for "mouse
follows focus" which breaks my workflow.
Original comment by mich...@newsrx.com
on 3 Dec 2013 at 7:52
@michael, this is a side issue, but RC2 was just released.
https://code.google.com/p/google-web-toolkit/downloads/list (but I'm in the
same position of being unable to test it).
Original comment by jdou...@basis.com
on 3 Dec 2013 at 7:56
No change for needing the workaround in Eclipse at this point.
Original comment by mich...@newsrx.com
on 4 Dec 2013 at 3:07
GWT 2.6.0 RC3 is released and it seems GWT_VERSION_NUM is back. No need to wait
for plugin update
Original comment by oleg.lya...@wolery.org
on 5 Dec 2013 at 6:55
Original comment by rdayal@google.com
on 20 Dec 2013 at 9:04
Original issue reported on code.google.com by
jens.neh...@gmail.com
on 30 Oct 2013 at 5:25