[GRADLE-2513] GRADLE_USER_HOME doesn't resolve correctly running under cygwin Created: 08/Oct/12  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: 1.2
Fix Version/s: None

Type: Bug
Reporter: Kirk Rasmussen Assignee: Unassigned
Resolution: Won't Fix Votes: 1


I tried the following use cases under Cygwin for Windows:

1) Setting an environment variable named GRADLE_USER_NAME=/cygdrive/x/gradle results in gradle user home being redirected to /cygdrive/x/cygdrive/x/gradle (NOTE the duplicate path).

2) Using -Dgradle.user.home=/cygdrive/x/gradle from the command line results in gradle user home being redirected to ./cygdrive/x/gradle (i.e. the current folder )

3) Using -Dgradle.user.home=`cygpath -w /cygdrive/x/gradle' does the right thing.

4) Using ~/.gradle/gradle.properties doesn't seem to work at all (i.e. still using default location).


I tried putting this .gradle/gradle.properties file in both my Windows home directory and the cygwin home directory since they are distinct at the moment. When running with default settings it seems to use the Windows home directory which IMO is the correct thing to do.

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:24:00 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.