[GRADLE-1931] Settings from gradle.properties are being ignored Created: 15/Nov/11  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 1.0-milestone-5
Fix Version/s: None

Type: Bug
Reporter: Stefan Schlott Assignee: Unassigned
Resolution: Won't Fix Votes: 1


I've got some settings in my <user.home>/.gradle/gradle.properties for setting up the company's proxy:


This worked great up to 1.0-m3, but after upgrading to 1.0-m5, gradle refused to download any dependencies. Wireshark showed that gradle tried to connect to the repositories directly, despite the proxy configuration. Passing the proxy settings via environment variable proved to be a workaround:

GRADLE_OPTS="-Dhttp.proxyHost=proxyname -Dhttp.proxyPort=3128" gradle ...

So I suppose gradle-1.0-m5 simply ignores the gradle.properties file.

Comment by Stefan Schlott [ 15/Nov/11 ]

More experiments, further observations I've been experimenting with both the DOS box and the cygwin command line.

When running from the DOS box, everything seems fine; when running from cygwin, the aforementioned problem occurs. I noticed that gradle won't access the contents of <user.home>/.gradle; instead, it creates a new subdirectory .gradle in my project directory. This explains why my properties file is no longer found. Unfortunately, I cannot explain why this happens

Comment by Matthieu Leclercq [ 21/Nov/11 ]

I have the same issue with milestone-5 and milestone-6 (worked on milestone-4 and above). But the 'GRADLE_OPTS' workaround does not work for me.

Comment by Alexander Klein [ 22/Nov/11 ]

For me, using cygwin, the workaround only works for M5, but not for M6.

Comment by Maxime Cowez [ 15/May/12 ]

The problem is still there in RC3, both in the DOS terminal and in Cygwin.
The workaround also doesn't work for me.
Win7 32 bit / Cygwin 1.7.14-2 / Gradle RC3

Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

Generated at Wed Jun 30 12:08:13 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.