[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

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

Type: Bug
Reporter: Mark Vieira (Inactive) Assignee: Unassigned
Resolution: Duplicate Votes: 2


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:

apply plugin: 'base'
task foo
assemble.dependsOn foo
apply plugin: 'java'

The result is the following error:

FAILURE: Build failed with an exception.

* Where:
Build file '/Users/mark/Desktop/gradle/build.gradle' line: 4

* What went wrong:
A problem occurred evaluating root project 'gradle'.
> Failed to apply plugin [class 'org.gradle.language.base.plugins.LanguageBasePlugin']
   > Cannot add rule org.gradle.language.base.plugins.LanguageBasePlugin$Rules#attachBinariesToAssembleLifecycle(org.gradle.api.Task, org.gradle.platform.base.BinaryContainer) for model element 'tasks.assemble' at state Initialized as this element is already at state GraphClosed.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.


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:

  • 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 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

Generated at Wed Jun 30 12:45:44 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.