commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matt Benson <>
Subject Re: [DISCUSS] promotion and release of [weaver] component
Date Wed, 18 Sep 2013 12:45:33 GMT
Hmm... well, the typical usage profile for WeaveProcessor/CleanProcessor
would be that it is invoked by Maven or Ant, so I wouldn't usually (ever?)
expect an active SecurityManager in these contexts.  That leaves custom
stuff, the nature of which I can't really begin to imagine having just
woken up.  ;)  IMO it doesn't really seem like an issue, but if you feel it
could be important you could do a little hacking.  :D


On Tue, Sep 17, 2013 at 10:45 PM, Dave Brosius <> wrote:

> On 09/17/2013 04:40 PM, Matt Benson wrote:
>> I propose that the [weaver] component [1] is ready for release.  I am the
>> primary contributor to the code, but Mark Struberg also worked on the core
>> architecture.  As soon as [weaver] is released I intend to incorporate the
>> privilizer module into Apache BVal, and at least at one point it was
>> planned that it would be similarly used in Apache OpenWebBeans, so
>> hopefully these will reduce its risk of being orphaned.  Does anyone have
>> any concerns before I put the promotion of [weaver] to a proper component
>> to a vote?
>> Thanks,
>> Matt
>> [1]**sandbox/commons-weaver/index.**html<>
> should the class loader creation in WeaveProcessor/CleanProcessor be done
> in a AccessController.doPrivileged block?
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: dev-unsubscribe@commons.**<>
> For additional commands, e-mail:

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