Hi

I think the point with weaver is more that some other apache projects (bval
for instance) needs it for next release.

*Romain Manni-Bucau*
*Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
*Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/>
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
*Github: https://github.com/rmannibucau*



2013/8/13 Benedikt Ritter <brit...@apache.org>

> Hi,
>
> I haven't been working on weaver so I cannot really comment on it's state.
> IMHO it's important that we only promote components to proper that are very
> close to a release.
>
> We have several components in proper that I think have been promoted to
> early.
> Examples are: csv, functor, imaging.
> After the first enthusiasm has ceased they are hanging around in proper
> without being released.
>
> I haven't seen much activity in weaver over the past weeks. How close is it
> to a release? What has to be done to cut an RC?
>
> Benedikt
>
>
> 2013/8/11 Matt Benson <gudnabr...@gmail.com>
>
> > Hi all,
> >   Hopefully you've noticed that I've been working, as time permits, on
> the
> > [weaver] component in the sandbox.  As a reminder, this component (after
> an
> > exhausting bout of on-list consensus building ;) ), is designed as a
> > general-purpose framework for defining bytecode transformations that may
> be
> > applied to a given codebase.  Currently a local filesystem-based
> > implementation is available which backs both a Maven plugin as well as a
> > custom Ant library, or "antlib".  There are two weaver implementations
> > available as of now:
> >
> >  * privilizer, which automates the handling of Java SecurityManager
> > privileges
> >  * normalizer, which merges functionally identical anonymous class
> > definitions
> >
> > I feel that this component is now ready to be promoted to proper and
> > released.  Does anyone have any concerns they feel should be addressed?
> >
> > Thanks,
> > Matt
> >
>
>
>
> --
> http://people.apache.org/~britter/
> http://www.systemoutprintln.de/
> http://twitter.com/BenediktRitter
> http://github.com/britter
>

Reply via email to