Then it is a bootstrapping issue. You can solve it either using an older binary version of Groovy to build the new version of Groovy, or writing enough of a Groovy interpreter in Java that you can build your compiler with it.
On 23 February 2016 at 12:47, Jochen Theodorou <blackd...@gmx.org> wrote: > > > On 23.02.2016 11:03, Alessio Stalla wrote: > >> Why is it hard to add to the build? Is it a bootstrapping issue? >> > > right now we have 2 steps, build the compiler, then use the new compiler > to build tests and runtime as well as modules. Since I need part of the > runtime for the compiler in my case, it cannot work like this, unless > enough of the runtime is Java to run the parts of the new compiler I am > using. This should be the case, but can be trouble in the future. > > bye Jochen >
