Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Multiple artifact versions can end up on the classpath #420

cemerick opened this Issue Feb 22, 2012 · 5 comments


2 participants

cemerick commented Feb 22, 2012

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).


technomancy commented Feb 22, 2012

Yeah, maybe putting all of Leiningen's own dependencies in :exclusions for all plugin loading would be a good idea.


cemerick commented Feb 23, 2012

I'm not sure that gets us very far. I see what leiningen.repl is doing already, and I think that's going to just be the tip of the iceberg. I have a couple of ideas. :-)


technomancy commented Jun 7, 2012

Thinking of bumping this to post 2.0.0 unless you have plans.


cemerick commented Jun 15, 2012

Yes, bump along. I really want to hear from people washing ashore on this before potentially complicating things for scenarios that aren't actual problems.


technomancy commented Jun 17, 2014

At this point having not seen any actual problems arising from this potential issue I'm comfortable closing it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment