[OPENNLP-675] Absence of logging and usage of System.out

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.7.1
• Component/s: Sentence Detector, Tokenizer
• Assignee: Jörn Kottmann
• Reporter: Eugene Prystupa
• Created: 20/Apr/14 00:25
• Updated: 20/Jan/23 07:30
• Resolved: 19/Jan/17 16:18

Description

There seems to be no concept of logging used by the libraries. Instead System.out.println is hard-coded in many places where debug information using a logging framework would do it.
This makes awkward to use the modules integrated into a different application (as it spams our logs or console).

Is the usage of System.out in core classes (like GISTrainer) by choice? Or is it simply a technical debt? I am happy to work on it and provide a patch if this is a technical debt.

Issue Links

• relates to: OPENNLP-1447 Move from System.out/System.err to SLF4J
• links to: GitHub Pull Request #5
• links to: GitHub Pull Request #71
• mentioned in: Page Loading...