This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

can I programatically get the fingerprint of a

DirectoryProperty

or

Provider<FileSystemLocation>

that Gradle uses for up-to-date checks? I'm using a Configuration to share a files between subprojects. The Configuration contains a some directories, and a JSON file that describes some config and lists the directories. The receiving subproject has a task that uses the config file as well as the directories. It would be convenient if I could add the fingerprint of the directories to the config file, so that the receiving task will be up-to-date. Otherwise, I have to set up task inputs, or manually compute an md5 for the directories, and I'd lose Gradle's file normalization.

On open source projects, is it fine to run build scans even if that can be a bit spammy? (Dependabot/Renovate PRs) and so on

I am having an issue with with the detekt task and Gradle 8.0, this is the setup: •

:gradle-extensions

(it has no code, it just add more subprojects using api(...), like it was an index of all projects) •

:gradle-extensions-subprojects:gradle-logging-extensions

And the error is this one:

Reason: Task ':gradle-extensions:detekt' uses this output of task ':gradle-extensions-subprojects:gradle-logging-extensions:spotlessKotlin' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.

    Possible solutions:
      1. Declare task ':gradle-extensions-subprojects:gradle-logging-extensions:spotlessKotlin' as an input of ':gradle-extensions:detekt'.
      2. Declare an explicit dependency on ':gradle-extensions-subprojects:gradle-logging-extensions:spotlessKotlin' from ':gradle-extensions:detekt' using Task#dependsOn.
      3. Declare an explicit dependency on ':gradle-extensions-subprojects:gradle-logging-extensions:spotlessKotlin' from ':gradle-extensions:detekt' using Task#mustRunAfter.

As you can see in the

Reason

, the

detekt

task is on the

gradle-extensions

module, and the the

spotlessKotlin

in a different module. I have tried to do

detekt.mustRunAfter(_tasks_.findByName("spotlessKotlin"))

, but that dependency would work with tasks on the same project

This message was deleted.

This message was deleted.

Maybe somebody here knows. 😅

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

* What went wrong:
A problem occurred configuring root project 'protos'.
> Could not create task ':updateProtos'.
   > Could not create task of type 'UpdateProtosTask'.
      > Too many parameters provided for constructor for type UpdateProtosTask. Expected 0, received 1.

When I debug, the "constructor args" are a function call from the plugin's apply method to an instance method on the task that runs some configuration code. This only happened when I changed the project that this plugin is applied to. In one project, no problem. In another, this error Yeah, removing the method call and putting all the config code in the plugin's apply method resolved the issue. Odd

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.