[
https://issues.apache.org/jira/browse/UIMA-3303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13783538#comment-13783538
]
Alexandre Patry commented on UIMA-3303:
---------------------------------------
{quote}
The descriptor generation functionality should be moved to ruta-core since
someone may want to use this also without the workbench.
{quote}
I would like that a lot. I have started to work on a ruta-maven-plugin to do
just that and was slowed down by the dependencies of the descriptor generator
on eclipse.
{quote}
Can you explain the differences between Richards syntax and your syntax to me?
Sorry, I am a bit slow on the uptake.
Why the PACKAGE? If the typesystemfile is given, then I would assume that the
package within the type system is meant. And if there is no file given, then
let uimaFIT find it in the classpath.
{quote}
Blame it on the quality of my english as a second language that gets worse at
night :)
There are two main differences:
* I do not like {{IMPORT * FROM <typesystem> AS <prefix>}} because a type
system can define many packages or a package that is not related to its name.
It seems more natural to me to import packages explicitly.
* {{IMPORT a.b.c AS d}} could either be _import type a.b.c as d_ or _import
package a.b.c as d_. The {{PACKAGE}} keyword disambiguate this case.
> Add a way to alias types in RUTA (e.g. "IMPORT type AS alias")
> --------------------------------------------------------------
>
> Key: UIMA-3303
> URL: https://issues.apache.org/jira/browse/UIMA-3303
> Project: UIMA
> Issue Type: Bug
> Components: ruta
> Reporter: Alexandre Patry
> Assignee: Alexandre Patry
>
> It would be convenient to define type aliases in RUTA script.
> One scenario where it would help is when many types have the same short name:
> {noformat}
> IMPORT com.example.a.T AS TA
> IMPORT com.example.b.T AS TB
> {noformat}
> For a discussion about it, see UIMA-3292.
--
This message was sent by Atlassian JIRA
(v6.1#6144)