[
https://issues.apache.org/jira/browse/UIMA-3346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16142740#comment-16142740
]
Richard Eckart de Castilho commented on UIMA-3346:
--------------------------------------------------
[~jacobcarter] Thanks! That looks like a useful addition.
I am not sure though that controlling the generation of imports via an
annotation is the best way. That means, that the developer of a component
controls whether the imports are generated. So e.g. if somebody want to
generate descriptors for a third-party component, that person will have to live
with whatever choice the component developer made.
Wouldn't it be more sensible to add a parameter to the "generate" goal where
the person that generates the descriptors can control whether or not they want
to have type system information in the generated descriptor?
The parameter could offer the choice between e.g.
* "none" - no type system information in the descriptor
* "embedded" - render type systems directly into the descriptor
* "by-name" - use import by name
* "by-location" use import by location
(which of the settings above are implemented would depend on
demand/contributions).
> "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
> Attachments: 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)
