SecurityException in environments with signed jars

_From [Sebastian.Zarnekow](https://code.google.com/u/107199171929119944056/) on July 07, 2009 04:26:57_

A SecurityException is raised when a dynamic class is created in a package,
that contains signed classes.

To overcome this, we have to patch Guice and substitute the
net.sf.cglib.core.NamingPolicy and prefix the package of the generated
classes with a $ the same way, as it is done for classes from java.* packages.

It would be very nice, if either the naming policy were customizable or the
NamingPolicy would somehow validate the "base class" and choose another
package on its own, if the class is signed.

This behaviour was observed with Guice 1.0.

_Original issue: http://code.google.com/p/google-guice/issues/detail?id=401_