> As the getLogger() method is probably the only one in LoggerManager that > people are commonly using, we could leave a LoggerManager skelett that > consists only of this single method. The left over method would call > the preferred Logger::getLogger() and additionally prints a deprecation > warning. > This way old code would run but would tell itself how to fix it. > This seems more user friendly that just let them search for a > README file.
I can understand your point, but I think this is not necessary. If we would leave such a skelett in it, we would carry it around for a loooong time. I don't think this is necessary with the 2.0 release. If we would upgrade from 2.0 to 2.1, that would be another thing. Other problems: people are forced to change code, cause they do need to include the Logger class for classloading. This ahs been done by LoggerManager before. I think it will not work to have two classloaders in place nor do I think it would be good to have an include statement in the LoggerManager class But that is only my 2 cents - if there are other opinions around, speak up :-) best, Christian
