I know you can force Gradle to swap out dependencies on the fly, e.g. replace com.google.gwt with org.gwtproject releases. If that would also be possible with Maven/Ivy/Bazel then it is just a matter of documentation.
If that is not possible, or not desired, then Google could probably publish a single, empty com.google.gwt:..:99.0 release without any dependencies in its pom. Our new published org.gwtproject:...:2.10 release would depend on com.google.gwt:...:99.0 which means all old GWT libraries should be upgraded via Maven/etc to 99.0 automatically as soon as you add org.gwtproject:...:2.10 to your dependencies. Since the 99.0 release is empty and the classes are provided by our new release, there should not be any class path conflicts. New GWT libraries would directly depend on our new release which means as soon as you try to migrate your code to one of the new GWT libs, our new org.gwtproject release will be pulled in and provide the code for everything. -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/10ac1356-1146-4ff1-9732-f4983a7d9367o%40googlegroups.com.
