technomancy/leiningen — Issue #420: Multiple artifact versions can end up on the classpath
Author: cemerick
Created: 2012-02-22 17:53:23+00:00
State: open

Most projects won't have this issue, but it's easy to get into trouble if you're hacking around with projects that happen to be used by leiningen itself, or the plugins in your `project.clj`.

It should be straightforward enough to maintain a set of artifacts that have been added to the classpath, and provide suitable warnings (or fail entirely) depending on what further dependencies are added. Such a mechanism should eventually end up in pomegranate, but it seems like experimenting with it should happen at the front lines first (i.e. Leiningen).