Detekt Gradle plugin #4052
Replies: 2 comments
-
Would any of those help with #2957? I don't have any strong opinion here. If we had a really stable API I would vote for the third option. But we don't so 1 or 2 are fine for me. |
Beta Was this translation helpful? Give feedback.
-
I'm in for the composite build approach (I'm biased maybe :)). I believe it would help us ship a better product overall. The problem is that currently detekt To mitigate the build impact, we could opt for an hybrid approach. Like we could have an env variable that optionally imports the composite build (for developers that wants to develop for it and for a CI workflow), and as an alternative fallsback to getting the artifact of the Gradle plugin from Gradle Plugin Central. |
Beta Was this translation helpful? Give feedback.
-
There are recent discussions with respect to the detekt-gradle-plugin. I would like to formally reach a consensus that if we want to build detekt-gradle-plugin as...
I assume we change gradle plugin more often than adding cli parameters, therefore, moving it to composite-build is making us more productive. Any other thoughts?
Beta Was this translation helpful? Give feedback.
All reactions