| Version 2 (modified by pap, 17 years ago) (diff) |
|---|
Analysis
(The purpose of the analysis is to give as much as possible of the needed information for designing and implementing the task.)
Overview
The logging should be revised especially the configuration should be fixed. A tutorial should be migrated from the old wiki. More attention should be paid on testing and runtime logging.
Task requirements
- Migrate and review the logging tutorial from the old wiki.
- Review logging format output.
- Find a way to make all modules use a single logging hierarchy.
- Configure logging so that log files are always at the same place no matter whether we run tests, the project from eclipse or the project as a standalone application. (may be left for the next revision if this runs out of time)
Task result
The result of this task is a wiki page, configuration file(s) and source code.
Implementation idea
- You can look at Pax Logging (http://wiki.ops4j.org/confluence/display/ops4j/Pax+Logging). I suppose it can be helpful as it is OSGI-ed version of log4j.
- Look the format of appenders of lo4j.properties file and think whether it's good enough
- Try putting log4j config in the resources of the application.
Related
http://asteasolutions.net/mediawiki/index.php/Veda-Design-R2#Logging
How to demo
- Start Sophie 2.0 and show where and how it logs.
Design
Implementation
(Implementation results should be described and linked here (from the wiki or the repository)
Testing
Comments
Log
