Proguard: avoiding naming collisions with pre-obfuscated library JARs

Question

It seems that Proguard doesn\'t make any attempt to avoid naming collisions with classes in library JARs when it renames/repackages classes. Is this correct, or have I just

Answer 1

From the progaurd manual,

If an input jar and a library jar contain classes in the same package, the obfuscated output jar may contain class names that overlap with class names in the library jar. This is most likely if the library jar has been obfuscated before, as it will then probably contain classes named 'a', 'b', etc. Packages should therefore never be split across input jars and library jars.

So it looks like using your own package is the recommended answer.

Answer 2

In closed libraries to prevent conflict between multiple obfuscated modules/libraries you should use

-keeppackagenames

proguard rule to prevent complete classes repackaging, otherwise you can find errors like:

Duplicate class a.a.a.a in [jetified-lib1] and a.a.a.a in [jetified-lib2]