Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||
| ID | |||||||||||
| 0006047 | |||||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||||
| feature request | [Openbravo ERP] A. Platform | minor | have not tried | 2008-11-19 11:55 | 2009-05-22 19:34 | ||||||
| Reporter | plujan | View Status | public | ||||||||
| Assigned To | iciordia | ||||||||||
| Priority | normal | Resolution | open | Fixed in Version | |||||||
| Status | acknowledged | Fix in branch | Fixed in SCM revision | ||||||||
| Projection | none | ETA | none | Target Version | |||||||
| OS | Any | Database | Any | Java version | |||||||
| OS Version | Database version | Ant version | |||||||||
| Product Version | pi | SCM revision | |||||||||
| Merge Request Status | |||||||||||
| Review Assigned To | |||||||||||
| OBNetwork customer | No | ||||||||||
| 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. | ||||||||||
| Tags | ReleaseCandidate | ||||||||||
| Attached Files | |||||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
|
 Relationships |
|
Notes |
|
|
(0010396) shuehner (administrator) 2008-11-19 12:16 |
You should already be able to specify the level yourself in the log4j.lcf (log4j config-file). We could just use this functionality and document it) |
|
(0010397) pjuvara (viewer) 2008-11-19 12:21 |
To the previous note: it would be good to have a central point of configuration in openbravo.properties |
|
Notes |
|
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 | OBNetwork customer | => No |
| 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 |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |