Re: Leiningen and loading hooks

2010-07-30 Thread MichaƂ Marczyk
On 30 July 2010 14:28, David Cabana wrote: > Just a personal opinion, but I'd urge you not to worry too much about > breaking changes just yet. The future value of doing the right thing > now outweighs the value of backwards compatibility in an application > as young as Lein. This sounds eminentl

Re: Leiningen and loading hooks

2010-07-30 Thread Phil Hagelberg
On Fri, Jul 30, 2010 at 8:03 AM, wrote: > +1, > > auto loading is simple and if performance becomes an issue, an explicit > list of hooks would solve this issue. I would however leave auto loading by > default. We have a couple of hundred jar dependencies so speed for us is > an issue but auto lo

Re: Leiningen and loading hooks

2010-07-30 Thread lprefontaine
I like magic, life is so complicated these days :))) Luc P. Phil Hagelberg wrote .. > On Fri, Jul 30, 2010 at 8:03 AM, wrote: > > +1, > > > > auto loading is simple and if performance becomes an issue, an explicit > > list of hooks would solve this issue. I would however leave auto loading by

Re: Leiningen and loading hooks

2010-07-30 Thread lprefontaine
+1, auto loading is simple and if performance becomes an issue, an explicit list of hooks would solve this issue. I would however leave auto loading by default. We have a couple of hundred jar dependencies so speed for us is an issue but auto loading seems to me a decent default for beginners, bet

Re: Leiningen and loading hooks

2010-07-30 Thread David Cabana
Phil, Just a personal opinion, but I'd urge you not to worry too much about breaking changes just yet. The future value of doing the right thing now outweighs the value of backwards compatibility in an application as young as Lein. To answer your direct question, I would not be affected by a requ

Re: Leiningen and loading hooks

2010-07-29 Thread Heinz N. Gies
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

Leiningen and loading hooks

2010-07-29 Thread Phil Hagelberg
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 f