Anže Sodja

Hi @anasoid, thanks for the report and sorry you have problems with 7.5. This is an unfortunate consequence of 7.5 since Checkstyle now uses Worker API. Would be possible for...

Maybe it would be worth adding at least a comment above the problematic line, something like: `for Gradle use ${config_loc}/checkstyle-suppressions.xml` or something like that.

Hi @HEdingfield, thanks for investigating the issue. Original issue was for the case where `google_checks.xml` was copy/pasted to a project, so modifying `.xml` to use `${config_loc}` is not problem. I...

Thanks for your interest in that feature. I will try to answer some questions. > My main unanswered question is: is this solution clearly better than delegation? Delegation was considered,...

From the comments, I believe that one of the concerns is that this feature will change the meaning of `=`. So this is my view on that: I believe that...

> I'd much prefer something that's limited but can be expanded consistently in the future instead of a low-effort solution that will introduce more implicit behavior and be redundant once...

Update: we (Gradle build tool) had a discussion with the Kotlin team some time ago due to concerns from the community. It was later decided that _assign operator overload_ won't...

Gradle 8 will allow to have a reason, not on the `component`, but on a checksum of a component (so for example sha256). I believe that closes this issue.

> Do you know what the situation is where we would want to add checksums for artifacts that already have matching, trusted signatures? I remember #21272 where user would want...

This is an interesting consequence of fixing `org.gradle.native` handling. Before 8.8 Gradle ignored `org.gradle.native` flag, which was basically a bug. That was fixed with https://github.com/gradle/gradle/pull/28021 in 8.8. Unfortunately our ForkingTestClassProcessor...