[GRADLE-3321] Task created by rules cannot be configured by legacy code then mutated by further rules Created: 13/Jul/15 Updated: 24/Jan/17 Resolved: 24/Jan/17
|Reporter:||Mark Vieira (Inactive)||Assignee:||Unassigned|
Because of a limitation of the rules/legacy bridging, we have introduced a configuration ordering issue between model and legacy lands. Essentially, a task created by rules cannot be configured by non-rules code (legacy plugin, build script, etc) and then later mutated by further rules. Consider the following build script:
The result is the following error:
This issue was originally reported by this forum post: https://discuss.gradle.org/t/illegalstateexception-cannot-add-mutate-rule/10541
|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 Paul Shomo [ 21/Nov/16 ]|
Commenting to confirm that this issue has requisite context, impact, behaviors, and examples.
|Comment by Eric Wendelin [ 24/Jan/17 ]|
Moved to GitHub at https://github.com/gradle/gradle/issues/1242