The other thing is ensuring our build environment downloads them and bundles them in the appropriate location - gotta go to the maven repo, look up the names, versions, etc. More effort. that's the other reason.
On Thu, Jul 17, 2008 at 12:36 PM, Les Hazlewood <[EMAIL PROTECTED]> wrote: > It is just one of the reasons, albeit minor as you point out. Who doesn't > prefer a smaller download size/time when possible ;) > > > On Thu, Jul 17, 2008 at 12:33 PM, Jeremy Haile <[EMAIL PROTECTED]> wrote: > >> Then why does the download size matter that much? i.e. It doesn't seem >> like it should be a consideration really when talking about this decision, >> since a) it only makes a difference of a few K and b) we already offer a >> smaller download without the dependencies. >> >> I just ask because it keeps being brought up as a reason not to move to >> SLF4J. Doesn't seem important to me. >> >> >> On Jul 17, 2008, at 12:26 PM, Les Hazlewood wrote: >> >> To mitigate the size of the download, you could always distribute a >>>> jsecurity.zip and jsecurity-with-dependencies.zip just like Spring does. >>>> >>> >>> >>> Heh. You must not have used any of our releases the past 3 months. We >>> do >>> this already ;) >>> >> >> >
