At 09:48 PM 2/25/2005, Curt Arnold wrote:
I can't stress how strongly that I believe these changes are bad and will unnecessarily cause some users of 1.2 to stay with log4j 1.2 or encounter broken behavior during the migration. I was disappointed that such significant changes were initially committed (back on the 18th) without any prior discussion or announcement. If I missed it, I apologize.
I understand. OK, to summarize:
1) The changes are compile-time backward compatible -- existing appenders will compile just fine without change against 1.2 as well as 1.3.
2) The changes only affect programmatic calls to appenders maintained outside the log4j project. If those appenders are invoked from log4j configuration files, then they will work just fine and without change with 1.2 as well as 1.3.
3) Applications such as hivemind which configure their custom appenders programmatically need to add one line to their code in order to invoke the activateOptions() method. If they do that, they will be compatible with both 1.2 and 1.3.
I've tried to explain to you the reasons for these changes over the phone. Apparently, I was not very successful. :-)
I think it is inappropriate to attempt to preemptively suppress a discussion. I think that I raised legitimate technical issues that should been discussed much earlier. I know that we disagree, I'd like to see what the rest of the list thinks.
You have raised a perfectly legitimate technical issue. I also happen to think that it does not deserve the effort wasted discussing it. However, you certainly have the right to raise the issue. If you'd like ask for a vote on the subject, you do not need my permission to do so. It is your right as a committer.
I'd just like to move forward with code that we can maintain on the long term.
-- Ceki Gülcü
The complete log4j manual: http://www.qos.ch/log4j/
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
