Jenkins Pipelines are a very specific usecase for KlumAST, so this might break until Jenkins switches to Groovy 2.5 or we can transform using 2.5 but still use the tranformed classes in 2.4
KlumAST needs to be written partly in Groovy instead of Java (speed?)
Supporting 2.4 and 2.5 simultaneously would be an extreme effort
Code could tremendously improve by using the new Macor feature in Groovy 2.5 (http://www.groovy-lang.org/metaprogramming.html#_macros)
However, this has some caveats: