Replies: 3 comments 4 replies
-
Moving to a discussion We're already working on consolidating reports here: #3394 - @chao2zhang is on it and we will hopefully come up with a solution that works with Gradle in the near future 👍
I'd say that there is no "idiomatic" way to define aggregations. What they're doing is defining a precompiled gradle plugins + a new |
Beta Was this translation helpful? Give feedback.
-
This solution has the advantage, that no additional dependencies need to be declared, as well as the aggregation could be done in any project, not only the root Project. But I do unterstand your comment. Thanks. |
Beta Was this translation helpful? Give feedback.
-
This is my first time reading "Structuring Large Projects" and the sample was using a particular set of gradle features such as composite builds.
Hence in #3394 the consensus is to provide Gradle tasks and sample code to aggregate these reports. |
Beta Was this translation helpful? Give feedback.
-
In gradle 6.8.x (and most probably before this already) gradle provides an "idiomatic" way to define aggregrations of reports without task-dependencies. This is mainly done using configurations, for an example see https://docs.gradle.org/release-nightly/samples/sample_structuring_software_projects.html.
Expected Behavior
The detekt Task should support this idiomatic way and should (best case) provide some detailed documentation on how to apply this pattern to an existing project.
Current Behavior
The current plugin implementation does not provide a nice and simple way to implement an report-aggregation, without any task-dependencies without a rootProject-build.
Beta Was this translation helpful? Give feedback.
All reactions