obfuscation and naming conflicts

On Thursday May 21 2009, Paul Phillips wrote:
> Trying to do some profiling on scalac, I find I can no longer use my
> yourkit profiling code, because:
>
> package yourkit contains object and package with same name: d
> one of them needs to be removed from classpath
>
> Sure enough yjp.jar is obfuscated, everything is crammed down to one
> letter, and com.yourkit has a package called d and a class called d.
> If we can come up with a less fatal resolution that'd be good; I'm
> sure this won't be the last obfuscated jar.

Perhaps one of those obfuscation tools could be used to uniformly rename
packages and / or classes in an already obfuscated application so as to
side-step this problem?

Randall Schulz