17 May
2016
17 May
'16
10:17 p.m.
Denis Gervalle said:
Thanks, I did not know about this tool, which sounds excellent.
Yes, we only
maintain documentation for the latest version of XWiki on
xwiki.org (not enough manpower to have decent doc for several versions
ATM).
However, for version 6.2.5 and later, you have a way to mitigate this
limitation. You can install the Scripting Documentation Application on your
own wiki (see
http://extensions.xwiki.org/xwiki/bin/view/Extension/Scripting+Documenta
tion+Application).
Unless you are using XWiki prior to 4.2 , using Wiki
Component is definitely
the recommended way to writes Groovy components. Registering
components "by hand" from a groovy script has many drawbacks not only
the restart one, and you should avoid doing that. The best is of course to
write the components in Java, and install them as an extension.
I've found the ability to write small Groovy scripts as components has been very handy
and simpler than writing full extensions in Java. For utilities that I don't wish to
make into public extensions the burden of a small Groovy script into a proper extension
seems prohibitive (although that may just be that I haven't written one yet, and
I'm just a walker at the bottom of a hill complaining about how high it looks...).
Last time I asked there is was no simple way to install private extensions. Also, I
didn't have much luck writing a proper component in Groovy, which I sometimes prefer
to Java.