[GRADLE-2850] Deal with the case where the class defines both a `get` method and an `is` method Created: 29/Jul/13 Updated: 10/Feb/17 Resolved: 10/Feb/17 |
|
| Status: | Resolved |
| Project: | Gradle |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Adam Murdoch | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Description |
|
Need to deal with the case where the class defines both a `get` method and an `is` method for a property. For example, `CompileOptions.debug` has both methods. Can you also deprecate one of the `get` or `is` methods for these properties on `CompileOptions`: debug and failOnError. |
| Comments |
| Comment by Luke Daley [ 08/Aug/13 ] |
|
What exactly should we do? Collect all the annotations and merge from both? |
| Comment by Adam Murdoch [ 12/Aug/13 ] |
|
I'd say you have to put the annotations on one location, either one of the methods or the field, and it's an error if they're spread across multiple locations. |
| 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. |