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: |New copied class/package name +
  (3.0 and above)
  |Notes
  3+^| *Module: groovy*
  | groovy.xml.QName
  | groovy.namespace
  | You need to migrate to using the new class at the same time as you migrate to affected modules
  using that class as a parameter in methods including `groovy-ant` and `groovy-xml` but only if you
  are using methods with `QName` parameters. You can continue to use the legacy class in your existing
  code or with the legacy versions of affected classes until Groovy 4.
  3+^| *Module: groovy-ant*
  | groovy.util
  | groovy.ant
  | Add an `import groovy.ant.AntBuilder` to classes/scripts
  using `AntBuilder` or you will still be using the deprecated version.
  3+^| *Module: groovy-console*
  | groovy.ui.ConsoleApplet
  | N/A
  | The `java.applet` API is deprecated. No replacement is planned for this Groovy class in Groovy 4.
  