```./gradlew check FAILURE: Build failed with an exception. * Where: Build file 'C:\projects\ger\b...

# gradle

[bitkid]

./gradlew check

FAILURE: Build failed with an exception.

* Where:
Build file 'C:\projects\ger\build.gradle.kts' line: 8

* What went wrong:
Plugin [id: 'com.github.ben-manes.versions', version: '0.27.0'] was not found in any of the following sources:

- Gradle Core Plugins (plugin is not in 'org.gradle' namespace)
- Plugin Repositories (could not resolve plugin artifact 'com.github.ben-manes.versions:com.github.ben-manes.versions.gradle.plugin:0.27.0')
  Searched in the following repositories:
    Gradle Central Plugin Repository

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at <https://help.gradle.org>

[GarouDan]

Comparing with here: https://plugins.gradle.org/plugin/com.github.ben-manes.versions

Could it be misspelled?

com.github.ben-manes:gradle-versions-plugin:0.27.0

com.github.ben-manes.versions:com.github.ben-manes.versions.gradle.plugin:0.27.0

[bitkid]

it's exactly this

[bitkid]

id("com.github.ben-manes.versions") version "0.27.0"

[bitkid]

and as i said .. happens to all plugins

[GarouDan]

If it is not a problem with proxy or something like it,
maybe could be interesting try to delete the gradle cache and use the --refresh-dependencies.

rm -rf~/.gradle/caches/modules-2/files-2.1/com....manes-versions # maybe remove the entire cache
rm -rf build buildSrc/build # all project builds folders maybe

./gradlew clean build --refresh-dependencies

But this is just a guess, anyway sometimes helps

[bitkid]

i am a bit afraid when i do that .. that all my deps are gone and i can't fetch them again

[bitkid]

a yes .. as soon as i add --refresh-dependencies

[bitkid]

PS C:\projects\ger> ./gradlew check --refresh-dependencies

FAILURE: Build failed with an exception.

* Where:
Build file 'C:\projects\ger\build.gradle.kts' line: 8

* What went wrong:
Plugin [id: 'org.jetbrains.kotlin.jvm', version: '1.3.50'] was not found in any of the following sources:

- Gradle Core Plugins (plugin is not in 'org.gradle' namespace)
- Plugin Repositories (could not resolve plugin artifact 'org.jetbrains.kotlin.jvm:org.jetbrains.kotlin.jvm.gradle.plugin:1.3.50')
  Searched in the following repositories:
    Gradle Central Plugin Repository

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at <https://help.gradle.org>

[bitkid]

what looks a bit weird is this

[bitkid]

16:52:04.775 [DEBUG] [org.apache.http.conn.ssl.SSLConnectionSocketFactory] Starting handshake
16:52:04.816 [DEBUG] [org.apache.http.impl.conn.DefaultManagedHttpClientConnection] http-outgoing-143: Shutdown connection
16:52:04.816 [DEBUG] [org.apache.http.impl.execchain.MainClientExec] Connection discarded

[bitkid]

but no exception .. nothing

[bitkid]

what is also really weird .. normal dependencies update just fine .. it seems it's only related to gradle plugins

[bitkid]

i have the proxy entered in my gradle.properties file .. does this also apply for the plugins?

[GarouDan]

Have you already tried these other approaches here? https://stackoverflow.com/questions/5991194/gradle-proxy-configuration

Using gradle-wrapper.properties, systemProp or the the inline arguments?

[bitkid]

as i said .. the proxy is configured in gradle.properties and it works for normal deps

[bitkid]

only gradle plugins are not workin

[bitkid]

g

[wakingrufus]

maybe its an https thing?

[wakingrufus]

like maybe they disabled http connections ont he plugins repo or something and your proxy doesnt work with https?

[bitkid]

i think it's a certificate issue .. our proxy does something like a man in the middle attack and adds a certificate

[bitkid]

i try adding our certificates to a local trust store and pass it to gradle .. but so far without success 😞