[
https://issues.apache.org/jira/browse/UIMA-2012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13023177#comment-13023177
]
Richard Eckart de Castilho commented on UIMA-2012:
--------------------------------------------------
I would prefer not having to maintain the datapath setting, in particular since
I have a large number of Maven projects using UIMA and I rely very much on the
dependency resolution of Maven. Also, I believe if I point the datapath to a
JAR, it'd might not be able to locate the type system descriptions within.
The Component Description Editor seems to be able to locate descriptors for
import-by-name via the classpath of a Java project. E.g. when I navigate to my
uimaFIT project, open the NoOpAnnotator.xml in the CDE, go to the type systems
tab and press "add", I can see a list of all XML files reachable from the that
project via the classpath, i.e. XML files in uimaFIT, uimaj-tools, etc.
The CDE does indeed import JDT packages in its plugin.xml.
> Handling of imported type systems causes error
> ----------------------------------------------
>
> Key: UIMA-2012
> URL: https://issues.apache.org/jira/browse/UIMA-2012
> Project: UIMA
> Issue Type: Bug
> Components: CasEditor
> Reporter: Peter Klügl
> Assignee: Jörn Kottmann
> Priority: Minor
> Fix For: 2.3.2SDK
>
>
> When opening a XMI with a type system that imports other type systems (by
> location), the editor displays an error. This problem occurs, if XMI contains
> data of types that are specified in the imported type systems. May be related
> to UIMA-2011.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
