multi-versioned Jars are being implemented which potentially will contain multiple classes or interfaces with the FullyQualifiedName but implemented differently, all existing under different paths within an archive.

Pack200 does not treat these paths differently, as it was designed to treat the whole jar as an
archive containing unique classes.

The gory details are documented in JDK-7131266, a test case is attached which exhibits the problem.

There are several ways to handle this:
1. treat each version within a jar-file as a segment and concatenate them.
2. move any duplicates to its own segment (needs to be done carefully).