[
https://issues.apache.org/jira/browse/OPENNLP-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15826494#comment-15826494
]
ASF GitHub Bot commented on OPENNLP-675:
----------------------------------------
GitHub user kottmann opened a pull request:
https://github.com/apache/opennlp/pull/71
OPENNLP-675 Use verbose param to control printing to stdout
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kottmann/opennlp OPENNLP-675
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/opennlp/pull/71.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #71
----
commit 98b2d5e12d9b671c26d8ad9dc6fc3d5dc3798470
Author: Jörn Kottmann <[email protected]>
Date: 2017-01-17T17:53:37Z
OPENNLP-675 Use verbose param to control printing to stdout
----
> 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
> 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)
