Is it planned to do a release with Gradle 8 compatibility? ``` Reason: Task ':detekt' uses this ...

# detekt

[Javier]

Is it planned to do a release with Gradle 8 compatibility?

Reason: Task ':detekt' uses this output of task ':foo:compileKotlin' 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 ':foo:compileKotlin' as an input of ':detekt'.
      2. Declare an explicit dependency on ':foo:compileKotlin' from ':detekt' using Task#dependsOn.
      3. Declare an explicit dependency on ':foo:compileKotlin' from ':detekt' using Task#mustRunAfter.

[PoisonedYouth]

Are you sure this is a general issue? I use Detekt 1.22.0 with Gradle 8.0 and everything works as expected without warning

[Javier]

Do you have a multiproject?

[Javier]

I am trying to find if I am registering the detekt task by myself but I can't find it

[Javier]

Curiously, the issue is not happening if I run detekt directly, it was happening if I run build

[PoisonedYouth]

No it's just a multimodule project.

[Javier]

I am going to investigate it more, really weird situation

[Javier]

Looks like it is a dependency between modules, like one module is depending on another one and that happens

[Javier]

Is it possible that detekt is aggregating modules which depends on?

current setup is

• foo
• foo-consumer (api(project(":foo"))
And it fails because multiple tasks from other plugins (spotless, and so on), from one module, crashes with the detekt one in another module, for example :foo:detekt fails because :foo-consumer:spotlessKotlin

[eygraber]

I have a similar setup (no spotless though) and I'm not seeing this issue

[Javier]

I found the issue, it was related to setting the sources on detekt task (something I was doing since the first setup a lot of years ago)

[Javier]

I had another workaround to get a detekt report on the root with that, I mean, I was setting the root dir as sources, I think @ephemient is doing it too, so maybe he will face this issue too