On Jul 30, 2010, at 6:07 , Phil Hagelberg wrote: > I discovered a problem in Leiningen 1.2.0 that I am debating how to > fix in 1.2.1. The gist is that it searches the whole classpath for all > namespaces matching leiningen.hooks.*, and this is very slow for large > classpaths. It can add several seconds to the Leiningen boot time. > > I'm contemplating a fix to this that would require hooks to be > declared in project.clj in order for them to be loaded. This is a good > idea for reasons other than just boot time, but it is a breaking > change. > > I'd like to gauge how many people would be affected by such a change. > Auto-loading hooks is a pretty new feature, so if I can fix the > performance issues with it before its use is widespread that might be > nice. But if a lot of people are relying on implicit loading, then I > will be more cautious. > > Please let me know. My suggestion would be make a project.clj tag like :hook-cps which holds all classpathes checked for hooks and one :implict-hooks true that would turn back old behavior - that said I'm not 'hurt' by any chance since I've no project that uses them :P
Regards, Heinz -- 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
