datahelix
datahelix copied to clipboard
migrate away from `System.[out|err]`
Feature Request
Description of Problem:
Common Consensus is to not use the System.err or System.out features to log messages, but to use a logging mechanism of some kind.
When the codebase moves to use a GUI or some other front end, the use of a logger will make it easier to catch the output messages and redirect them.
This will also allow us to have debug log messages which can be turned off via a config file/command line switch.
Potential Solutions:
migrate to use slf4j as a logging abstraction layer and logback or log4j as the logging backend.
Steps to implement:
- [ ] add dependancies to
pom.xmlfiles - [ ] add
logback.xmlorlog4j.xmlconfiguration file - [ ] migrate
System,errcalls tologger.errorcalls - [ ] migrate
System,outcalls tologger.infoorlogger.debugcalls - [ ] add command line switch to alter logging verbosity level
Acceptance Criteria:
- [ ] no uses of
System.outexist in the codebase - [ ] no uses of
System.errexist in the codebase
Whichever product is selected needs to match the license for this product. Log4j is under an Apache license, logback is under a LGPL license.
Log4j may be best as we are already covered by an Apache license.
We also need to check that any selected will work with java 1.8 without restriction or issue