Tobias Crawley rightly suggested that Pomegranate's URLClasspath protocol should be factored out into a separate project, so as to provide a common abstraction for interacting with dynamic classloaders. The new project (dynapath @ https://github.com/tobias/dynapath) is already being used by other Clojure projects, and he has a pull request into Pomegranate now that would make the necessary changes there:
https://github.com/cemerick/pomegranate/pull/43 Using dynapath should be a total win; aside from participating in what looks to be the emerging standard for the protocol for this purpose, dynapath's protocol supersets Pomegranate's and dynapath includes a couple of handy utilities that pomegranate does not. I'm sending this message now as an early heads-up to anyone who is using Pomegranate and has already extended its URLClasspath protocol. The change to Pomegranate will be a breaking one, and I'd like to make sure people have sufficient time to look at the proposed changes, potentially suggest alternatives, and otherwise make appropriate plans. FWIW, I plan on merging the pull request "soon", whatever that means. Pipe up if you'll be negatively affected, etc. Cheers, - Chas -- 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