On 9/28/05, Tim Colson (tcolson) <[EMAIL PROTECTED]> wrote:
>
> > It's a big freakin' patch,
> Wow. If it's nearly as big as the comments, it's freakin' huge. ;-)
>
> Good on ya. :-)

thanks.

> > After several very, very long debates with Geir over
> > commons-logging, i have become largely convinced that it is
> > something we should do with hesitation (i.e. let's talk about
> > it for 2.0, but not before).
>
> Yeah, those really were long, they made JR's posts look short by
> comparison. <grin>
>
> RE: 2.0 -- I think that's a good idea.
>
> I'm not all that bright when it comes to cvs/svn branching... would it
> be possible in the AFS infra to branch the svn repo so that this patch
> (and others) could be available in a 2.0 branch for playing around?

actually, i'm hoping this patch will get into 1.5.  despite the scope
of the changes, most apps currently using Velocity probably won't
notice any difference, except perhaps the addition and use of
StandardOutLogSystem and JdkLogSystem.

any developers who have implemented their own LogSystem's will have to
add two simple methods to their implementations if they decide upgrade
to 1.5.  this is likely to be uncommon, very easy to do, and won't
make their library incompatible with earlier Velocity versions. 
VelocityTools falls into this category.

also, any developers who implement their own Uberspect, don't extend
UberspectImpl, and implement UberspectLoggable (read: no one) will
have to implement one new method in the UberspectLoggable interface,
which again, won't make them incompatible with earlier versions of
Velocity.

in other words, the changes are backwards compatible, and the
deprecation path is clearly set.  there's no reason to wait for 2.0
before adding these enhancements.

> Cheers,
> -Timo
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to