[
https://issues.apache.org/jira/browse/UIMA-852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12576589#action_12576589
]
Marshall Schor commented on UIMA-852:
-------------------------------------
The import-by-name should only be looking things up in the class path (and
datapath). The description seems to say it *is* finding things by name if the
the name is a relative path to where jcasgen is run. Is this true?
An alternative to setting up the UIMA_DATAPATH is to put the paths where you
want the import-by-name to look in, in the classpath. Have you tried this, and
is it working? If it is working, is this a sufficient approach, or do you see
a need for something more?
> jcasgen.sh has trouble with import by name
> ------------------------------------------
>
> Key: UIMA-852
> URL: https://issues.apache.org/jira/browse/UIMA-852
> Project: UIMA
> Issue Type: Bug
> Components: Tools
> Environment: Linux RHEL5.1
> IBM Java6
> Reporter: Jerry Quinn
>
> If processing a typesystem file that uses <import name="some/path/to/blah">,
> and the path to blah is not relative to where jcasgen is run, jcasgen will
> fail because uima.datapath cannot be set.
> The simplest approach to resolve it would be to read the value from an
> evironment variable such as UIMA_DATAPATH.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
