uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eddie Epstein (JIRA)" <uima-...@incubator.apache.org>
Subject [jira] Closed: (UIMA-1629) UIMACPP <import> behavior not sufficiently documented
Date Fri, 06 Nov 2009 16:02:32 GMT

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

Eddie Epstein closed UIMA-1629.
-------------------------------

    Resolution: Fixed

> UIMACPP <import> behavior not sufficiently documented
> -----------------------------------------------------
>
>                 Key: UIMA-1629
>                 URL: https://issues.apache.org/jira/browse/UIMA-1629
>             Project: UIMA
>          Issue Type: Bug
>          Components: C++ Framework
>            Reporter: Eddie Epstein
>
> 1. uimacpp does not support import by name <import name="..." />, which I think
is not mentioned in the documentation.
> 2. using <import location="..." /> employs a different path resolving strategy
from that of uimaj:
>  -  both  support using absolute paths and relative paths (relative to the descriptor
in which the import occurs)
>  -  uimacpp can be given the environment variable UIMACPP_DATAPATH which is additionally
used to resolve relative paths
>  - However, uimaj does not support resolving relative <import location="..." />
from it's datapath.
> Kind regards
> Matthias

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message