It is a pity that I missed the start of THIS party but here I go! Answer inline:
> -----Original Message----- > From: robert burrell donkin [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, January 29, 2002 9:11 PM > > ... > > (perhaps paulo realizes now why i refused to look at his logging material > from avalon.) I still think there is no excuse. To give a practical example, I never hesitate at looking at Jon's code and using it if it suites my needs. And if one day I really post my common logging configuration mechanism, I will give him credit because part of the code id from him. A lot of people here knows about several of my past flames with Jon. I still feel no problem about using his prior art instead of going trough the silly waste of energy that went on here. > hi berin > > from my point of view, avalon didn't influence the design any more than > log4j. please search the list archives if you don't believe me. (i've > taken a *lot* of flak about being unwilling to learning from avalon.) IMO you are wrong I gave several suggestions which were accepted and those suggestions were completely based on what I learned from Avalon's code. The commons used Avalon know how trough me. > i've been waiting since the commons was started for a solution to our > logging problem. every particular logging system that was proposed was > vetoed (including avalon). commons-logging is unfortunately the only > choice remaining on the table. it's either this or not having a solution > at all, > > i personally couldn't care less about who gets attributed with what. if > that's all that's bothering you, please submit a patch. > > on the other hand, if you think that we should be using > whatever-bit-of-code-in-avalon then that's a different issue. please > submit a alternative proposal so that we can vote on it. The current interface is practically a copy of Avalon's. > all i want is to have a solution to the logging problem. > > - robert As I already _insisted_ before, the solution was there for a long time. Have fun, Paulo Gaspar -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
