Bug#804156: warrant (restrictive) http*_proxy env variables

[Yaroslav Halchenko]

Package: gradle
Version: 2.5-3
Severity: wishlist

Most probably it is not gradle's issue but somewhere within Java's ecosystem of
libraries it uses.  I just have no clue in that world and would appreciate if
you forward this bug accordingly

It is quite often desired to restrict access to network and it is common to do
so by providing http_proxy env variable(s) to point to a bogus proxy server,
technique often used in debian/rules.  But it seems that gradle just ignores
those and happily downloads stuff from the web.

$> http_proxy=http://localhost:9 https_proxy=http://localhost:9 gradle build    
:compileJava
:processResources
:classes
:jar
:assemble
:compileTestJava
Download http://maven.xnat.org/libs-release/com/github/tomakehurst/wiremock/1.50/wiremock-1.50.pom
Download http://maven.xnat.org/libs-release/xmlunit/xmlunit/1.5/xmlunit-1.5.pom
...


-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.3.0-rc7+ (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gradle depends on:
ii  default-jre-headless    2:1.7-52
ii  libgradle-core-java     2.5-3
ii  libgradle-plugins-java  2.5-3

Versions of packages gradle recommends:
ii  default-jdk              2:1.7-52
ii  libcodenarc-groovy-java  0.17-2
ii  scala                    2.11.6-1

gradle suggests no packages.

-- no debconf information