Slackbot
06/07/2023, 12:19 PMVampire
06/07/2023, 12:27 PMdependsOn
is always a code-smell unless the left-hand side is a lifecycle task.
If you actually need the outputs of that task in the other project, you should use the proper cross-project publication means as documented at https://docs.gradle.org/current/userguide/cross_project_publications.htmlJavi
06/07/2023, 12:36 PMdependsOn
that I have to put related to the Gradle 8.0 upgrade.
Should be great a guide about how to avoid them, for example when I codegen some sources, detekt task cries, and so on.Vampire
06/07/2023, 12:44 PMsrcDir
for the source set.
Then any part requesting sources like compilation task, source jar task, and so on, automatically get those sources and the needed implicit task dependency.
In case of generated code you only have a problem if the code generation also uses the sources as input. Then you would have a circular dependency and have to check on a case-by-case basis how to properly do it.Javi
06/07/2023, 12:45 PMShalom Ben-Zvi Kazaz
06/07/2023, 12:46 PMVampire
06/07/2023, 12:48 PMShalom Ben-Zvi Kazaz
06/07/2023, 12:54 PMVampire
06/07/2023, 1:02 PMShalom Ben-Zvi Kazaz
06/07/2023, 1:03 PMShalom Ben-Zvi Kazaz
06/07/2023, 5:09 PMJavi
06/08/2023, 3:19 AMJavi
06/08/2023, 9:18 AMSourceTask
but I am still getting the same error
Reason: Task ':detekt' uses this output of task ':generateProjectData' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.
Javi
06/08/2023, 9:27 AMsrcDirs
but now I am getting
* What went wrong:
Could not determine the dependencies of task ':check'.
> Could not create task ':detekt'.
> Failed to query the value of extension '...' property 'includes'.
> Stack overflow during pattern compilation near index 4
((?<=\p{Ll})\p{Lu}|\p{Lu}(?=\p{Ll}))
^
Javi
06/08/2023, 10:10 AMbuild/generated
to detekt inputs which was bad in first instance 🤦♂️Vampire
06/08/2023, 12:07 PM