Openbravo Issue Tracking System - Openbravo ERP |
View Issue Details |
|
ID | Project | Category | View Status | Date Submitted | Last Update |
0006047 | Openbravo ERP | A. Platform | public | 2008-11-19 11:55 | 2009-05-22 19:34 |
|
Reporter | plujan | |
Assigned To | iciordia | |
Priority | normal | Severity | minor | Reproducibility | have not tried |
Status | acknowledged | Resolution | open | |
Platform | | OS | 5 | OS Version | |
Product Version | pi | |
Target Version | | Fixed in Version | | |
Merge Request Status | |
Review Assigned To | |
OBNetwork customer | |
Web browser | |
Modules | Core |
Support ticket | |
Regression level | |
Regression date | |
Regression introduced in release | |
Regression introduced by commit | |
Triggers an Emergency Pack | No |
|
Summary | 0006047: The compile output level should be specified on Openbravo.properties file |
Description | When compiling, current compiling level is set to INFO, so a huge amount of data is displayed. But it would be nice to have an option for cutting this output to show only desired level:
* ERROR, WARN and INFO
* ERROR and WARN
* Only ERROR
This is a basic logging functionality. Log4j has this levels built in, so adding the feature to Openbravo ERP should be easy. |
Steps To Reproduce | |
Proposed Solution | |
Additional Information | |
Tags | ReleaseCandidate |
Relationships | |
Attached Files | |
|
Issue History |
Date Modified | Username | Field | Change |
2008-11-19 11:55 | plujan | New Issue | |
2008-11-19 11:55 | plujan | Assigned To | => pjuvara |
2008-11-19 11:55 | plujan | sf_bug_id | 0 => 2314568 |
2008-11-19 11:55 | plujan | Regression testing | => No |
2008-11-19 12:16 | shuehner | Note Added: 0010396 | |
2008-11-19 12:19 | pjuvara | Tag Attached: ReleaseCandidate | |
2008-11-19 12:19 | pjuvara | Status | new => acknowledged |
2008-11-19 12:20 | pjuvara | Category | Z. Others => A. Platform |
2008-11-19 12:21 | pjuvara | Note Added: 0010397 | |
2009-05-22 19:34 | pjuvara | Assigned To | pjuvara => iciordia |