The issue is that the target does depend on this (explicitly), but that dependency is via our custom resolver, which caches its jars in a different directory from ivy. This is unique in the pants ecosystem (I assume): normally the explicit dependency would resolve to the same jar in the same cache that ivy uses, and this wouldn't be an issue in missing dep detection.