Exclusions & configuration

Not everything can be safely renamed or translated. RJNI ships built-in exclusion profiles for the common cases that would otherwise break at runtime, plus config-driven controls you set yourself.

1. Reflection by nameClass.forName-style lookups by literal string.
2. ServiceLoaderProvider-lookup classes matched by service-file convention.
3. JPMS module descriptorsmodule-info classes.
4. Spring proxyingYour own bean classes stay eligible; Spring's own proxy internals don't.
5. Proxy-library internalsCGLIB, ByteBuddy, Javassist, Hibernate's bytecode provider.
6. Config-driven keep rules ConditionalYour own class-level exclusion patterns.
7. Trial / evaluation mode ImplementedProtect a deterministic subset before licensing the full build.
8. Configuration referenceEvery CLI flag, in one place.