Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
niloc132 opened this issue Nov 2, 2024 · 3 comments
Open

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

niloc132 opened this issue Nov 2, 2024 · 3 comments

Comments

@niloc132
Copy link
Member

niloc132 commented Nov 2, 2024

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:

See also #10011.

@zbynek
Copy link
Contributor

zbynek commented Nov 2, 2024

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
Copy link
Member Author

niloc132 commented Nov 4, 2024

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.

@jiakuan
Copy link

jiakuan commented Nov 13, 2024

jiakuan/gwt-gradle-plugin#79 has been fixed in v2
Only changed files would trigger a GWT rebuild, currently tracking inputs are:

  • Module files configured
  • Package directory for each entry-point files
  • Source paths configured in GWT module files
  • Public paths configured in GWT module files

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants