Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Received-SPF: neutral (nike.apache.org: local policy)
From: Stefan Bodewig <bodewig@apache.org>
To: dev@commons.apache.org
Cc: dev@cocoon.apache.org
Subject: Re: [JEXL] Problem Integrating JEXL 1.x Branch and Cocoon 2.2.x
References: <871vbnd5cc.fsf@v35516.1blu.de>
	<1277977131122-2274885.post@n4.nabble.com>
	<87sk43bjm0.fsf@v35516.1blu.de>
Date: Sat, 03 Jul 2010 14:27:40 +0200
In-Reply-To: <87sk43bjm0.fsf@v35516.1blu.de> (Stefan Bodewig's message of
	"Thu, 01 Jul 2010 12:07:51 +0200")
Message-ID: <87fx00da2r.fsf@v35516.1blu.de>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

On 2010-07-01, Stefan Bodewig wrote:

> From a Gump POV if you ever expect to do another JEXL 1.x release we
> should keep tracking the branch and help the JEXL and Cocoon devs
> figure out which way to go.  If the branch is a dead-end anyway, we
> can as well stop tracking it and provide JEXL 1.1 to Cocoon which is
> known to work.

So I guess the question is whether anybody ever expects to do another
JEXL 1.x release from the branch (which, let me repeat, is incompatible
with JEXL 1.1).

Unless I hear anybody say anything else, I'm going to remove the JEXL
1.x branch builds from Gump and provide JEXL 1.1 to those projects that
depend on it sometime during the next week.

Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org