You can try the latest Buildship snapshot which has a support for proxy settings. If you set the http/https proxy settings in the Eclipse preferences UI, Buildship and Gradle will automatically make use of it.
Update: starting from version 1.0.3, Buildship support working behind the firewall.
You’re saying that those are all the “proxy” system properties you’ve set? You’re setting “proxyHost” and “proxyPort”, but only for “https”, and you’re setting “proxyUser” and “proxyPassword”, but only for “http”. Seems pretty clear why you’re getting a 407. You’ve set the host:port, but not the user/password. The URL is using “http”, so it tries to use the settings for “http”, but you’ve only set the host and port.
I encountered a similar issue in the Eclipse environment. Although our corporate proxy does not require authentication Gradle kept complaining about 407 error code.
After adding bogus proxyUser and proxyPassword properties to the gradle.properties file the issue went away.
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.
Please use gradle.properties next to project’s build.gradle file to specify these settings:
systemProp.https.proxyHost=<proxyHost/DNS resolvable name>
systemProp.https.proxyPort=<port>
systemProp.https.proxyUser=<proxy-user>
systemProp.https.proxyPassword=<proxy-password>
systemProp.https.nonProxyHosts=localhost,127.0.0.1,<intranet domains>
Also please check in your <userhome>/.gradle/gradle.properties (Looks like Android Studio directly copies the IDEs proxy settings there without putting a password, instead of making it project local)