I agree that an immediate 4.0.1 that breaks backwards compatibility days
after a final release is bad. I figured it was only something for
consideration for the Framework 4.1/Cocoon 2.1/etc timeframe.
If the various Logging solutions will be consumed by the JDK standard, you
only get to decide when to break backwards compatibility, not if, since
you'll need to shift from LogKit to JDK 1.4 in Avalon. Since some platforms
will inevitably lag behind (like BSD, AS400) others, making a generic
interface that supports both before then might be useful.
> Thats similar to what I proposed ages ago to Ceki and it is also similar
to
> the proposal in jakarta commons. The problem is that adopting such an
> interface doesn't really gain you anything. It just creates a 6th API that
> you have to learn.
I'm confused. If the Avalon interface Loggable is generic, then I only need
to learn that one and I probably only already know at most one (LogKit,
Log4J, JDK 1.4, etc.) which is the one I want to plug in for consistantcy.
The guy that wrote the generic API needs to know all six but few others
would bother.
-Steve
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
