A modern programming language that makes developers happier.

kotlinlang

I'd like to move my custom Detekt configuration into a Gradle plugin in buildSrc later on, so at this point a `detektPlugins(project("..."))` configuration would no longer work anyways...

Add this to dependencies block inside build.gradle.kts (buildSrc)

`implementation("io.gitlab.arturbosch.detekt:detekt-gradle-plugin:$detekt")`

Ah, I only applied `detekt-api` there, applying the plugin there should work?! Nice!

No, this didn't work unfortunately :disappointed: The custom ruleset is not found.

That `implementation` let you use `detektPlugins` in precompiled plugins

image.png

For example, this is my own plugin for detekt

The filename for my detekt plugin is Detekt.gradle.kts

Hrm... weird, this doesn't look like a standard plugin (that has to be wrapped into a `Plugin&lt;Project&gt;` derived class) at all, but if this works for you, well.

I worked around it for now by using
```dependencies {
  val detektPlugins by configurations
  detektPlugins(files("$rootDir/buildSrc/build/libs/buildSrc.jar"))
}```

Still haven't moved my Detekt configuration to buildSrc, but only have the additional rules there

<https://docs.gradle.org/current/userguide/custom_plugins.html#sec:precompiled_plugins>

Hi, we are doing the same at our repo with precompiled plugins and project dependencies as `detektPlugins` :
<https://github.com/detekt/detekt/blob/master/buildSrc/src/main/kotlin/detekt.gradle.kts#L45>

<@U0MDRD3RN> can you take a look to this issue? <https://github.com/detekt/detekt/issues/2732|https://github.com/detekt/detekt/issues/2732>

<@U0MDRD3RN> Sorry for the late reply. Actually, I kind of dislike of having more than `buildSrc` as build configuration source. I see however that Gradle provides no clean way to access the `buildSrc` module itself for this configuration, probably because of <https://github.com/gradle/gradle/issues/2531>