[
https://issues.apache.org/jira/browse/GROOVY-9904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17270121#comment-17270121
]
Paul King commented on GROOVY-9904:
-----------------------------------
I'd recommend using checkstyle and codenarc and IDE checks (or looking at Java
compiler warnings if calling from Java) which can tell you when you are calling
deprecated methods.
As hinted to earlier, if using from Groovy, you really shouldn't be calling
such methods directly but via the extension method form in which case there
should be no impact moving to 3.0.x.
Otherwise, if you are calling those methods directly (a bad practice and code
smell for sure) then you could look at the japicmp output (gradle
binary-compatibility subproject) when running the Groovy build.
> 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)
