ctakes-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Joseph Masanz (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CTAKES-219) configure log4j for ctakes-assertion module and remove stdout print statements
Date Wed, 18 Sep 2013 09:16:53 GMT

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

James Joseph Masanz updated CTAKES-219:

    Fix Version/s: 3.1.1
> 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
>            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

View raw message