commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matt Benson <>
Subject Re: [privilizer] promotion plan
Date Wed, 28 Nov 2012 21:08:58 GMT
Hi Gary,
  Feel free to suggest one or more alternate names, and we can vote on
them!  The intent is to quickly convey that the component "equips your code
to run in a Java security constrained environment," thus "privilizer" or
"that which makes your code privileged."  Since the main use of the
component is to instrument compiled code during the build process (a
possible future enhancement is to support RT enhancement in a custom
classloader), I don't see that it fits into any existing component, but am
open to correction.

Thanks for your interest,

On Wed, Nov 28, 2012 at 2:55 PM, Gary Gregory <>wrote:

> Another aspect to consider is would this new "privalizer" component (not
> crazy about the name ATM) fit in an existing Commons component?
> On Wed, Nov 28, 2012 at 3:44 PM, Matt Benson <> wrote:
>> Hi all,
>>   As long as I've been part of the Commons community I don't know that
>> I've
>> encountered this exact situation:  a committer adds some code to the
>> sandbox that is more or less complete.  I don't know precisely what
>> requirements must be met before we promote [privilizer] to proper. We seem
>> to have interest from one or more members of the PMC as prospective users;
>> this would seem to imply that were I hit by a bus there ought to be
>> someone
>> interested in maintaining the component.  Speaking for BVal I intend to
>> put
>> this component to immediate use there (that's what I wrote it for!).  Mark
>> has mentioned that OWB and perhaps other ASF projects might want to make
>> use of it.  What else do I need to do?
>> Matt
> --
> E-Mail: |
> JUnit in Action, 2nd Ed: <http://goog_1249600977>
> Spring Batch in Action: <>
> Blog:
> Home:
> Tweet!

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