Re: [DISCUSS] promotion and release of [weaver] component

2013-09-18 Thread Romain Manni-Bucau
yep from my side Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2013/9/18 Matt Benson : > My intention for runtime weaving would be to bootstrap the weave process in > another

Re: [DISCUSS] promotion and release of [weaver] component

2013-09-18 Thread Matt Benson
My intention for runtime weaving would be to bootstrap the weave process in another manner (I don't think cleaning is relevant to run time). The processor module is described as defining the SPI and providing the filesystem-based/build time infrastructure to invoke the service providers. Does that

Re: [DISCUSS] promotion and release of [weaver] component

2013-09-18 Thread Romain Manni-Bucau
+1, not that important for the first release "build" oriented but if we extend the concept to runtimes it should be done but it is not that easy since you need to take care of current context to know if you are in a container or not and if you use right perms. Romain Manni-Bucau Twitter: @rmannibuc

Re: [DISCUSS] promotion and release of [weaver] component

2013-09-18 Thread Matt Benson
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

Re: [DISCUSS] promotion and release of [weaver] component

2013-09-18 Thread Benedikt Ritter
Go for it! Send from my mobile device Am 17.09.2013 um 22:40 schrieb Matt Benson : > 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

Re: [DISCUSS] promotion and release of [weaver] component

2013-09-17 Thread Dave Brosius
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

[DISCUSS] promotion and release of [weaver] component

2013-09-17 Thread Matt Benson
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 planne