Related to issue 23770: Backed out change, some warning should be logged
authorAugusto Mauch <augusto.mauch@openbravo.com>
Thu, 30 May 2013 16:56:01 +0200
changeset 20502 1693de72b307
parent 20501 e6e46782e850
child 20503 ada107be4fd6
Related to issue 23770: Backed out change, some warning should be logged

The approach used in this fix (modifying the template so only the jasper error are logged by default) should be improved. Instead of not logging any warning, we should try to reduce the number of warnings logged by fixing them. I.e. lots of warnings are related to the use of deprecated methods, those can be avoided by using the @supresswarnings annotation or by using a not deprecated method.
config/log4j.lcf.template
--- a/config/log4j.lcf.template	Thu May 30 18:06:34 2013 +0530
+++ b/config/log4j.lcf.template	Thu May 30 16:56:01 2013 +0200
@@ -21,7 +21,6 @@
 # Set our global levels
 log4j.category.org=WARN
 log4j.category.org.openbravo=INFO
-log4j.category.net.sf.jasperreports=ERROR
 
 log4j.appender.R=org.apache.log4j.RollingFileAppender
 log4j.appender.R.File=${catalina.base}/logs/openbravo.log