You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@opennlp.apache.org by "Joern Kottmann (JIRA)" <ji...@apache.org> on 2017/01/03 10:35:58 UTC

[jira] [Assigned] (OPENNLP-675) Absence of logging and usage of System.out

     [ https://issues.apache.org/jira/browse/OPENNLP-675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joern Kottmann reassigned OPENNLP-675:
--------------------------------------

    Assignee: Joern Kottmann

> Absence of logging and usage of System.out
> ------------------------------------------
>
>                 Key: OPENNLP-675
>                 URL: https://issues.apache.org/jira/browse/OPENNLP-675
>             Project: OpenNLP
>          Issue Type: New Feature
>          Components: Sentence Detector, Tokenizer
>            Reporter: Eugene Prystupa
>            Assignee: Joern Kottmann
>             Fix For: 1.7.1
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)