2013/2/21 Phil Hagelberg <p...@hagelb.org> > Unless you want to clear the cache manually every time your dependencies > change, you'd have to make a parallel tree of jars for each version of > Clojure you plan on using. >
Ah yes, I forgot that clojure code may compile differently, depending on the clojure version it is used with. > I think the simplest way to do this would be with a proxying repository > that also cross-compiled jars to new artifacts with added classifiers as > they came through. You'd also need a bit of magic on the Leiningen side > with some middleware in a plugin to add classifiers to every Clojure > dependency. But I have no idea how you would easily tell apart Clojure > jars from Java jars without opening them up to inspect their contents, > which could add a startup time penalty. > I would imagine that as an opt in solution, where either the library writers and/or users specify that the byte cache should be used for a library. Then the middleware would only need to look if there is ~/.cache/bytecache/org/example/lib/0.2/clj-1.4/ and add it to the classpath, if available. -- -- 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 --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
