The "correct" way to deal with this is for users of your libraries to exclude those dependencies if they don't want them. Both Leiningen and Maven support exclusion of transitive dependencies.
But given the reorganization of contrib, compatibility between 1.3 and 1.2 is difficult to achieve. Maintaining 2 branches of your library may be the only solution for now. Also, going forward, you should not have dependencies on contrib/ standalone but on just the individual modules you need. -S On Nov 4, 2:44 am, Saul Hazledine <shaz...@gmail.com> wrote: > Hello, > I've put some small libraries on github. At the moment they > specifically depend on Clojure 1.2 and contrib (since its the released > version). However, I have had requests to take out the dependencies on > clojure and contrib so that they don't infect projects that use them. > Is this standard practice? Would it catch people out? > > I thought about alternative approaches but have no solution. For > instance, in Leiningen, it is possible to specify a minimal version > e.g > [org.clojure/clojure-contrib "[1.2,)"] > > This would normally be fine but in 1.3 the dependency on contrib > changes: > > [org.clojure.contrib/standalone "1.3.0-alpha2"] > > Has anyone hit this problem? What is the best way of dealing with it? > > Thanks in advance for any help. > Saul -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
