Re: Log4j 1.3 Woes

[Jess Holle]

Jess Holle wrote: Also give that most legacy libraries won't be recompiled against a hypothetical 1.2.13 real soon, there is still something to be said for either: Reintroducing Category and Priority Sure their existence is ugly but how much did they *really* hurt anyone? It would seem that by making the constructors for Category and Priority package scoped one could prevent all but the most stupid usages from ever constructing non-Logger / non-Level instances of these classes. That would APIs that used these classes is 1.2 to continue doing so while allowing 1.3 APIs to assume Logger and Level.  New sibling APIs could be introduced that use Logger and Level for existing APIs so that casting can be avoided except for legacy callers. For that matter almost all implementation could be at the Category and Priority level as Logger and Level are just preferred names... What is breaking so much source code and many existing binaries really buying? -- Jess Holle