Expected Behavior
Running gradlew on a (Linux / Mac) system that has the http_proxy and / or https_proxy environment variables set should be able to download the configured Gradle distribution though the specified proxy.
Current Behavior
The gradlew script does not pass any proxy configuration from the http_proxy / https_proxy environment variables to the JVM that runs the Java implementation for the wrapper, resulting in the download of the Gradle distribution to fail on systems that can only access the Internet via a proxy.
Context
In environments behind a corporate proxy running a Gradle project's ./gradlew fails out of the box because the JVM does not know about the proxy even if http_proxy / https_proxy is set. A Gradle user has to manually pass the http(s).proxy* JVM system properties either directly to gradlew on the command line via -D, or configure them in the ~/.gradle/gradle.properties file.
This is inconvenient extra work and not in line with other package managers / build systems like e.g. Yarn which do respect http_proxy / https_proxy.
As such it would be nice if the gradlew script would by default parse http_proxy / https_proxy and pass the information on via the http(s).proxy* system properties to the JVM that runs the Java implementation for the wrapper.
Expected Behavior
Running
gradlewon a (Linux / Mac) system that has thehttp_proxyand / orhttps_proxyenvironment variables set should be able to download the configured Gradle distribution though the specified proxy.Current Behavior
The
gradlewscript does not pass any proxy configuration from thehttp_proxy/https_proxyenvironment variables to the JVM that runs the Java implementation for the wrapper, resulting in the download of the Gradle distribution to fail on systems that can only access the Internet via a proxy.Context
In environments behind a corporate proxy running a Gradle project's
./gradlewfails out of the box because the JVM does not know about the proxy even ifhttp_proxy/https_proxyis set. A Gradle user has to manually pass thehttp(s).proxy*JVM system properties either directly togradlewon the command line via-D, or configure them in the~/.gradle/gradle.propertiesfile.This is inconvenient extra work and not in line with other package managers / build systems like e.g. Yarn which do respect
http_proxy/https_proxy.As such it would be nice if the
gradlewscript would by default parsehttp_proxy/https_proxyand pass the information on via thehttp(s).proxy*system properties to the JVM that runs the Java implementation for the wrapper.