commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Niall Pemberton <>
Subject Re: [JELLY] Branch to prepare for JEXL-2.0 enhancements?
Date Wed, 06 Jan 2010 10:07:46 GMT
On Wed, Sep 16, 2009 at 7:06 PM, Paul Libbrecht <> wrote:
> Henri,
> Some people might even say the whole of Jelly is dormant, and indeed, I, as
> many other jelly committers have been unable to find cycles to simply fix
> the most elementary things such as the wrong "how-to-start".
> Maven 2 is not using Jelly, that was one of the reason for them to move to
> maven2, I've been told. Last I tried to bring it back in an m2 project, I
> failed to find any possibility to include it.
> Jelly is used here and there in not so visible projects... that's my blurred
> estimate. Since jelly is glue oriented, it is typically not so visible and
> could often be replaced by another glue, e.g. groovy, beanshell,
> shell-scripting with some greps and xslt... therefore an estimate is real
> hard to make.
> Your approach to only fix jelly-core may be quite good. The solutions you'd
> find might well apply to the other tag-libs...

I did some work in a branch at the end of last year to create an m2
build for jelly:

> Challenges of porting to m2 include:
> - tag-docs generation (xdoclet under the hood)

I provided a 2 step mechanism (1st step in m2 and 2nd step using ant)
to generate the tag-docs - the comments in the ant build describe how
to do it:

The only problem is the m1 plugin handled special html characters from
the text extracted from the javadocs just fine, but for some reason
running the jelly script outside of m2 doesn't and any that containing
escaped special html characters generate invalid xdocs. So this needs
to be resolved.

> - probably some distribution targets (maybe not so bad)

> - unit testing of jelly files

Works just fine once I made the following change:

> - overall web-site generation

I was having some problems with this - javadoc generation took forever.


> paul
> Le 16-sept.-09 à 16:21, Henrib a écrit :
>> If it is welcome and useful, I'd say it is worth at least a try then. :-)
>> I was only considering the JELLY "core" project though; in theory, if the
>> API does not change and new behaviors come with new APIs - or through
>> options/properties - it should not break compatibility.
>> We can even consider the upwards compatibility as a "must have" feature of
>> this update if necessary.
>> Trying to gage usefulness, are there heavy-weight active projects using
>> Jelly ? (is Maven 2 using it?)
>> We might also "restrict" the list of sub-projects that would benefit from
>> this to-be branch to a subset, those with a still active community and
>> avoid
>> spending efforts on "dormant" ones.
>> WDYT ?

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message