I changed the privilizer weaver to blow up with an Exception if an access level is set and a @Privileged method which has a wider accesslevel got detected.
Imo this is a clear user error if one defines a public @Privileged method and explicitly only wants them being private. Imo this is the only way to go as a user usually doesn't see/check what bytecode really got generated for him. Any objections? LieGrue, strub --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
