Thanks Dennis for your response. Do you have any other ideas how to disable it because I created commons-logging.properties file with org.apache.commons.logging.Log=org.apache.commons.logging.impl.NoOpLog Added it in my classpath and my program still sends logging info to the console.
Thanks Alex -----Original Message----- From: Dennis Lundberg [mailto:[EMAIL PROTECTED] Sent: Thursday, March 16, 2006 2:04 AM To: Jakarta Commons Users List Subject: Re: common-logging disabling logging Hello In order to disable logging completely you can put a file called commons-logging.properties in your class path with the following contents: org.apache.commons.logging.Log=org.apache.commons.logging.impl.NoOpLog -- Dennis Lundberg Alex wrote: > I installed commons http-client and had to add commons-logging b/c it > requires it. I read the docs on 'logging' which either I don't understand > well or docs don't really explain how to setup logging, find out which > logging it's using. If I need to do it in main method or whatever For now > all I really need is to find out how to disable all those "INFO and warnings > logging. If some1 has an example or know how to do it feel free to let me > know. > > Thanks > > -----Original Message----- > From: Remko Popma [mailto:[EMAIL PROTECTED] > Sent: Wednesday, March 15, 2006 9:01 PM > To: [email protected] > Subject: [logging] log4j TRACE support justifies minor release > > I hope this is the correct mailing list, apologies if dev would have been > better. > > Support for TRACE-level logging has been available for about eight months > now (log4j 1.2.12 was released in August 2005). > As you are probably aware, the current commons.logging release (1.0.4) > outputs Log.trace() calls at DEBUG level, even if the underlying log4j > version supports the TRACE level. > > I understand that this will be fixed in the upcoming JCL 1.1 release, but > this release will also include many other features and fixes, and the > Release Plan wiki page > (http://wiki.apache.org/jakarta-commons/Logging/1.1.0ReleasePlan) > does not have a release date and shows the status as "Preparations for > Alpha 1". > This sounds like a release is still a long time (several months) away. > > I also saw that plans for a 1.0.5 release (with support for log4j TRACE > level logging) were cancelled because developers wanted to include so many > new features that a 1.1 release was justified. > > I think it is great that developers are so enthusiastic and have many > ideas about how to improve JCL. For servlet-related work, the JCL 1.1 > release is probably a great step forward. However, there must be many > developers working on both servlet and non-servlet projects who would > *really* like to have proper TRACE support in commons.logging soon, and > who don't like to wait for the JCL 1.1 release. > Please don't become like log4j 1.3, which has a zillion great features and > will be released Real Soon Now... > > I believe that TRACE support alone would justify a minor release. > Would it be a lot of work to release a new version of commons.logging > (1.0.5) with *only* the TRACE issue fixed, and no other changes? > > Respectfully, > --Remko Popma > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
