[GRADLE-1121] Support ConfigSlurper-based user configuration file. Created: 17/Aug/10  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Improvement
Reporter: Peter Ledbrook Assignee: Unassigned
Resolution: Won't Fix Votes: 0


Please consider supporting a ConfigSlurper-based configuration file in addition to gradle.properties. The particular reason I would like this is so that I can conditionally set an HTTP proxy. But I imagine there are other uses too.

Also, it would be really nice if I could set a proxy that works for both download and upload repositories. MavenDeployer is simply broken for me. I'm ranting a bit, but I'm frustrated at not being able to upload the Grails Gradle plugin from work.

Comment by Hans Dockter [ 17/Aug/10 ]

This is on the list of things to do. We want to provide project and user specific init scripts. There are many use cases for this. You can already put an init.gradle in your GRADLE_USER_HOME. This will be executed as part of every gradle project.

Comment by Hans Dockter [ 17/Aug/10 ]

For the conditional proxy problem the global init script should be in fact the right solution.

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 11:47:26 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.