James Daugherty created GROOVY-11512: ----------------------------------------
Summary: Inconsistent isAttribute & getAttribute behavior in Groovy 4 with traits Key: GROOVY-11512 URL: https://issues.apache.org/jira/browse/GROOVY-11512 Project: Groovy Issue Type: Bug Components: Compiler Affects Versions: 4.0.0 Reporter: James Daugherty As a follow-up to GROOVY-10621: >From looking at the following class in groovy 4: {code:java} class Testing { boolean deleted } {code} This will generate `getDeleted()` & `isDeleted`, but if a trait adds the property like this code: {code:java} trait ParentTesting { boolean deleted } class Testing implements ParentTesting { } {code} It will generate only the isDeleted() and not the getDeleted() on the testing class. Also, the behavior change mentioned in GROOVY-10621 is not meanted in the Groovy 4 release notes. Can this behavior either be made consistent or reverted to pre-groovy 4 behavior? -- This message was sent by Atlassian Jira (v8.20.10#820010)