2 May
2007
2 May
'07
4:10 p.m.
A quick check replacing groovy-all-1.0-jsr06.jar with groovy-all-1.0.jar
shows 4 errors in GroovyTemplateEngine.
There seems to be a typo in the old Groovy version, naming a method
MetaClassRegistry.getIntance() (instead of getInstance() - note the
missing 's').
Renaming those methods makes XWiki compilable (at least in Eclipse), so
I don't think there would be a big problem to use the Groovy 1.0 release
- as long as there are no Groovy scripts somewhere that might break due
to changes in the Groovy language itself.
cya
Michael
Vincent Massol schrieb:
Hi Michael,
On Apr 30, 2007, at 8:08 PM, Michael Baehr wrote:
Quite some time ago I asked whether there are
plans to upgrade the
included version of Groovy from JSR-06 to the 1.0 release.
I never got an answer, and I see that no version change occurrred in
the last release candidate.
Is Groovy used in a standard installation and can I replace the
corresponding jar myself without breaking anything?
The general answer is "yes we would like to use it". I think the
reason we haven't migrated yet is because we were worried it would
break something and we wanted to release 1.0 ASAP. But personally I
agree that we should have tried the upgrade earlier.
It's a bit late now to try the upgrade as we're in RC stages for the
1.0 release but we should definitely do it in early 1.1 releases.
I don't know if anything will break but it's very likely the core will
need to change to work with groovy 1.0. If others know more, please
chime in.
Thanks
-Vincent