You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Marshall Schor (JIRA)" <de...@uima.apache.org> on 2017/03/06 18:27:33 UTC

[jira] [Resolved] (UIMA-5352) uv3 logger test dependencies incorrect or missing

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

Marshall Schor resolved UIMA-5352.
----------------------------------
    Resolution: Fixed

> uv3 logger test dependencies incorrect or missing
> -------------------------------------------------
>
>                 Key: UIMA-5352
>                 URL: https://issues.apache.org/jira/browse/UIMA-5352
>             Project: UIMA
>          Issue Type: Bug
>          Components: Core Java Framework
>            Reporter: Marshall Schor
>            Assignee: Marshall Schor
>             Fix For: 3.0.0SDK-alpha02
>
>
> Some test cases need the logger.  The uv3 default logger is no logger - and slf4j uses its "NOP" logger.  To make these tests work like they do in v2, add a test dependency on the slf4j-jdk14 adapter.  
> One project had this accidentally added but not as a test scope (it used the default compile scope).  This worked, except it showed up a (probable) bug in Maven / Invoker, when running the jcasgen-maven-plugin integration tests - the slfj4-api would go missing from the jcasgen maven plugin's environment.  Fixing the other dependency in uimaj-cpe for slfj4-jdk14 to "test" made the invoker plugin no longer delete the slf4j-api jar from its execution classpath.  (Documented here for historical reasons, and because it took most of a day to debug this!)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)