Umm, ok. We have an extremely large and complex GWT development environment here, developed over a decade; God only knows what might be involved in rearchitecting it to not use the GWT SDK. It's complete news to me that there's any alternative; I don't quite know where to start in trying to make sense of this configuration.
-- 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? And is there seriously no way to tell the "Validating GWT components" process to stop harassing me?
On Wednesday, July 24, 2019 at 8:40:21 AM UTC-7, Thomas Broyer wrote:
On Wednesday, July 24, 2019 at 8:40:21 AM UTC-7, Thomas Broyer wrote:
On Wednesday, July 24, 2019 at 5:14:42 PM UTC+2, Jim Douglas wrote:> Sure. Use a build tool of your choice and use the maven dependencies.I don't know what that means. As far as I've ever known, developing a GWT application in Eclipse implies installing the GWT Plugin for Eclipse and picking a GWT SDK.Nope.Install the GWT Eclipse Plugin (https://gwt-plugins.github.io/documentation/gwt-eclipse- ; note that the SDKs are optional).plugin/Download.html Create (https://gwt-plugins.github.io/documentation/gwt-eclipse- ) or import (https://gwt-plugins.github.plugin/maven/Maven.html io/documentation/gwt-eclipse- ) a Maven project using GWT.plugin/workspace/Importing. html You're all set; the plugin will use the GWT dependencies from the Maven project.
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/00420c60-e882-4196-a842-57117110b67c%40googlegroups.com.
No comments:
Post a Comment