commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matt Benson <>
Subject Re: [ALL] BCEL and JCS as Commons components?
Date Thu, 16 Jun 2011 15:03:16 GMT
First, I'm glad to see I'm not the only one who hadn't heard of JCS.
Considering [1], I'd say it's more relevant now than, arguably, ever.
I'd like to work on it.  From the Jakarta threads, Thomas Vandahl
offered to step up, so given our low bar for existing ASF committers,
it should have enough care to ensure its welfare.  Not 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.  I guess I'm saying these components probably should have
been under the Commons umbrella as soon as it "opened."  If they can't
thrive here, they can be stuffed in the attic later, but what can it
hurt to bring them in and see what happens?



On Thu, Jun 16, 2011 at 9:52 AM, sebb <> wrote:
> On 16 June 2011 14:53, Torsten Curdt <> wrote:
>> <snip/>
>> Given that I have looked a bit after BCEL over the past few years here
>> are my two cents:
>> BCEL development is dead dead dead ... still people come and use it.
>> Why they don't use ASM is beyond me. I myself use ASM whenever I can.
> Just checked Findbugs and they seem to be using ASM and BCEL, so
> perhaps they have found something that BCEL does better than ASM?
>> For those how want "easier" I would suggest javassist ...if it wasn't LGPL
>> (although I heard it is now dual licensed LGPL + MPL)
>> That said BCEL trunk has quite some major fixes and changes.
>> Due to lack of feedback and testers this has never been released.
>> And I don't see that happening anytime soon.
>> BCEL is one of the few failed Apache communities.
>> A couple people/groups/projects have forked it without ever contributing back.
>> This would have been crucial for this so very specialized code base.
>> Not pointing fingers - it was very poorly maintained before.
>> After the years I have given up hope on BCEL.
>> Being part of Commons ... hm ... doesn't feel right.
>> Who would step up and work on it here? (anyone?)
> If there is a need for a new release, I would work on it.
>> IMO attic would reflect the reality. Just not sure whether we should
>> do a release before or not.
>>> Regarding Tomcat usage - it might be of interest to the new commons
>>> sandbox component - formerly Meiyo. Tomcat 7 uses BCEL to scan
>>> annotations without the need to load classes through a class loader.
>> With all honesty - it should switch to ASM and not look back.
>> cheers,
>> Torsten
>> --
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> For additional commands, e-mail:
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

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

View raw message