Provide at least one sample that shows how to use Gradle with GWT

[niloc132]

Going by GWT's samples and documentation, no one uses Gradle. This clearly isn't true, but for existing Gradle users who want to add GWT to their projects, or existing GWT users that want to move to Gradle, better documentation and samples could improve this situation.

There are several Gradle plugins out there that support GWT, and while we shouldn't "pick a winner", the GWT project documentation and samples should demonstrate how Gradle can be used to build GWT projects. These can be used to encourage users to start their own projects in maintainable ways, and can be used for release testing.

Existing GWT+Gradle integration tools:

• https://github.com/esoco/gwt-gradle-plugin/ - doesn't support org.gwtproject groupid
• https://github.com/jiakuan/gwt-gradle-plugin - doesn't support org.gwtproject groupid
• https://github.com/tbroyer/gwt-gradle-example/ - no reusable plugin, instead requires wholesale copy/paste into each project, already archived and frozen

See also #10011.

[zbynek]

https://github.com/jiakuan/gwt-gradle-plugin - doesn't support org.gwtproject groupid

The 1.x version supports both groupIds since jiakuan/gwt-gradle-plugin@8b71a07 (does not use the BOM though)

The 2.x version (first non-alpha release 2.0.12 released just today) drops support for the old one.

[niloc132]

Thanks @zbynek, looks like jiakuan/gwt-gradle-plugin#63 should be closed then?

That same plugin also doesn't seem very "gradle-native", the jiakuan/gwt-gradle-plugin#79 issue in particular makes me worry that I'm going to need to rebuild all of our downstream because GWT was forced to re-run. I can vouch that the de.esoco.gwt plugin doesn't have that problem.