Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Message-ID: <002301c43229$08efd5c0$9ccf9a51@oemcomputer>
From: "Stephen Colebourne" <scolebourne@btopenworld.com>
To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
References: <20040504213439.4633.qmail@web50604.mail.yahoo.com>
 <6D4DC648-9E14-11D8-ABE2-003065DC754C@blueyonder.co.uk>
Subject: Re: [digester] local ArrayStack implementation not
 backwardscompatible?
Date: Tue, 4 May 2004 23:42:09 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

From: "robert burrell donkin" <robertburrelldonkin@blueyonder.co.uk>
> maybe we could sidestep this issue by including the two collections
> classes (ArrayStack and Buffer) that beanutils depends upon (either
> directly or indirectly) within the beanutils release and removing the
> collections dependency. since the versions of these classes in
> collections 2.1 and 3.0 seem to differ only in licensing and
> documentation, this would make beanutils and digester compatible with
> both 2.1 and 3.0 collections.

I am in favour of removing the direct dependency on [collections]. The
proposed solution of copying the two classes to digester (no package rename)
is fully acceptable to me, and I will happily add comments to [collections]
noting that the copy has occurred (or you could add the comments to
collections yourself ;-).

I have no plans to update either Buffer or ArrayStack, nor are there any
known issues. They are very stable classes, and well suited to this kind of
copy.

Stephen


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