[
https://issues.apache.org/jira/browse/UIMA-3346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacob Carter updated UIMA-3346:
-------------------------------
Attachment: UIMA-3346.2.patch
Thanks [~rec] for the suggestions, and I agree that it makes more sense to move
this configuration out of the code and into the Maven configuration.
I have attached a replacement patch which adds a {{typeSystemDescription}}
parameter to the uimafit-maven-plugin which can take one of the following enum
values;
* {{NONE}} - DEFAULT
* {{BY_NAME}}
* {{EMBEDDED}}
An example usage would look like:
{code:xml}
<plugin>
<groupId>org.apache.uima</groupId>
<artifactId>uimafit-maven-plugin</artifactId>
<configuration>
<typeSystemDescription>BY_NAME</typeSystemDescription>
</configuration>
</plugin>
{code}
> "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.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)
