[jira] [Commented] (UIMA-4639) ruta-maven-plugin misses qualification of names when importing by name

["Peter Klügl (JIRA)" <de...@uima.apache.org>]

    [ https://issues.apache.org/jira/browse/UIMA-4639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14970897#comment-14970897 ] 

Peter Klügl commented on UIMA-4639:
-----------------------------------

With which version did the error occur? Did you test it also with the current trunk? It's possible that I already fixed this problem, or at least parts of it.

> ruta-maven-plugin misses qualification of names when importing by name
> ----------------------------------------------------------------------
>
>                 Key: UIMA-4639
>                 URL: https://issues.apache.org/jira/browse/UIMA-4639
>             Project: UIMA
>          Issue Type: Bug
>          Components: ruta
>    Affects Versions: 2.3.1ruta
>            Reporter: Armin Wegner
>            Assignee: Peter Klügl
>             Fix For: 2.4.0ruta
>
>
> The resource names in the descriptors generated by ruta-maven-plugin have no name qualification at all when importing resources by name. The package names are ignored. 
> I've created a new Maven project. Added /src/main/ruta as source folder and put the scripts therein. There's no Java involved. The project was deployed with Maven and referenced by a Java UIMA project. Because a variant of the CPE builder from uimaFIT is used, all imports must be by name (The desciptor file of the UIMA aggregate is temporarily written to the systems temp folder). Resource resolution fails. But adding the name qualifications manually solves the issue, e. g. prepending org.apache.uima.ruta.engine to BasicTypeSystem or the project's package names to the generated resources.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)