IntelliJ sbt Proxy Settings for Dependency Downloads

Put proxy JVM arguments in the sbt settings, then launch a new sbt process for imports or shell work.

IntelliJ's Check Connection tests the IDE's own route. It can pass while the separate sbt JVM cannot download a dependency.

  1. Open Settings → Build, Execution, Deployment → Build Tools → sbt.
  2. In the JVM settings, enter the needed properties in VM parameters as JVM arguments:
-Dhttp.proxyHost=proxy.example -Dhttp.proxyPort=8080
-Dhttps.proxyHost=proxy.example -Dhttps.proxyPort=8080

Use only the hostname from the chosen endpoint, without a URL scheme. The HTTP proxy list is a source of public candidates for this download route. The HTTPS property pair selects HTTPS downloads; it does not change the listener to a TLS proxy.

Launch a new sbt process after changing these inputs. An existing sbt shell retains its launch configuration. Check whether IntelliJ uses the sbt shell for imports or delegates builds to it so the failing operation uses that newly configured process.

If the failed operation is an IDE plugin download, use IntelliJ's HTTP Proxy settings instead. A separately launched application uses its run configuration and network client.

The four properties select a route. For a proxy authentication challenge, follow the advertised scheme and the actual sbt downloader's supported authentication settings.

Аффингæй хæстæг статьялтæ