A simple method is to use the strict ivy conflict manager, which will cause the jar resolution to fail with an error if it detects two artifacts with conflicting versions. This has the advantage of forcing a dev to be aware of (and make a decision about) confliction versions.

the problem i found with this is that the version of zinc that pants uses (and which i think is the latest?) uses scala_2.10 (and thus org.scala-lang.scala-library@2.10), and didn’t seem to respect managed_dependencies. is that a misconfiguration on my end, or an actual issue?