Maintaining up-to-date Gradle Wrapper files in codestarts

[reaver585]

Hi everyone,

While investigating an issue related to the Gradle wrapper generated by the CLI (#48191 (comment)), I noticed that the wrapper files used in codestarts are outdated. For example, the generated gradlew script still includes Macos-specific logic that was removed from Gradle several years ago.

This led to a failure when running ./gradlew quarkusRun, due to a combination of the outdated script and how certain environment variables interacted with SmallRye Config. That particular issue has since been fixed in SmallRye, so it's no longer a blocker - but it did highlight that the wrapper files checked into the repo are out of sync and could cause other subtle problems.

Just wanted to raise the question of how this could be handled going forward. Some possible options:

1. Manual updates + comment in pom.xml
   Require contributors to update the wrapper files manually whenever the Gradle version is bumped, and document this clearly in independent-projects/tools/pom.xml (I have a PR opened for that, #48395)

2. Automated sync mechanism
   Build tooling to fetch or regenerate wrapper files automatically as part of a release or CI process. Might not be viable if the CLI is expected to work fully offline, and the potential complexity is questionable.

3. Other suggestions
   Are there better approaches for keeping things in sync? Should wrapper versions be coordinated across tools/pom.xml and build-parent/tools/pom.xml?

If you’ve worked with the CLI / codestarts or have ideas for improving how this is maintained, your ideas are very appreciated.
Thanks in advance!

[quarkus-bot[bot]]

/cc @glefloch, @ia3andy (codestart), @quarkusio/devtools (codestart)

[reaver585]

I'd say the topic is now closed with #48506.

[gsmet]

Yes, thanks a lot for diagnosing this issue as it has probably been annoying for our Gradle users for quite a while!