Monday, September 9, 2013

GWT Compile project errors

When doing a GWT compile project, I was always curious about the 14 errors that were supressed.  At runtime they don't seem to cause a problem, but what are they all about?  So today I tried a compile with the -strict option, and got a whole load more errors than 14.  For example:

Compiling module uk.co.ricoh.ppbg.sd.shark.ui.SharkUI
   Validating units:
      [ERROR] Errors in 'file...'
         [ERROR] Line 19: No source code is available for type org.junit.Assert; did you forget to inherit a required module?
         [ERROR] Line 22: The method format(String, NlsMessageBean.NlsKeyword, String) is undefined for the type String

So firstly, is -strict the correct thing to do to investiagte the 14 errors?  And secondly, why am I getting errors like that shown above for code that is implemented in the server side part of the project?  That should not be compiled to JS?  But how does GWT know not to do that?

Thanks
Simon

--
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 google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/groups/opt_out.

No comments:

Post a Comment