James Strachan has talked openly about fundamental flaws in Jelly. Things that are not easily fixed such as the JellyContext, class loading, and ThreadLocal variables (this is off the top of my head so I'm not sure if this last statement is verbatim). Jelly has some huge memory leaks. You should never call it from the main thread.
Anyway, this is one of the reasons why Maven is leaving Jelly behind. I have encountered some of these issues, but I use Jelly for XML processing and creation. Beanshell can do anything that Jelly can do, but I find Jelly's syntax for XML fairly intuitive, in that the resulting document looks very much like the Jelly script that created it.
Christopher Farnham Senior Consultant at Wrycan, Inc.
chris.farnham{at}wrycan{dot}com
http://www.wrycan.comPaul Libbrecht wrote:
So that means you're going to actually talk to the ant tasks programmatically... mmmh... I wonder how readable this will end.
Not that jelly was a biest in readability but ant has definitely achieved an amount in readability which java really can't do.
paul
On 1-Apr-04, at 21:41 Uhr, Emmanuel Venisse wrote:
For Maven2, we'll rewrite all plugins. They will be write in Java and will be more extensible.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
