[
https://issues.apache.org/jira/browse/CTAKES-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pei Chen resolved CTAKES-219.
-----------------------------
Resolution: Fixed
updated since r1509832.
Note- there may be some 3rd party libs that have console output. But at least
the ctakes code in assertion should use the same logging mechanism as the other
components now.
> configure log4j for ctakes-assertion module and remove stdout print statements
> ------------------------------------------------------------------------------
>
> Key: CTAKES-219
> URL: https://issues.apache.org/jira/browse/CTAKES-219
> Project: cTAKES
> Issue Type: Improvement
> Components: ctakes-assertion
> Affects Versions: 3.0-incubating
> Environment: Java
> Reporter: Chase Master
> Assignee: Pei Chen
> Priority: Minor
> Labels: log4j, logger
> Fix For: 3.1.1
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> Most cTAKES modules use log4j and thus the logging for most of the pipeline
> is easily configurable when included in another application. However, the
> assertion module uses the java logger, and in order to configure the
> properties (for instance, add a file handler and suppress the output to the
> console) I believe it must be done where it is instantiated (somewhere inside
> the pipeline?). Logging configuration should be possible without checking out
> the project. Also, the System.out.println statements could be removed and a
> console handler used instead. This would make cTAKES easier to use inside
> other applications.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
