You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Eddie Epstein (JIRA)" <ui...@incubator.apache.org> on 2009/10/21 15:59:59 UTC
[jira] Created: (UIMA-1629) UIMACPP behavior not
sufficiently documented
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.
[jira] Closed: (UIMA-1629) UIMACPP behavior not
sufficiently documented
Posted by "Eddie Epstein (JIRA)" <ui...@incubator.apache.org>.
[ 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.
[jira] Updated: (UIMA-1629) UIMACPP behavior not
sufficiently documented
Posted by "Marshall Schor (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marshall Schor updated UIMA-1629:
---------------------------------
Fix Version/s: 2.3C
> 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
> Fix For: 2.3C
>
>
> 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.