[GRADLE-1223] Support property preconditions, prompting and persistence Created: 17/Nov/10 Updated: 10/Feb/17 Resolved: 10/Feb/17 |
|
| Status: | Resolved |
| Project: | Gradle |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | ||
| Reporter: | Chris Beams | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Description |
|
Per conversations with Hans: Support a section in the build script where required properties are specified. Search for those properties very early in the build lifecycle. If a property is not (a) assigned at task configuration time, (b) specified in the project's gradle.properties (c) specified in $HOME/.gradle/gradle.properties, then fall back to a prompt. Give users the option at that prompt to persist the value of that property in the location of their choice. Provide an option to encrypt sensitive passwords on persistence. Provide INFO level logging that shows the system's algorithm for determining property values. Use the output of ssh -v for inspiration. |
| Comments |
| 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:
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. |