[GRADLE-2616] Remove creating of named container elements via property read in container configuration closures Created: 03/Jan/13 Updated: 10/Feb/17 Resolved: 10/Feb/17 |
|
| Status: | Resolved |
| Project: | Gradle |
| Affects Version/s: | 1.3 |
| Fix Version/s: | None |
| Type: | Improvement | ||
| Reporter: | Luke Daley | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Issue Links: |
|
||||||||
| Description |
|
Currently, to create a named element in a container you can simply read a variable with the name you want. For example, to create a configuration called 'custom'…
configurations {
custom
}
The problem is that this uses a surprising resolution strategy. It is effectively DELEGATE_FIRST, if the delegate has it, then owner, then propertyMissing() on the delegate if the owner doesn't have it. This is at odds with with our otherwise universal use of DELEGATE_FIRST. This behaviour should be removed, which would mean that users would need to effectively invoke the method with this name.
configurations {
custom { }
}
|
| 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. |