anchor.diff:  [[Groovy2.5releasenotes-Moreinformation]]
   == More information
   
  -You can browse all the link:../changelogs/changelog-2.5.0.html[tickets closed for Groovy 2.5 in JIRA].
  +You can browse all the link:../changelogs/changelog-2.5.0.html[tickets closed for Groovy 2.5.0 in JIRA].
  
positive.code: had to become familiar with the compiler's internal representation of
  Groovy syntactic structures. But that has now changed.
  
  Groovy 2.5 supports macros. Macros let you use Groovy syntax directly
  rather than using the internal compiler representations when creating
  compile-time metaprogramming extensions. This puts the creation of transformations
  in the hands of all Groovy programmers not just Groovy compiler gurus.
  
negative.code: part of it for handling commandline processing, then you might notice that it has been converted to picocli and usage
  of a handful of methods will throw a DeprecationException which mentions the alternative approach you should use.
  
  [[Groovy2.5releasenotes-Knownissues]]
  == Known issues
  
  * The GDK documentation for the java.time extensions wasn't included in the release.
  It will be included in the first maintenance release (2.5.1) but can be found in the meantime at:
  http://docs.groovy-lang.org/docs/groovy-2.5.1-SNAPSHOT/html/groovy-jdk/
  * Users of `groovy.util.CliBuilder` need to also include the `org.codehaus.groovy:groovy-cli-commons`
  dependency on their compile classpath in addition to `groovy` or `groovy-all`. This won't be required
  after the next maintenance release but users should migrate away from that class in any case as it
  will be removed from the next major version of Groovy.
  * Users of Spock 1.1-groovy-2.4 may find strange ClassCastException errors with some tests, e.g. with `cleanup:`
  clauses. Using Spock 1.2-groovy-2.4-SNAPSHOT from the https://oss.sonatype.org/content/repositories/snapshots/
  repo may help but work is on-going to improve Spock support.
  * Users combining final and `@CompileStatic` or final and Spock may see errors from
  the final variable analyzer. Work is underway to resolve those error messages.
  * Users needing the groovy-xml module and running on JDK9 and above may need to use
  the `--add-modules java.xml.bind` command-line option to fix the break in backwards
  compatibility in JDK9+.
  * JDK9+ produces warnings with many libraries including Groovy due to some planned
  future restrictions in the JDK. Work is underway to re-engineer parts of Groovy
  to reduce/remove those warnings. Users wanting to hush the warnings as an interim
  measure may consider using the add-opens escape clause offered by JDK9.
  See commit 92bd96f (currently reverted) on the Groovy master branch for a potential
  list to add.
  
  [[Groovy2.5releasenotes-JDKrequirements]]
  == JDK requirements changes
  
  