Great! Do you think that's something that should be run by default when someone builds a GWT library? (integrated in the lifecycle of the gwt-lib maven packaging) or it would be better left as an optional additional feature? Are you using it at Google? or are you rather relying on unit-tests? (or compilation failures in downstream GWT applications?) See https://github.com/tbroyer/gwt-maven-plugin/issues/4
(note: apparently, JSORestrictionsChecker is run as part of the CompilationStateBuilder, so IIUC it's run as part of -validateOnly) On Thu, Jun 6, 2013 at 4:23 AM, Ray Cromwell <[email protected]> wrote: > I haven't look at the code, but I think it runs a precompile, and then > stops. So it constructs the whole program AST and runs generators, so it > runs all checking up to that point. I'm pretty sure it should be running > JSORestrictionsChecker which runs on JDT I believe. > > > > > On Wed, Jun 5, 2013 at 6:25 PM, Thomas Broyer <[email protected]> wrote: >> >> Hi, >> >> Anyone knowns what the -validateOnly flag to the compiler does exactly? >> can it be reliably used to validate that all classes in a given module are >> translatable? >> I used it once but it was years ago so I don't remember what it checked >> exactly. AFAICT it didn't check that JSNI was valid JavaScript >> (understandable and not a blocker: if you have JSNI in a lib you should >> probably have unit-tests too) >> >> See also http://stackoverflow.com/q/16944701/116472 > > -- Thomas Broyer /tɔ.ma.bʁwa.je/ -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- 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]. For more options, visit https://groups.google.com/groups/opt_out.
