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 (athena.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: <BANLkTimV20qYOCin=nqXnAbP_WHw3uOxPA@mail.gmail.com>
References: <BANLkTim5-8qTwLXx+WPaaofMPCDoDUM5iA@mail.gmail.com>
	<BANLkTimjvnLYeq1hcYYnsPRv0rLSob5Eeg@mail.gmail.com>
	<4DF9F4DA.7030908@apache.org>
	<BANLkTikeo0TX2f6Ma7tu2cCid0xett0f7g@mail.gmail.com>
	<BANLkTinAj9ZRu7ntmMYJpf=hJS=Ve2tA1A@mail.gmail.com>
	<BANLkTinOiV4zhp8yo6=Lk6bKtre71zEiJw@mail.gmail.com>
	<BANLkTimV20qYOCin=nqXnAbP_WHw3uOxPA@mail.gmail.com>
Date: Thu, 16 Jun 2011 18:15:58 +0200
Message-ID: <BANLkTikUzuSyqzbSe9osMfekQ0ziaufY4A@mail.gmail.com>
Subject: Re: [ALL] BCEL and JCS as Commons components?
From: Torsten Curdt <tcurdt@vafer.org>
To: Commons Developers List <dev@commons.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

>=A0Not sure what
> factors contributed to the stagnation of BCEL development, but I like
> to think of Commons as "the" swiss army knife for Java developers--any
> library with a sharply defined surface area and, even better,
> satisfying some need commonly encountered by Java developers, belongs
> here IMO.

So according to you byte code manipulation is a "commonly encountered
need" for java developers?
I guess then Commons should/could be the home of virtually any java
library out there.

...plus your favorite kitchen sink :)

That's not how I interpret our charter.

cheers,
Torsten

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