[
https://issues.apache.org/jira/browse/GROOVY-10708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17577666#comment-17577666
]
Sterling Greene commented on GROOVY-10708:
------------------------------------------
Thanks. I think we can live with this too.
I think we may special case `Boolean isFoo()` for Gradle tasks temporarily if
we find many cases of this.
> Property access for wrapped vs. primitive boolean
> -------------------------------------------------
>
> Key: GROOVY-10708
> URL: https://issues.apache.org/jira/browse/GROOVY-10708
> Project: Groovy
> Issue Type: Bug
> Affects Versions: 4.0.3
> Reporter: Kyle Moore
> Assignee: Eric Milles
> Priority: Major
>
> In upgrading our codebase from Groovy 3.0.11 to 4.0.3, we noticed the
> documented change that {{isXyz}} accessors returning a {{Boolean}} are no
> longer recognized as properties.
> This has the potential to break a few use-cases in Gradle where accessors
> returning {{Boolean}} are no longer included in
> {{MetaClass#getProperties()}}. We may be able to workaround this on our own,
> but are wondering if this behavior can be configured or modified in the 4.0.x
> timeline.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
