details: https://code.openbravo.com/erp/devel/pi/rev/1693de72b307
changeset: 20502:1693de72b307
user: Augusto Mauch <augusto.mauch <at> openbravo.com>
date: Thu May 30 16:56:01 2013 +0200
summary: 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.
diffstat:
config/log4j.lcf.template | 1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diffs (11 lines):
diff -r e6e46782e850 -r 1693de72b307 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
------------------------------------------------------------------------------
Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
Get 100% visibility into your production application - at no cost.
Code-level diagnostics for performance bottlenecks with <2% overhead
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap1
_______________________________________________
Openbravo-commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openbravo-commits
