Uploaded image for project: 'UIMA'
  1. UIMA
  2. UIMA-4513

ruta-maven-plugin does not handle import by name correctly

    Details

    • 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
    • Labels:
      None
    • Environment:

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

      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>

        Attachments

          Activity

            People

            • Assignee:
              pkluegl Peter Klügl
              Reporter:
              sebastian.furth Sebastian Furth
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: