I’m having problems using detekt in my project… (k...

# detekt

[pedro]

I’m having problems using detekt in my project… (kotlin jvm project)

I have different problems if I use 1.9.1 or 1.10.0

1.10.0

Execution failed for task ':foo:detekt'.
> Could not resolve all files for configuration ':foo:detekt'.
   > Could not find io.gitlab.arturbosch.detekt:detekt-cli:1.10.0.
     Searched in the following locations:
       - <https://repo.maven.apache.org/maven2/io/gitlab/arturbosch/detekt/detekt-cli/1.10.0/detekt-cli-1.10.0.pom>
     If the artifact you are trying to retrieve can be found in the repository but without metadata in 'Maven POM' format, you need to adjust the 'metadataSources { ... }' of the repository declaration.

I have seen someone mentioning in github issues that it seems that some artifacts weren’t published in all repositories

If I try to use 1.9.1:

> Could not find org.jetbrains.kotlinx:kotlinx-html-jvm:0.7.1.
     Searched in the following locations:
       - <https://repo.maven.apache.org/maven2/org/jetbrains/kotlinx/kotlinx-html-jvm/0.7.1/kotlinx-html-jvm-0.7.1.pom>
     If the artifact you are trying to retrieve can be found in the repository but without metadata in 'Maven POM' format, you need to adjust the 'metadataSources { ... }' of the repository declaration.
     Required by:
         project :foo > io.gitlab.arturbosch.detekt:detekt-cli:1.9.1

I’ve tried all possible combinations of the instructions in the website and still haven’t got it to work. Can someone help?

[pedro]

This would be what my simple gradle file would look like. But I’ve tried many variations already.

buildscript {
    dependencies {
//        classpath "org.jetbrains.kotlinx:kotlinx-html-jvm:0.7.1"
        classpath "io.gitlab.arturbosch.detekt:detekt-gradle-plugin:1.9.1"
    }
}
plugins {
    id "io.gitlab.arturbosch.detekt" version "1.9.1"
}

It doesn’t help that the detekt recommends slightly different approaches in different places and some of them actually have syntax errors (happy to post some of those issues on a separate thread)

[gammax]

Thanks for reporting. So the first issue you’re facing is related to this https://github.com/detekt/detekt/issues/2842 (1.10.0 is not yet on maven central, we’ll hopefully fix it soon).

[gammax]

For your second point, can I ask you to try this configuration https://detekt.github.io/detekt/groovydsl.html#configuration-when-using-groovy-dsl ? Seems like you’re not specifying your repositories{} block and this is causing the build to fail.

[gammax]

It doesn’t help that the detekt recommends slightly different approaches in different places and some of them actually have syntax errors (happy to post some of those issues on a separate thread)

If you could actually create a Github Issue or open a PR, that would be great 👌

[pedro]

I had tried with repositories before and it didn't work either (in the error message it reported as having looked at one repo only which is weird)

I can try what you said when I get back to my computer and I'll update (not soon)

Cheers

[Brais Gabin]

Kotlin html is only published in jcenter. So you need to add that repository at least for that dependency.

[Brais Gabin]

We discussed this before. It would be great to have that kotlin htlm in maven central but it's out of our control.

[pedro]

I tried what “configuration on groovy dsl” link. As it is in the example, it fails with only buildscript {} and other plugins {} script blocks are allowed before plugins {} blocks, no other statements are allowed.

Wrapping it with buildscript { ... } it goes back to the error message I posted, where it can’t find kotlinx html

fwiw, this is the gradle file now:

buildscript {
    repositories {
        jcenter()

        // or
        // also tried removing the repositories below this line
        mavenCentral()
        jcenter {
            content {
                // just allow to include kotlinx projects
                // detekt needs 'kotlinx-html' for the html report
                includeGroup "org.jetbrains.kotlinx"
            }
        }
    }
}

plugins {
    id "io.gitlab.arturbosch.detekt" version "1.9.1"
}

It shouldn’t affect this, but this is in a multi module project. Although to simplify things I am trying to apply this directly in one of the modules…

This is an open source project so you can get exactly the same code as me if you want to try it on your computer

[pedro]

Also tried the instructions for android:

buildscript {
    repositories {
        maven { url "<https://plugins.gradle.org/m2/>" }
        jcenter()
    }
    dependencies {
        classpath "io.gitlab.arturbosch.detekt:detekt-gradle-plugin:1.9.1"
    }
}

plugins {
    id "io.gitlab.arturbosch.detekt" version "1.9.1"
}

Same kotlinx html error

[pedro]

Feel free to suggest more tweaks, or show me a project that is able to use the version 1.9.1 of the plugin and I can try to find the differences…

[gammax]

This is an open source project so you can get exactly the same code as me if you want to try it on your computer

Can you please link it?

[pedro]

https://github.com/pedroql/mvflow

I’m trying to do this in the mvflow-core module (the only module with actual kotlin code so far). So you can open mvflow-core/build.gradle file instead of the one in the root folder.

[pedro]

I’m working on the branch feature/code_quality_improvements but it shouldn’t affect this either.

[gammax]

So this will work:

plugins {
    id "io.gitlab.arturbosch.detekt" version "1.10.0"
}
repositories {
    mavenCentral()
    jcenter()
}

[gammax]

And if you want to use the buildscript{} syntax, also this will work:

buildscript {
    repositories {
        maven { url "<https://plugins.gradle.org/m2/>" }
    }
    dependencies {
        classpath "io.gitlab.arturbosch.detekt:detekt-gradle-plugin:1.10.0"
    }

}
apply plugin: 'io.gitlab.arturbosch.detekt'

repositories {
    jcenter()
}

[gammax]

That being said, our documentation is misleading and we should update it. You are right.

[pedro]

wow, that works!

I was convinced that the dependencies for a plugin had to be declared inside the buildscript closure. So my problem was that I was missing the repositories in the top level! 😮

[pedro]

thank you!!

[pedro]

I created this PR with some suggested changes. Left a few comments too to explain my reasoning but someone needs to decide what goes into the official docs. That’s just a suggestion! 🙂

https://github.com/detekt/detekt/pull/2845/