TL;DR: If you have the capability to do so, now would be an excellent time to help us test GWT in anticipation of a release, especially around the groupId change we're going to make.
-- We think that we're one merge away from being ready for a GWT 2.10 release, so I'm starting the release process a bit early, since this last commit involves changing GWT's groupId away from com.google and to org.gwtproject. To that end, I have a maven repo with the maven changes along wit all of the other changes in the GWT 2.10 series. The repo's URL is https://repo.vertispan.com/gwt-groupid-migration-test/, and the only GWT version that exists there is "2.10.0-new-groupid-2". Based on earlier work (such as in the https://groups.google.com/g/google-web-toolkit-contributors/c/L2RMqglOEXo/m/44BeZKeBCQAJ thread), this should allow projects to transition from com.google.gwt to org.gwtproject by adding the org.gwtproject:gwt:pom to their project, and then specify gwt-user etc, and automatically manage the version of gwt used by dependencies. It should also be possible to just use the old groupid for this release, but later releases will not have that option. Please note that *packages are not changing *as part of this transition, only groupIds. Rough release notes: * Updated htmlunit and jetty to more recent versions * Dropped support for IE8/9/10 * Dropped support for Java 7 * Support long classpaths by using CLASSPATH env vars to run child permutation workers * Many enhancements to emulation APIs and generated code Please reply to this thread or email me directly with any results/surprises/questions. -- 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/dad1685b-9ad0-4a1a-88f4-dd0332d7b91dn%40googlegroups.com.
