Description

Uwe noticed this. After the update to gradle 8.14, I've updated the gradle-wrapper script's version and SHA. The new scripts launch it using -jar (previously it was launched using an explicit main method). This uncovered a potential problem that hasn't manifested itself so far - we only check if gradle-wrapper.jar exists; if it doesn't exist, we invoke WrapperDownloader but if gradle-wrapper.jar already exists, we take no action and use this file (which may be older/different).

We could check the sha of the wrapper script on each invocation but this seems like an overkill. I don't have a fix for this one. I think we're just going to live with this oddity, hoping that it doesn't cause side effects often (what Uwe experienced).

Version and environment details

No response