Uploaded image for project: 'Gradle'
  1. Gradle
  2. GRADLE-1121

Support ConfigSlurper-based user configuration file.

    Details

    • Type: Improvement
    • Status: Open
    • Resolution: Unresolved
    • Affects Version/s: 0.9
    • Fix Version/s: None

      Description

      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.

        Activity

        Hide
        hans_d Hans Dockter added a comment -

        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.

        Show
        hans_d Hans Dockter added a comment - 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.
        Hide
        hans_d Hans Dockter added a comment -

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

        Show
        hans_d Hans Dockter added a comment - For the conditional proxy problem the global init script should be in fact the right solution.
        Hide
        bmuschko Benjamin Muschko added a comment -

        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!

        Show
        bmuschko Benjamin Muschko added a comment - 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!

          People

          • Assignee:
            Unassigned
            Reporter:
            pledbrook Peter Ledbrook
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:

              Development