Hi Ceki,
On 23.04.2010, at 16:18, Ceki Gülcü <[email protected]> wrote:
On 23/04/2010 2:14 PM, Joern Huxhorn wrote:
Didn't you change LocationAwareLogger and doesn't that mean that
it's not compatible with the current Logback anymore?
Or is this only relevant for wrappers like jcl-over-slf4j and you
changed all of them already?
Right, LocationAwareLogger affects compatibility with logback but so
does MessageFormatter changes, actually the latter in a deeper way as
it is no longer possible to compute the formatted message lazily in
LoggingEvent. I must be computed eagerly in LoggingEvent's
constructor.
Are you aware that my ParameterizedMessage supports both #70 and lazy
initialization?
This is possible since the placeholders are only counted during
creation. The actual formatting/placeholder replacement is only
performed when the formatted message is requested. The formatted
message is kept so it won't be regenerated in case of further calls.
It could also be enhanced to perform the toString of the arguments at
a later time. The Message interface could be extended by an
prepareForDeferredProcessing() method for that purpose.
I agree with Ralph that this would be a good time to extend the Logger
interface with Message-aware methods since 1.6 will be incompatible
anyway.
This wouldn't mean that varargs need to be added at this point.
A new release of logback compatible with 1.6.0-RC0 will follow
shortly.
I didn't have the time, yet, to check this myself. Please give me a
short notice.
No pressure here.
I could likely check this on our project some time next week.
OK.
Cheers,
Joern.
On 22.04.2010, at 20:21, Ceki Gülcü wrote:
Sure. I'd appreciate if you could give 1.6.0-RC0 a try.
On 22/04/2010 2:17 PM, Joern Huxhorn wrote:
Thanks for implementing the fix for ticket 70!
Cheers,
Joern.
On 21.04.2010, at 22:59, Ceki Gülcü wrote:
Hello all,
I am happy to announce the immediate availability of SLF4J version
1.6.0-RC0, which is still experimental, consisting of several
important enhancements and bug fixes.
As of 1.6.0-RC0, in the absence of an SLF4J binding, slf4j-api
will
default to a no-operation implementation discarding all log
requests. Thus, instead of throwing an exception, SLF4J will
emit a
single warning message about the absence of a binding and
proceed to
discard all log requests without further protest.
Please refer to the the news page for precise details.
http://www.slf4j.org/news.html
You can download SLF4J, including full source code, class files
and
documentation on our download page, shown below.
http://www.slf4j.org/download.html
You can receive SLF4J related announcements by subscribing to the
SLF4J announce mailing list. To subscribe to QOS.ch announce list,
please visit the following URL.
http://qos.ch/mailman/listinfo/announce
--
Ceki Gülcü
Logback: The reliable, fast and flexible logging framework for
Java.
http://logback.qos.ch
_______________________________________________
slf4j-dev mailing list
[email protected]
http://qos.ch/mailman/listinfo/slf4j-dev
_______________________________________________
slf4j-dev mailing list
[email protected]
http://qos.ch/mailman/listinfo/slf4j-dev
_______________________________________________
slf4j-dev mailing list
[email protected]
http://qos.ch/mailman/listinfo/slf4j-dev
_______________________________________________
slf4j-dev mailing list
[email protected]
http://qos.ch/mailman/listinfo/slf4j-dev
_______________________________________________
slf4j-dev mailing list
[email protected]
http://qos.ch/mailman/listinfo/slf4j-dev
_______________________________________________
slf4j-dev mailing list
[email protected]
http://qos.ch/mailman/listinfo/slf4j-dev
