From dev-return-116450-apmail-commons-dev-archive=commons.apache.org@commons.apache.org Wed Oct 14 16:12:23 2009 Return-Path: Delivered-To: apmail-commons-dev-archive@www.apache.org Received: (qmail 18548 invoked from network); 14 Oct 2009 16:12:23 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 14 Oct 2009 16:12:23 -0000 Received: (qmail 90972 invoked by uid 500); 14 Oct 2009 15:55:37 -0000 Delivered-To: apmail-commons-dev-archive@commons.apache.org Received: (qmail 90892 invoked by uid 500); 14 Oct 2009 15:55:36 -0000 Mailing-List: contact dev-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Commons Developers List" Delivered-To: mailing list dev@commons.apache.org Received: (qmail 90882 invoked by uid 99); 14 Oct 2009 15:55:36 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 Oct 2009 15:55:36 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jak-commons-dev@m.gmane.org designates 80.91.229.12 as permitted sender) Received: from [80.91.229.12] (HELO lo.gmane.org) (80.91.229.12) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 Oct 2009 15:55:26 +0000 Received: from list by lo.gmane.org with local (Exim 4.50) id 1My6Bt-0000kh-LO for dev@commons.apache.org; Wed, 14 Oct 2009 17:55:05 +0200 Received: from 84-73-59-63.dclient.hispeed.ch ([84.73.59.63]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 14 Oct 2009 17:55:05 +0200 Received: from guillaume.deflache by 84-73-59-63.dclient.hispeed.ch with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 14 Oct 2009 17:55:05 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: dev@commons.apache.org From: =?ISO-8859-1?Q?Guillaume_D=E9flache?= Subject: Re: [JELLY] Branch to prepare for JEXL-2.0 enhancements? Date: Wed, 14 Oct 2009 17:50:49 +0200 Lines: 54 Message-ID: <4AD5F359.2090808@wyona.com> References: <25436184.post@talk.nabble.com> <25473476.post@talk.nabble.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 84-73-59-63.dclient.hispeed.ch User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) In-Reply-To: Sender: news X-Virus-Checked: Checked by ClamAV on apache.org Hi all! Would you guys consider doing a 1.0.2 release any time soon too? Paul Libbrecht a écrit : > Some people might even say the whole of Jelly is dormant, and indeed, I, Indeed, before seeing this thread I was about to send a "is-Jelly-dead?" probe message instead of this! ;) > 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". One thing that we would very much like to be in the next point release would be the fixes in that have already been tested and committed in Jelly-core's trunk, but never released. E.g. the "Allow Expressions to throw exceptions" and " Jelly should throw an exception if an unknown tag is used in a TagLibrary" improvements (resp. and ) would also be helpful to anyone developing with Jelly IMHO. Also if going the Java >= 1.5 route you might consider fixing the apparently trivial "nested exceptions are displayed incorrectly with JellyException" bug (). [...] > 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. For us because of these bugs and some other ones it's becoming more of a legacy library (we may try to move on to StringTemplate or even retreat to XSLT again), hence the dire need to get at least a more maintainer-friendly behaviour. FYI we only need Java 1.5+ compatibility and reducing dependencies is always welcome! :) Regards, Guillaume P.S.: I initially wrote some blurb about this in then in without answer: I guess I should have come here in the 1st place, else please so tell me/point me to what is deemed appropriate for Commons. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org For additional commands, e-mail: dev-help@commons.apache.org