Herwig Hochleitner writes: >> I understand not delivering AOT libs through maven not knowing the target >> environment but having a tuning tool to speed up loading by avoiding > compilation >> would help with all the tooling starting to appear. > > How about a lein-bytecache plugin, that can AOT compile and manage the > .class files of released jars in the ~/.cache directory. > When that's up and running, leiningen could make use of it for the > leiningen jar itself.
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. 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. Anyway, it can certainly be done. I suspect you'd get more bang for your buck by just compiling it once and not doing a clean, but protocols kind of throw a wrench in that plan when it comes to AOT. -Phil -- -- 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.
