But I have to go back to my original question: Wouldn't it be theoretically trivial to simply strip out the offending classes from gwt-dev.jar in the process of publishing a GWT 2.9.0?
That would break everyone using current GWT SDK. repackaging into a different package would be the better option.
You can download and use the GWT artifacts published to Maven Central (https://search.maven.org/search?q=g:com.google.gwt) which do not include the offending classes. However you must provide these classes manually then as additional jars on your class path.
The only thing that is still packaged with gwt-dev.jar from Maven Central is a patched version of Eclipse JDT compiler.
And is there seriously no way to tell the "Validating GWT components" process to stop harassing me?
I assume you can open the projects settings in Eclipse and disable the GWT validator. There is a validation section somewhere in the Eclipse settings.
-- J.
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/0d94f0f6-b357-4f9a-a3e3-a8a06da6fa5d%40googlegroups.com.
No comments:
Post a Comment