anchor.diff:  | groovy.inspect
   | groovy.console
   .3+| `groovyConsole` is normally used as a command-line tool and its use in that form is unaffected.
  -     If you use any of the classes directly you can use the old versions until you migrate.
  -     You should not mix and match old and new classes.
  +If you use any of the classes directly you can use the old versions until you migrate.
  +You should not mix and match old and new classes.
   | groovy.inspect.swingui
   | groovy.console.ui
   | groovy.ui
  
positive.code: You won't be able to use any of the new language features with the old parser.
  The old parser is deprecated and will be removed in Groovy 4.
  |===
  
  [[Groovy3.0releasenotes-Splitpackages]]
  == Split package changes (from beta-2)
  
negative.code: | groovy.util
  | groovy.xml
  | For classes like `XmlParser` and `XmlSlurper`, you need to import `groovy.xml.XmlParser` and `groovy.xml.XmlSlurper` respectively to not
  get the deprecated versions. You will need to do this before Groovy 4. If you are using `groovy.xml.XmlUtil.serialize` on a
    `groovy.util.slurpersupport.GPathResult`, you will need to swap to using the deprecated methods in `groovy.util.XmlUtil` since
    `groovy.xml.XmlUtil` only handles the new classes.
  | org.codehaus.groovy.tools.xml.DomToGroovy
  