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)
--
Thomas Broyer
/tɔ.ma.bʁwa.je/