> > They’re not the same class and that’s the problem. It’s similar to loading > two versions of the same library in OSGi
Let's say you are dealing with org.vafer.Foo the library relocates this as org.apache.commons.compress.internal.org.vafer.Foo The library only deals with org.apache.commons.compress.internal.org.vafer.Foo They cannot get mixed up. Please explain how this will cause problems.