Return-Path: X-Original-To: apmail-commons-dev-archive@www.apache.org Delivered-To: apmail-commons-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A96EF6BE1 for ; Thu, 16 Jun 2011 15:07:57 +0000 (UTC) Received: (qmail 78779 invoked by uid 500); 16 Jun 2011 15:07:57 -0000 Delivered-To: apmail-commons-dev-archive@commons.apache.org Received: (qmail 78704 invoked by uid 500); 16 Jun 2011 15:07:57 -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 78696 invoked by uid 99); 16 Jun 2011 15:07:57 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 Jun 2011 15:07:57 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of simone.tripodi@gmail.com designates 209.85.213.43 as permitted sender) Received: from [209.85.213.43] (HELO mail-yw0-f43.google.com) (209.85.213.43) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 Jun 2011 15:07:52 +0000 Received: by ywa6 with SMTP id 6so916306ywa.30 for ; Thu, 16 Jun 2011 08:07:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; bh=QDh9Ip/BleQbV7I5KUXtSdGcg7G6nhkoj5+WXkvTpQo=; b=ISUxLG4HcCqZe04Nzjt/khkivEOLojts+w4ZEdJ3unaz/eQwpW1QLfnA22kMlCXObc kI6nP6LUeg8uksRCF7/5JQCdlc6mPfIEipJZHuMmY6vbyuV7fgtY1bKHuw+j4p/e2r9U RSOSXN5zGZSGXD5BRV6cb5ewN1RW6T6o81y98= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=PODJiT+GxMHvaPU6hWbRQGmy0oqrOWjrKIVUVk6za8cbpOjOzAalaDo4qQ9naVXk+s q4EOSk0hca6ViBd0ww/V+OOTphrIOBPx6CMgYxjtjRw2udUDgf5a5F9n24Oh7y1baP/7 TSjcIEfX5GhBYr+O5fiGehK1szF2YjaoC1jUA= MIME-Version: 1.0 Received: by 10.151.116.17 with SMTP id t17mr578055ybm.375.1308236851928; Thu, 16 Jun 2011 08:07:31 -0700 (PDT) Sender: simone.tripodi@gmail.com Received: by 10.151.47.12 with HTTP; Thu, 16 Jun 2011 08:07:31 -0700 (PDT) In-Reply-To: References: <4DF9F4DA.7030908@apache.org> Date: Thu, 16 Jun 2011 17:07:31 +0200 X-Google-Sender-Auth: OR1t4JkAD2Zs4jluSIH16ZV-22s Message-ID: Subject: Re: [ALL] BCEL and JCS as Commons components? From: Simone Tripodi To: Commons Developers List , gudnabrsam@gmail.com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable +1 to Matt, wise said :) http://people.apache.org/~simonetripodi/ http://www.99soft.org/ On Thu, Jun 16, 2011 at 5:03 PM, Matt Benson wrote: > 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. =C2=A0From 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. =C2=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. =C2=A0I guess I'm saying these components probably should have > been under the Commons umbrella as soon as it "opened." =C2=A0If 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? > > Matt > > [1] http://groups.google.com/group/jsr107/browse_thread/thread/9a4153ee37= 5f44ae > > > On Thu, Jun 16, 2011 at 9:52 AM, sebb wrote: >> On 16 June 2011 14:53, Torsten Curdt wrote: >>> >>> >>> 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 L= GPL >>> (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 contributin= g 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 >>> -- >>> http://www.yourdailygeekery.com >>> http://www.torstencurdt.com >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org >>> For additional commands, e-mail: dev-help@commons.apache.org >>> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org >> For additional commands, e-mail: dev-help@commons.apache.org >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org > For additional commands, e-mail: dev-help@commons.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org For additional commands, e-mail: dev-help@commons.apache.org