[
https://issues.apache.org/jira/browse/UIMA-3346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16173431#comment-16173431
]
Richard Eckart de Castilho commented on UIMA-3346:
--------------------------------------------------
I applied the patch with some modifications.
Most notable is the removal of the `BY_NAME` mode. I tried setting up an
integration test for this mode, that failed because the patch expects all type
systems to be in a JAR (accessible via a JarURLConnection) and couldn't handle
the case where the descriptors reside on the file system in the same project as
the component for which the descriptor was generated.
> "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
> Priority: Minor
> Fix For: 2.4.0Addons, 2.4.0uimaFIT
>
> 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)
