[GRADLE-478] Provide declarative validation for task properties Created: 12/May/09  Updated: 24/Jan/17  Resolved: 24/Jan/17

Status: Resolved
Project: Gradle
Affects Version/s: 0.9
Fix Version/s: None

Type: Improvement
Reporter: Adam Murdoch Assignee: Unassigned
Resolution: Fixed Votes: 3


 Description   

For example, most tasks have certain mandatory properties, yet our tasks are inconsistent about checking whether a given property has been specified or not, and we end up with NPEs when the tasks execute. We should make it easy to declare that a given property is mandatory, so that Gradle can take care of the validation and providing feedback to the user.

Any validation could probably be applied to convention objects too.

 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:

  • 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 [ 24/Jan/17 ]

The functionality is handled by input/output annotations.

Generated at Wed Jun 30 11:31:08 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.