moving the interceptor to jboss-invocation, removing the dependency
POM updates
Prep 1.0.0.Beta3
Next is 1.0.0.Beta4
Calling Subject.getSubject includes a permissions check, this in itself encourages the call to be in a PrivilegedAction.

Unfortunately the call to AccessController.getCurrent() requires the opposite to prevent the AccessControlContext from being replaced.

Combining these two calls into a single utility method encourages a situation where the Subject is easily hidden or a case where wide access to the getSubject method needs to be granted so that the method will work cleanly.

Overall a utility method should make a developers life easier, in this case I believe the method is doing the opposite.
Move actions to the action package
Prep 1.0.0.Final
Next is 1.1.0.Beta1
Enable checked mode by default
Add service descriptor for security manager class
SecurityManager must have public constructor for service loading to work
Avoid JDK bug where the exact call stack depth is relied upon for member access, and fix special Atomic*FieldUpdater cases
Slightly more strict checking
Fix member access checking
Add helper support for custom permission types with action sets
Enhance error reporting for access control exceptions
Enhancements to support int and long action set fields in a permission
Fix some spelling mistakes
Replace illicit usage of RuntimePermission with new WildFlySecurityManagerPermission
Remove defunct SubjectUtils class