Yep. However using a commons-logging.properties file is generally more convenient.
You should check whether there is already a commons-logging.properties file in the classpath (eg inside a jarfile) at a position earlier than the one you created. Note that the file should be at the "top level", eg not nested inside com/acme/... Cheers, Simon On Fri, 2006-03-17 at 20:55 +0100, Dennis Lundberg wrote: > Hi Alex > > Another way to do it is to set a system property when you run your > program. Something like this (but all on one line): > > java -classpath=... > -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.NoOpLog > com.yourcompany.YourClass > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
