[OODT-693] Consolidate logging in OODT

• Type: Improvement
• Status: Reopened
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 0.6
• Fix Version/s: 1.1, 2.0
• Component/s: file manager
• Skill Level: Newcomer (Easy) - Everyone can do this
• Assignee: Imesha Sudasingha
• Reporter: Lewis John McGibbney
• Created: 14/May/14 18:16
• Updated: 23/Sep/19 21:17

Description

Right now we seem to be using an array of inconsistent logging frameworks.
Personally I really like the Slf4j over Log4j setup. Extremely easy to work with, easy to configure and Log4j 2.X is dynamite so if we can implement that then we are laughing.
This is by no means a trivial task.
It is however an important one.

Issue Links

• is blocked by: OODT-980 Update File Manager to use SLF4J logging
• is blocked by: OODT-981 Update Workflow Manager to use SLF4J logging
• is blocked by: OODT-982 Update Crawler to use SLF4J logging
• is blocked by: OODT-984 Update PGE to use SLF4J logging API
• is blocked by: OODT-987 Update Configuration Management to use Log4J2 over Log4J
• links to: GitHub Pull Request #66
• links to: GitHub Pull Request #66
• mentioned in: Page Loading...

Sub-Tasks

• Update File Manager to use SLF4J logging: Resolved
• Update Workflow Manager to use SLF4J logging: Resolved
• Update Crawler to use SLF4J logging: Resolved
• Update Resource Manager to use SLF4J logging: Open
• Update PGE to use SLF4J logging API: Resolved
• Update Configuration Management to use Log4J2 over Log4J: Resolved