From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

Hi, every time I run './gradlew wrapper' with 9.5.0, the new retry values are reset to their defaults
once I set a number of retries, shouldn't it keep the values I set?

I don't think so.
The 4 wrapper files are always overwritten with the defaults unless you supply options to the wrapper task like `--retries` or `--retray-back-off-ms`, see `gw help --task wrapper`.
Or via task configuration.

Preserving values in the existing file if no options are supplied would probably be a candidate for a feature request

maybe setting in gradle.properties is the way to override?

documentation says to update the gradle-wrapper.properties file to set retries, so that doesn't seem quite right

<https://docs.gradle.org/9.5.0/userguide/gradle_wrapper.html#sec:configuring_wrapper_retries>

As I said, you can set via CLI options to the `wrapper` task or task-configuration of the `wrapper` task what to generate.
So if you want to have certain values when you call the `wrapper` task, configure the `wrapper` task in your build script.

got it.  i was reading it as I had to set the CLI whenever I called wrapper.
this makes sense now.  thanks

I agree that the docs are misleading on this point. They say to edit the file directly. They do _not_ say to configure the task.

for completeness,
when I committed the task that sets the properties, copilot sees this as a conflict with the settings in gradle-wrapper.properties

Then I'd say Copilot is obviously wrong, as the task configuration controls what will be written to that file if you execute the  `wrapper` task.