On 21 August 2013 07:58, Benedikt Ritter <brit...@apache.org> wrote: > 2013/8/19 sebb <seb...@gmail.com> > >> The Groovy version used by JCI is very out of date. >> >> I've updated it to the most recent of the 1.7 series, but since then >> there has been 1.8 and 2.0, as well as 2.1.x which is the current >> series. >> >> Should JCI update to one of the more recent versions? >> >> I don't have amy experience of Groovy versions so I don't know if >> there are good reasons for sticking with 1.7. >> >> For example, Python 2 and Python 3 are rather different beasts; is the >> same true of Groovy? >> > > I believe so.
In which case, do we need several groovy compilers? Or do we just support the latest? Or, if we are very lucky, the compiler API is the same, and users can provide whichever groovy jar they want. > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org >> >> > > > -- > http://people.apache.org/~britter/ > http://www.systemoutprintln.de/ > http://twitter.com/BenediktRitter > http://github.com/britter --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
