Different packages in different versions of the same artifact

Here's a case I don't think we've addressed. I don't know of a mistake like this in GCP libraries but it does happen:

https://stackoverflow.com/questions/24962607/multiple-versions-of-the-same-dependency-in-maven

In this case, there are completely different packages in different versions of the *same* groupID:artifactID

This prevents multiple packages with completely non-overlapping classes from being loaded ito the same VM, no matter how dependencies are resolved.

I could see Apiary coming close to this though.