It would be great if we had an option to tell GWT to not fail on compilation errors but automatically mark non compiling code as @GwtIncompatible.Is it a possible enhancement I can submit?
But then you would hide real compilation issues.
So for now, the only way to use thrid-party libraries that don't compile as is with GWT (even if the problem is in a part that I don't use) is to copy the sources and then patch them with @GwtIncompatible annotations?
Yes either use @GwtIncompatible or provide a super-source implementation. In the best case you would fork the third-party library in question, make it GWT compatible by adding @GwtIncompatible annotation and contribute it back.
But keep in mind when using @GwtIncompatible its acts like you have deleted that annotated method in source code. The source code must still be valid even with the now "deleted" method and as the JavaDoc states it can have surprising effects with method overloading or inheritance if you do not take care.
-- 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 post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment