Since moving to Gradle 9 my bash scripts in `src main dist b Gradle Community #community-support

Since moving to Gradle 9, my bash scripts in `src/...

Arthur McGibbon

08/05/2025, 4:22 PM

Since moving to Gradle 9, my bash scripts in

src/main/dist/bin

lose their exec attribute when being copied into the archive by the distribution plugin. That's a bug isn't it?

Anze Sodja

08/05/2025, 4:28 PM

See https://docs.gradle.org/current/userguide/upgrading_major_version_9.html#reproducible_archives_by_default

Arthur McGibbon

08/05/2025, 4:31 PM

Doh - thanks. Seems weird to change the default.

Vampire

08/05/2025, 4:32 PM

Permissions configured on the copy-spec are hopefully still taken into account @Anze Sodja?

Vampire

08/05/2025, 4:32 PM

It's imho anyway better to configure it there for consistent cross-OS build results

👍 1

Anze Sodja

08/05/2025, 4:37 PM

You mean:

Copy code

eachFile {
 ...
}

? yes it overrides setting on a task. We actually didn't change any behaviour, just the default.

👌 1

Anze Sodja

08/05/2025, 4:45 PM

> Seems weird to change the default. There was a lot of comments in https://github.com/gradle/gradle/issues/30871 But this execution flag is probably the most surprising thing indeed. But more we discussed it, it seemed that the right way is to have fully reproducible archives in the end and offer opt-out for permissions. That is why we also added an opt-out flag on the build level via:

Copy code

org.gradle.archives.use-file-system-permissions=true

👍 2

Arthur McGibbon

08/05/2025, 5:36 PM

Makes sense. And it's easy for me to fix. I suppose it would be nice to have a warning from Gradle saying it has changed a file's permission to 0644 (if that file wasn't 0644) and that I need to setup handling to deal with that if I want to keep the original permissions. I take @Vampire's point that it's better to explicitly configure it for consistency.

4 Views

Open in Slack

Previous Next