[GRADLE-1214] Provide command line option for specifying alternate ~/.gradle/gradle.properties file or no file at all Created: 10/Nov/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: Chris Beams Assignee: Unassigned
Resolution: Won't Fix Votes: 1


 Description   

We have two Gradle-based CI builds. The first is a nightly build that performs a complete release and makes use of properties in ~/.gradle/gradle.properties in the build user's home dir. This works as desired.

The second build triggers on every commit, and should not have any awareness of these same properties. There needs to be a switch at the command line in order to say 'ignore ~/.gradle/gradle.properties' entirely. It may also be useful to specify an alternate file as well.

 Comments   
Comment by Hans Dockter [ 16/Nov/10 ]

The use case is that one CI build should validate that you can use the build without a gradle.properties file. The properties that are set in this file are only needed by certain tasks.

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