That's *exactly* what I am trying to change here and now. I think when Rod started this, he was as unaware of Avalon as Avalon's community was of him.
That is the past. This is the present, and I WANT Avalon and commons to work in harmony, not dischord. Scott > -----Original Message----- > From: Berin Loritsch [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, January 29, 2002 1:17 PM > To: Jakarta Commons Developers List > Cc: Morgan Delagrange > Subject: Re: [Logging] [VOTE] Commons Logging 1.0 Release > > > Remy Maucherat wrote: > > >>So that clinches it. The _initial_ HttpClient abstraction was > >>definitely not informed by Avalon. In fact, we had already > packaged > >>Logging as a separate component by then. (Hey, I guess I wrote the > >>proposal. I should add myself as a contributor!) > >> > >>Maybe the Avalon abstraction should have a credit to HttpClient. ;) > >> > > > > +1 ;-) > > Although, seeing all this, I'm not sure I want to be > involved in any > > way with Avalon ;-) > > > However, if you guys tried to work with us from the outset, > much of this confusion would never have risen. > > > > > > -- > > "They that give up essential liberty to obtain a little > temporary safety > deserve neither liberty nor safety." > - Benjamin Franklin > > > -- > To unsubscribe, e-mail: > <mailto:commons-dev-> [EMAIL PROTECTED]> > For > additional commands, > e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
