[UIMA-4513] ruta-maven-plugin does not handle import by name correctly

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.3.0ruta, 2.3.1ruta
• Fix Version/s: 2.3.1ruta
• Component/s: Ruta

Environment

Mac OS X, Eclipse 4.4 (Kepler), Maven 3.2.1

• Assignee: Peter Klügl
• Reporter: Sebastian Furth
• Created: 16/Jul/15 09:17
• Updated: 16/Aug/15 15:20
• Resolved: 16/Aug/15 15:20

Description

We have two "mavenized" Ruta projects (Project A and B). The pom files in these projects strictly follow 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>