Breaking Changes

Conflicting isser and getter methods

If you are using objects of classes that implement conflicting isser and getter methods and you are using the property syntax to get the getter value, your code can break with Groovy 4.

Fix

In Groovy 4, if you are using objects of classes that implement conflicting isser and getter methods, and using the property syntax to get the getter value, you must re-write the logic to use the getter method directly.

For example, in Groovy 2, the get call below returns the value of JsonArray object (contents of array), and the JsonNode class has conflicting isser and getter methods:

def theArray = get("/rest/api/2/issuetype")
        .header('Accept', 'application/json')
        .asJson().body.array
 
theArray // In Groovy 2 this is used to return the value of getArray() method of JsonNode

In Groovy 4, theArray will be the return value of the method isArray() of JsonNode. So the above code should be written as:

def theArray = get("/rest/api/2/issuetype")
        .header('Accept', 'application/json')
        .asJson().body.getArray()

Node not found and issues related to getter functions in Groovy

The Groovy 2 import statement import groovy.util.slurpersupport breaks with Groovy 4.

To fix your scripts that use that import statement, please replace the package name with import groovy.xml.slurpersupport.

Unable to resolve class XmlSlurper

The Groovy 2 import statement import groovy.util.XmlSlurper breaks with Groovy 4.

To fix your scripts that use that import statement, please replace it with import groovy.xml.XmlSlurper.

Unexpected input for ,

The new Groovy 4 parser does not allow empty objects in an array list. Scripts with code like "a","b",,"c","d" breaks with Groovy 4.

To fix your scripts that have empty arrays or lists, please remove the empty objects by adding quote marks ( ""), like "a","b","","c","d".