commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Henrib <>
Subject Re: [JELLY] Branch to prepare for JEXL-2.0 enhancements?
Date Wed, 16 Sep 2009 14:21:48 GMT

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.


polx wrote:
> Henri,
> this would be welcome but it might be quite hard since jelly and maven  
> 1 have been living hand in hand for a long time and there's still a  
> huge lot of maven.xml code in the many jelly projects.
> Le 14-sept.-09 à 15:54, Henrib a écrit :
>> It might be convenient to create a branch in Jelly to update it to  
>> Maven2 and
>> prepare for JEXL-2.0. I'd also wish to update to Java 1.5 and try to  
>> reduce
>> dependencies if it's possible.
>> Any "against" opinions ?
> Update to 1.5 (or even 1.6) is not an issue I think but you should ask  
> on commons-users.
>> I haven't tried (yet:-)) but out of curiosity, does JELLY require  
>> different
>> commit rights than JEXL?
> No, jelly is part of commons.
> paul

View this message in context:
Sent from the Commons - Dev mailing list archive at

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

View raw message