Javier
03/09/2023, 4:28 PMReason: 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.
detekt
task in the root project even if I am not applying the plugin in the root project.
Anyone can confirm that is being done on the Detekt Gradle Plugin?
As Gradle does naming matching, it is unnecessary to do that.PoisonedYouth
03/09/2023, 5:52 PMJavier
03/09/2023, 5:54 PMdetekt
task by myself but I can't find itdetekt
directly, it was happening if I run build
PoisonedYouth
03/09/2023, 5:56 PMJavier
03/09/2023, 5:57 PMfoo
• 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
03/09/2023, 7:05 PMJavier
03/10/2023, 11:18 AM