Ceki,
> Remy Maucherat said,
> > At this point, the only productive thing that could happen
> > is if log4j adopted the java.util.logging API as the
> > logging API for log4j.next.
> It doesn't make any sense for log4j.next to adopt
> java.util.logging API.
Why not? Provide specifics. If we are going to go ahead with changes to
JCL to facilitate a next generation standard, let's include discussion of
all options.
> it should be clear to any moderately astute observer
> that bundling an API with the JDK is not enough to
> create a standard.
Well, actually, I think that bundling with the JDK pretty much does define a
standard, since it would be available everywhere. Perhaps not THE standard,
if there were widespread adoption of alternatives.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
