Monday, December 3, 2012

Checking client-side code compilation before deployment

I occasionally use API in my client or shared code that is not supported
by GWT's Java-to-Javascript compiler. But I usually only notice this
when I try to run it in a browser, via "mvn gwt:run" (I use maven), when
I see some error about Gwt.Bridge being unable to instantiate something.

These errors seem to happen during some post-deployment compilation
phase rather than when the code is actually run.

I can avoid this by adding a GwtTest unit test for each part of the
code, and I should have those tests anyway. But isn't there some general
way to check that all my client and shared code is OK?

--
murrayc@murrayc.com
www.murrayc.com
www.openismus.com


--
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+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.

No comments:

Post a Comment