[
https://issues.apache.org/jira/browse/GROOVY-9904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17270116#comment-17270116
]
Romain Bioteau commented on GROOVY-9904:
----------------------------------------
Hi [~paulk]
Is there a way of detecting all those deprecated methods that has been removed
between 2.5.x and 3.0.x ?
I'm not personnaly using this method, but they are part of the groovy API and
as a developer of a platform that executes third party groovy code, I'd like to
be able to anticipate the impact of migrating to 3.0.x.
> DefaultGroovyMethods.size() breaking change in 3.0.x
> ----------------------------------------------------
>
> Key: GROOVY-9904
> URL: https://issues.apache.org/jira/browse/GROOVY-9904
> Project: Groovy
> Issue Type: Bug
> Components: groovy-runtime
> Affects Versions: 3.0.7
> Reporter: Romain Bioteau
> Priority: Major
>
> {code:java}
> org.codehaus.groovy.runtime.DefaultGroovyMethods.size(StringBuffer sb) {code}
> doesn't have the same behavior between 2.5.x and 3.0.x
> {code:java}
> assert org.codehaus.groovy.runtime.DefaultGroovyMethods.size(new
> StringBuffer('test')) == 4 // true in 2.5.x
> assert org.codehaus.groovy.runtime.DefaultGroovyMethods.size(new
> StringBuffer('test')) == 4 // false in 3.0.x, expected 1{code}
> I didn't find any explanation about this change in the release note.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
