[
https://issues.apache.org/jira/browse/UIMA-3346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13794022#comment-13794022
]
Richard Eckart de Castilho commented on UIMA-3346:
--------------------------------------------------
If the information is contained in the descriptor, then UIMA may bark if the AE
descriptor gets incompatibly out-of-sync with other AE descriptors.
So how do you expect it to work? The maven plugin finds the types.txt files in
the usual locations and adds all the type descriptors it finds that way to the
generated descriptor as import-by-name?
> "generate" goal should include type system imports
> --------------------------------------------------
>
> Key: UIMA-3346
> URL: https://issues.apache.org/jira/browse/UIMA-3346
> Project: UIMA
> Issue Type: Improvement
> Components: uimaFIT-Maven-Plugin
> Affects Versions: 2.1.0uimaFIT
> Reporter: Jens Grivolla
> Priority: Minor
>
> The "generate" goal of the uimaFIT maven plugin should include type system
> imports in the generated descriptors. This would make those descriptors
> directly usable in descriptor-based workflows such as CPE or UIMA-AS.
> In our case, we point to the TS descriptor files directly in types.txt, thus
> not relying on any "magic" TS discovery. This could translate directly to a
> corresponding import by name in the XML descriptor. More sophisticated setups
> might of course be more difficult to handle.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
