commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Torsten Curdt <tcu...@vafer.org>
Subject Re: [weaver]/[bcel] WAS [privilizer] promotion plan
Date Tue, 04 Dec 2012 23:01:22 GMT
I would suggest to go with ASM instead ...unless there are people that are
eager to work on BCEL.

cheers,
Torsten


On Tue, Dec 4, 2012 at 11:54 PM, Matt Benson <gudnabrsam@gmail.com> wrote:

> Well, it looks like the most comfortable avenue for everyone is Commons
> [weaver].  IMO [weaver] would look like a framework for implementing any
> kind of code weaving, so the most important decision is the look of the
> API, and it would seem that eating our own dog food would be appropriate in
> Commons.  Thus I would propose that [weaver] be built on top of [BCEL], and
> I would think it likely that we might provide a nice (fluent?) API for
> common code modifications.
>
> Firstly, does anyone object to using [BCEL] as [weaver]'s foundation?;
> secondly, can anyone tell me what (Java 7?) features [BCEL] currently
> lacks?; thirdly, does any of us already have the expertise to add these?
>
> Thanks,
> Matt
>
>
> On Fri, Nov 30, 2012 at 6:35 AM, Emmanuel Bourg <ebourg@apache.org> wrote:
>
> > Le 29/11/2012 19:12, Matt Benson a écrit :
> > > This would go back to the idea of something like a BCEL library
> > > (notwithstanding the fact that the existing privilizer code does not
> use
> > > BCEL).
> >
> > For such a component BCEL would be an implementation detail, so I don't
> > think it should be a sub part of BCEL.
> >
> > If an annotation equivalent to @SwingInvokeLater can be added to the
> > project I would be highly interested in using it.
> >
> > As for the name of the component, what about Commons Weaver ?
> >
> > Emmanuel Bourg
> >
> >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message