Re: [slf4j-user] [POLL] Requiring JDK 1.5 for SLF4J
yes Ceki Gulcu wrote: Do you accept SLF4J dropping JDK 1.3 compatibility and require JDK 1.5 instead? ___ user mailing list user@slf4j.org http://www.slf4j.org/mailman/listinfo/user
Re: [slf4j-user] Java 5 version of SLF4J?
Hi Simon, You should never confuse Java byte code with compiled byte code. I understand there are a few superfluous byte codes, but in the end the JVM determines how to compile it to CPU instructions. Unfortunately I am not aware of what the JVM actually does with unused values. Does it do escape analysis already? Regards, Erik. Simon Kitching schreef: Erik van Oosten schrieb: Christopher, As I wrote already on Feb 17: There is another aproach, as taken by http://code.google.com/p/log5j/. It is a wrapper around log4j. I wish they had made it for SLF4J! I am still waiting for someone to this for SLF4J. It should not be hard. I did not yet find the time myself :( Sigh. Broken broken broken. Re the feature for determining which category to create a logger for, see the documentation for Exception.getStackTrace. There is no guarantee that valid info about the callstack is available. So this code will work fine under unit testing, then may start emitting messages to the wrong categories when run in a high-performance environment. That will be fun to debug... Re the printf-style formatting: log.debug(format str, arg0, arg1, arg2); is exactly equivalent to: push format str onto stack tmp = new Object[3]; tmp[0] = arg0; tmp[1] = arg1; tmp[2] = arg2; push tmp onto stack invoke log.debug (and of course garbage-collect the tmp object later..) So in practice, for good performance you need if (log.isDebugEnabled()) around each call anyway. In which case, the printf-style stuff gives no performance benefits at all; if something is going to be logged then the formatting is nowhere near the bottleneck step. The SLF4J fake-varargs approach, where the api allows 0,1 or 2 params is slightly better, as it avoids the new Object[] call. But for best performance, isDebugEnabled should be used anyway. Regards, Simon ___ user mailing list user@slf4j.org http://www.slf4j.org/mailman/listinfo/user -- -- Erik van Oosten http://day-to-day-stuff.blogspot.com/ ___ user mailing list user@slf4j.org http://www.slf4j.org/mailman/listinfo/user
Re: [slf4j-user] Java 5 version of SLF4J?
Christopher, As I wrote already on Feb 17: There is another aproach, as taken by http://code.google.com/p/log5j/. It is a wrapper around log4j. I wish they had made it for SLF4J! I am still waiting for someone to this for SLF4J. It should not be hard. I did not yet find the time myself :( Regards, Erik. [EMAIL PROTECTED] wrote: Ceki, I do understand your reasoning, and thank you for your quick response. -- Erik van Oosten http://day-to-day-stuff.blogspot.com/ ___ user mailing list user@slf4j.org http://www.slf4j.org/mailman/listinfo/user
Re: [slf4j-user] [ANN] JCL to Slf4j migration in a Maven environment
Hello slf4j-ers, I took no-commons-logging to the next level and called it Version 99 Does Not Exist. http://day-to-day-stuff.blogspot.com/2007/10/announcement-version-99-does-not-exist.html Have fun! Erik. -- Erik van Oosten http://2008.rubyenrails.nl/ http://day-to-day-stuff.blogspot.com/ ___ user mailing list user@slf4j.org http://www.slf4j.org/mailman/listinfo/user
Re: [slf4j-user] [ANN] JCL to Slf4j migration in a Maven environment
Hi Ceki, Hopefully it will not be necessary in 5 years :) But, yes I want to keep it around for at least 5 years. I host it at home together with another site which needs to be up for at least 5 years. The hostname is a free DNS service from http://www.no-ip.com/, which proved to be very reliable in the past. My uplink is no so wide, but within a couple of months it will go to 10Mbit/s. Only when the repository becomes so popular that the other site is starving for bandwidth I will have to shut it down (or find another hosting party). If you want absolute certainty, you can now also download the complete repository from http://no-commons-logging.zapto.org/. Regards, Erik. Ceki Gulcu-2 wrote: Hi Erik, Thank you for sharing this nifty hack. Do you think the no-commons-logging repository at http://no-commons-logging.zapto.org/mvn2/ can stand the test of time? How likely it is to still be there in 5 years? Cheers, -- Ceki Gülcü -- View this message in context: http://www.nabble.com/-ANN--JCL-to-Slf4j-migration-in-a-Maven-environment-tf4109103.html#a11705974 Sent from the Slf4J - user mailing list archive at Nabble.com. ___ user mailing list user@slf4j.org http://www.slf4j.org/mailman/listinfo/user
[slf4j-user] [ANN] JCL to Slf4j migration in a Maven environment
Hi, I wrote my own version of a commons-logging release to fool Maven and completely exclude JCL from my application. Read about the why and how on my blog: http://day-to-day-stuff.blogspot.com/2007/07/no-more-commons-logging.html Regards, Erik. -- Erik van Oosten http://2008.rubyenrails.nl/ http://www.day-to-day-stuff.blogspot.com/ -- View this message in context: http://www.nabble.com/-ANN--JCL-to-Slf4j-migration-in-a-Maven-environment-tf4109103.html#a11685030 Sent from the Slf4J - user mailing list archive at Nabble.com. ___ user mailing list user@slf4j.org http://www.slf4j.org/mailman/listinfo/user
