[
https://issues.apache.org/jira/browse/UIMA-2672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13660437#comment-13660437
]
Peter Klügl commented on UIMA-2672:
-----------------------------------
TYPESYSTEM loads a type system descriptor with the dkpro types, which is
located in the descriptor folder. I think Martin actually used that method on
all dkpro types systems and generated the descriptor.
Martin has already told me about the approach with the text file in the
meta-inf folder. It's definitely somethig that should be included in Ruta
sometime, but I think it won't be straightforward to add it. Many problems can
emerge, e.g., the differences between "compile" and "runtime", which can
influence autocompletion and syntax checks. You would have to search for the
text files in the dependencies of the Ruta project. There is also no meta-inf
folder in Ruta projects right now. The problems that might occur are all
solvable, but I want to take enough time to think about the possible
consequences before starting to code.
If you want you can open a feature request for it, or I will create one
sometime ;-)
> TextMarker: Enable direct import of uimaFIT analysis engines
> ------------------------------------------------------------
>
> Key: UIMA-2672
> URL: https://issues.apache.org/jira/browse/UIMA-2672
> Project: UIMA
> Issue Type: New Feature
> Components: ruta
> Affects Versions: 2.0.0TextMarker
> Reporter: Peter Klügl
> Assignee: Peter Klügl
> Fix For: 2.0.2ruta
>
>
> Currently, only analysis engines imported by referencing the descriptor file
> are available. It would be useful, if uimaFIT analysis engines can directly
> imported into a TextMarker script by referencing the actual implementation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
