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

Posted to dev@uima.apache.org by "Jim Challenger (JIRA)" <de...@uima.apache.org> on 2015/03/26 20:54:52 UTC

[jira] [Closed] (UIMA-4186) DUCC Logger: use log4j API for configuration, not classpath element

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

Jim Challenger closed UIMA-4186.
--------------------------------
    Resolution: Fixed

> DUCC Logger: use log4j API for configuration, not classpath element
> -------------------------------------------------------------------
>
>                 Key: UIMA-4186
>                 URL: https://issues.apache.org/jira/browse/UIMA-4186
>             Project: UIMA
>          Issue Type: Improvement
>          Components: DUCC
>    Affects Versions: 1.1.0-Ducc
>            Reporter: Jim Challenger
>            Assignee: Jim Challenger
>             Fix For: 2.0.0-Ducc
>
>
> Use the log4j API to configure the ducc logger and remove ducc_runtime/resources from the classpath.
> This is because 3rd party stuff is trying to load from our log4j.xml and sometimes crashes due to non-presence of a custom appender. 



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