Two "issues" I added detect to my android project via the plugins block in my root build.gradle. 1. Now I try to run

./gradlew detektMain

, but I get an error:

Task 'detektMain' not found in root project 'rollertoaster'.

2. If I run ./gradlew detekt, I get a success message in 1s, but I don't think detekt actually analyzed my code.

The following Kotlin source sets were configured but not added to any Kotlin compilation:
 * androidAndroidTestRelease
 * androidTestFixtures
 * androidTestFixturesDebug
 * androidTestFixturesRelease
You can add a source set to a target's compilation by connecting it with the compilation's default source set using 'dependsOn'.
See <https://kotlinlang.org/docs/reference/building-mpp-with-gradle.html#connecting-source-sets>

BUILD SUCCESSFUL in 1s

3. I can't add detekt into spotless right? I use spotless in order to run ktfmt, so being able to add detekt into spotless would be cool. Can I get help on those three?

1+2. https://github.com/detekt/detekt/issues/3663 3. https://github.com/diffplug/spotless/issues/143

Interesting. 1+2: Running detektAll doesn't work for me 3. Looks like there's no reason to configure detekt inside of spotless

there is no detektAll task, "It can be simply implemented like `...`". either do that or run the specific detekt tasks you want

Oh. I saw "I think we could add a 

detektAll

 task that can depend on all the 

detekt*

 tasks." and thought they implemented

ditto,

detektDebug

etc.

Yeah. Anyone got ideas for what I should do?

So for 1:

via the plugins block in my root build.gradle.

That’s actually the problem. If you add Detekt to your root project

plugins{}

, you’re applying to a non-Android project. Therefore all the Android specific tasks will not be added.

@gammax 1. oh. well apparently I misinterpreted the docs. LET ME TRY NOW! 2. Cool. 3. It's fine for now. Was just curious if someone else had the same experieience.

Docs says “make sure to have detekt configured in the project level

build.gradle

file” no? They never mention root 🤔

All other docs for libraries I've used say "project level" as root, and app level as the android app module. Even plugins from the android team use that same nomenclature.

for what it's worth, I do like to add an extra Detekt task in the root project which includes all the kotlin buildscripts

I only need to have it run on like 2 of 8 modules. So I'm currently trying to figure that out. Lol

We tend to refer to

project

as Gradle do. So what in Android you would call a

module

for Gradle is a `project`: https://docs.gradle.org/current/userguide/multi_project_builds.html#sec:creating_multi_project_builds

And then I'd run detekt via

./gradle :module2:detekt

?

correct 👍

Oooh. That's nice. But all of the results will still be placed into the modulename/build/whatever right?

Yeah I agree that the whole “project” thing in Gradle is really confusing 😞

Awesome. Thank you for the help Nicola. I also love the podcast. Keep it up!

@Colton Idle I had a similar issue, and my projects include the following in a plugin to fix it (I think I found this somewhere in a GitHub issue):

val artifactType = Attribute.of("artifactType", String::class.java)

class DisambiguationRule : AttributeDisambiguationRule<String> {
  override fun execute(t: MultipleCandidatesDetails<String>) {
    /**
     * The default disambiguation rules exclude the jar variants because they define the `org.gradle.libraryelements`
     *
     * See <https://github.com/gradle/gradle/blob/master/subprojects/dependency-management/src/main/java/org/gradle/internal/component/model/MultipleCandidateMatcher.java#L221>
     *
     * Not 100% sure why this happens but forcing to use the jar in this specific case fixes the issue
     */
    val jar = t.candidateValues.firstOrNull { it == "jar" }
    if(jar != null) {
      t.closestMatch(jar)
    }
  }
}

dependencies.attributesSchema.attribute(artifactType).disambiguationRules.add(DisambiguationRule::class.java)e