On Thu, 2004-10-14 at 20:21, Nathan Coast wrote:
> Hi,
>
> I've read a few threads about jelly being dropped as the defacto
> scripting language for 2.0. If I'm developing a plugin, what's the best
> approach to minimise the effort when it eventually is moved to 2.0? I
> know 2.0 is still som
You should write as much as possible in Java then wrap it up in Jelly
(see artifact plugin for a reasonable example).
Jelly should continue to work, but Java will be preferred. There are
likely to be other alternatives too.
Cheers,
Brett
On Fri, 15 Oct 2004 08:21:52 +0800, Nathan Coast <[EMAIL P
Hi,
I've read a few threads about jelly being dropped as the defacto
scripting language for 2.0. If I'm developing a plugin, what's the best
approach to minimise the effort when it eventually is moved to 2.0? I
know 2.0 is still some way off.
I guess jelly tag classes are a big no? Should I
