[GRADLE-3452] Non-abstract getters of managed types are not directly accessible via model input DSL Created: 11/May/16  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Bug
Reporter: Mark Vieira (Inactive) Assignee: Unassigned
Resolution: Won't Fix Votes: 0


This issue was originally reported on the forums: https://discuss.gradle.org/t/implemented-properties-of-a-managed-type-are-not-accessible-using-model-path/17558

Given the following build script:

abstract class MyManagedType {
    public abstract String getProp1();
    public abstract void setProp1(String prop1);

    public String getProp2() {
        return getProp1().toUpperCase();

class Rules extends RuleSource {
    void foo(MyManagedType m) {}

apply plugin: Rules

model {
    foo {
        prop1 = 'bar'
    tasks {
        printProperty(Task) {
            doLast {
                println $.foo.prop2

Running gradle printProperty results in the following error:

FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring root project 'gradle'.
> The following model rules could not be applied due to unbound inputs and/or subjects:
    printProperty(org.gradle.api.Task) { ... } @ build.gradle line 23, column 9
        - tasks.printProperty Object
        - foo.prop2 Object (@ line 25) [*]
            suggestions: foo.prop1
  [*] - indicates that a model item could not be found for the path or type.

It seems that changing the code to reference the property indirectly does indeed work.

def foo = $.foo
println foo.prop2

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 [ 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.

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