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

Posted to dev@uima.apache.org by "Burn Lewis (JIRA)" <de...@uima.apache.org> on 2015/04/03 23:01:53 UTC

[jira] [Commented] (UIMA-3846) The cli jar should reference a complete consistent set of UIMA jars

    [ https://issues.apache.org/jira/browse/UIMA-3846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14395070#comment-14395070 ] 

Burn Lewis commented on UIMA-3846:
----------------------------------

Starting with DUCC 2.0 the user's code is isolated from the DUCC jars used to run the JD & JPs, so all the UIMA jars needed by the user code MUST be provided in the user's classpath.  None are in the cli jar.

> The cli jar should reference a complete consistent set of UIMA jars
> -------------------------------------------------------------------
>
>                 Key: UIMA-3846
>                 URL: https://issues.apache.org/jira/browse/UIMA-3846
>             Project: UIMA
>          Issue Type: Bug
>          Components: DUCC
>    Affects Versions: 1.1.0-Ducc
>            Reporter: Burn Lewis
>            Assignee: Burn Lewis
>            Priority: Minor
>
> When the cli jar's manifest adds only 2 of the UIMA jars, others added to the classpath may cause a UIMA version mismatch error.  Simplest fix is to add a consistent set. 



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