You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Richard Eckart de Castilho (JIRA)" <de...@uima.apache.org> on 2017/11/09 20:20:01 UTC
[jira] [Resolved] (UIMA-3346) "generate" goal should include type
system imports
[ https://issues.apache.org/jira/browse/UIMA-3346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Richard Eckart de Castilho resolved UIMA-3346.
----------------------------------------------
Resolution: Fixed
Marking as resolved as announced. BY_NAME should be implemented via another issue if required.
> "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.2.0uimaFIT
> Reporter: Jens Grivolla
> Assignee: Richard Eckart de Castilho
> Priority: Minor
> Fix For: 2.3.1uimaFIT
>
> Attachments: UIMA-3346.2.patch, UIMA-3346.patch
>
>
> 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.4.14#64029)