Andreas Sewe

> related? #522 Might be. As to your question in #522: > Any chance to upgrade to more recent Gradle 6.x? The above `NoSuchFieldError` occurs with the following: ``` $...

FWIW, with the latest Gradle 6.6.1 the above `buildEnvironment` tree looks exactly the same.

More input (using `git bisect run`). The likely problem, i.e., the `okhttp` version mismatch (as found by `./gradlew :intellij:buildEnvironment | grep 'okhttp.*->'`), was introduced when we updated from `org.jetbrains.intellij` version...

A bit more (manual) bisecting shows that the version mismatch was introduced **between** `org.jetbrains.intellij` version 0.4.16 to 0.4.17. Hope that helps.

Can someone else please verify that their `buildEnvironment` also contains the suspicious `com.squareup.okhttp3:okhttp:3.14.4 -> 4.3.1` upgrade? Would like to ascertain that this is not some weird side-effect of our build...

@YannCebron I am afraid I can reproduce with 0.5. Here’s the stacktrace: ``` Execution failed for task ':intellij:com.teamscale.ide.intellij:publishPlugin'. > Companion * Try: Run with --debug option to get more log...

Very likely, as even the latest version of Retrofit2 ([`com.squareup.retrofit2:retrofit:2.9.0`](https://search.maven.org/artifact/com.squareup.retrofit2/retrofit/2.9.0/jar)) still uses a 3.x of `okhttp3`, so the 3.x/4.x clash can't be fixed by simply updating `plugin-repository-rest-client`’s dependencies: ``` +---...

Just tested with 0.7.2. This is unfortunately still any issue, which means I am still stuck using 0.4.21, which is a real pity as I would very much like to...

I would also love to see a simple `` option. Other plugins that have a similar option (unfortunately with somewhat inconsistent naming): - [`maven-checkstyle-plugin`](https://maven.apache.org/plugins/maven-checkstyle-plugin/check-mojo.html#includeTestSourceDirectory) `` - [`maven-pmd-plugin`](https://maven.apache.org/plugins/maven-pmd-plugin/pmd-mojo.html#includeTests) `` - [`spotbugs-maven-plugin`](https://spotbugs.github.io/spotbugs-maven-plugin/check-mojo.html#includeTests)...

> And at the same time incorrect interpretation/enforcement of metrics can lead to bad things, which as we all know quite often happens with code coverage metrics :wink: I can...