yikes. so... uh... yeah. my brain is pretty full these days... umm... what was i saying? yes, i would like to take a vacation... thanks! :)
anyway, though i've clearly been out to lunch in being suprised that 1.5-dev now has a commons-lang dependency, i'll attempt to stand by my opinion that VelocityTools core classes shouldn't be given a new dependency just to test for empty strings. and really, given that i was more accepting of the commons-lang dep in the core because the core project offers two jars (to simplify things for users that want them simplified), i can at least claim consistency in concern about adding dependencies. :) On 9/19/05, Will Glass-Husain <[EMAIL PROTECTED]> wrote: > Hi Nathan, > > (Responding to the JIRA). Yes, Velocity has a commons-lang 2.1 dependency, > as of last week. (was bundled in with the event handler patch). > > You actually commented positively on it (which was encouraging as I am > reluctant to add dependencies without need). > > WILL > > ----- Original Message ----- > From: "Nathan Bubna" <[EMAIL PROTECTED]> > To: "Velocity Developers List" <velocity-dev@jakarta.apache.org> > Sent: Monday, September 12, 2005 6:56 AM > Subject: Re: event handler patch > > > looks great, Will! > > regarding the dependency thing... are we going to continue to > provide both the velocity.jar and velocity-dep.jar with the 1.5 > version? if so, then the addition of commons-lang is not too bad. > people can use the whole commons-lang lib with velocity.jar and we can > extract and ship StringUtils in the velocity-dep.jar. > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
