Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
0011683Openbravo ERPA. Platformpublic2009-12-08 14:362009-12-11 00:00
mtaal 
mtaal 
normalminorhave not tried
closedfixed 
5
pi 
pi 
Core
No
0011683: JUnit tests should not use log4j.properties but log4j.lcf
The src-test folder has its own log4j.properties file. This overwrites the log4j.properties file in the src folder. This last log4j.properties file is used by the new build window.

The junit test classes should make use of the log4j.lcf file in the src folder.

This change is maybe temporarily as the log4j properties file structure is under review.

No tags attached.
Issue History
2009-12-08 14:36mtaalNew Issue
2009-12-08 14:36mtaalAssigned To => mtaal
2009-12-08 16:46hgbotCheckin
2009-12-08 16:46hgbotNote Added: 0022549
2009-12-08 16:46hgbotStatusnew => resolved
2009-12-08 16:46hgbotResolutionopen => fixed
2009-12-08 16:46hgbotFixed in SCM revision => http://code.openbravo.com/erp/devel/pi/rev/9afb05bdcfaecd5f64edbe3ab488a0c0bd1647c6 [^]
2009-12-10 12:47shuehnerNote Added: 0022631
2009-12-10 12:47shuehnerStatusresolved => closed
2009-12-11 00:00anonymoussf_bug_id0 => 2912325

Notes
(0022549)
hgbot   
2009-12-08 16:46   
Repository: erp/devel/pi
Changeset: 9afb05bdcfaecd5f64edbe3ab488a0c0bd1647c6
Author: Martin Taal <martin.taal <at> openbravo.com>
Date: Tue Dec 08 16:46:14 2009 +0100
URL: http://code.openbravo.com/erp/devel/pi/rev/9afb05bdcfaecd5f64edbe3ab488a0c0bd1647c6 [^]

fixes issue 11683: JUnit tests should not use log4j.properties but log4j.lcf

---
R src-test/log4j.properties
---
(0022631)
shuehner   
2009-12-10 12:47   
run.all.tests runs fine with the removed log4j.properties without any warnings about non-initialized log4j.