anchor.diff:  If this is difficult, you can use the old class (and directly use the related `NioGroovyMethods` methods)
   until you are ready to migrate.
   You should not mix and match old and new classes.
  -3+^| Module: groovy-test
  +3+^| *Module: groovy-swing*
  +| org.codehaus.groovy.binding
  +| org.apache.groovy.swing.binding
  +.3+| You can continue to use the old classes if you use them in your existing code or from within legacy classes still
  +using the old classes. `SwingBuilder` now uses the bew classes.
  +| groovy.model
  +| groovy.swing.model
  +| groovy.inspect.swingui
  +| org.apache.groovy.swing.table
  +3+^| *Module: groovy-test*
   | org.codehaus.groovy.runtime. +
   ScriptTestAdapter
   | org.apache.groovy.test
  
positive.code: |===
  
  [[Groovy3.0releasenotes-Splitpackages]]
  == Split package changes
  
  The Java Platform Module System requires that classes in distinct modules
  have distinct package names. Groovy has it's own "modules" but these haven't
  
negative.code: get the deprecated version. You will need to do this before Groovy 4.
  | groovy.lang
  | groovy.test
  3+^| *Module: groovy-xml*
  | groovy.util
  | groovy.xml
  | For classes like `XmlParser` and `XmlSlurper`, you need to import `groovy.xml.XmlParser` and `groovy.xml.XmlSlurper` respectively to not
  