It is not a RuntimeException so even though you might be able to remove it from GWT emulation code, your IDE will still annoy you in calling code to either catch that exception or redeclare it because your IDE does not know that GWT emul is cheating. If that calling code is exclusively within other emulated code, then it kind of depends on how JDT behaves I guess.
But honestly, it is just an exception and I would simply add it to GWT emulation. Done. It is always preferable to have a single emulation within GWT proper instead of one emulation per project that needs it with various degrees of implementation quality. -- J. -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/188c7862-b408-467c-a140-4383cd619ca7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
