ctakes-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chase Master (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CTAKES-219) configure log4j for ctakes-assertion module and remove stdout print statements
Date Wed, 31 Jul 2013 19:37:52 GMT
Chase Master created CTAKES-219:
-----------------------------------

             Summary: 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


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

Mime
View raw message