Sebastian Furth created UIMA-4513:
-------------------------------------
Summary: Maven plugin does not handle import by name correctly
Key: UIMA-4513
URL: https://issues.apache.org/jira/browse/UIMA-4513
Project: UIMA
Issue Type: Bug
Components: ruta
Affects Versions: 2.3.0ruta, 2.3.1ruta
Environment: Mac OS X, Eclipse 4.4 (Kepler), Maven 3.2.1
Reporter: Sebastian Furth
Priority: Critical
Fix For: 2.3.1ruta
We have two "mavenized" Ruta projects (Project A and B). The pom files in these
projects strictly follows the ruta-maven-example.
Project A contains some basic scripts that shall be reused in other Ruta
projects. Thus Project B has a maven dependency to Project A.
The ruta-maven-plugin has a configuration parameter that handles the type of
import (by location or by name), e.g. <importByName>false</importByName>
Setting importByName to true rises the following issues:
1. The generated TypeSystem descriptors do not contain the types of the
BasicTypeSystem, i.e. the scripts can not resolve the basic types.
2. The generated Engine descriptors contain import statements that are not
fully qualified, i.e. the package of referenced engines is missing.
The following example shows the errornous import of the TypeSystem
„com.denkbares.ruta.structures.LinesTypeSystem"
<typeSystemDescription>
<imports>
<import name="LinesTypeSystem"/>
</imports>
</typeSystemDescription>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
