[
https://issues.apache.org/jira/browse/UIMA-3292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13778570#comment-13778570
]
Peter Klügl commented on UIMA-3292:
-----------------------------------
If this step is for the AE, then this would of course solve the problem with
the unknown aggregated AE inclunding the script as we can just solve the
conflicting name to the import only and not to the type system. I think know I
understood you :-)
> Conflicting types are not flagged by RUTA
> -----------------------------------------
>
> Key: UIMA-3292
> URL: https://issues.apache.org/jira/browse/UIMA-3292
> Project: UIMA
> Issue Type: Bug
> Components: ruta
> Affects Versions: 2.1.0ruta
> Reporter: Alexandre Patry
> Assignee: Alexandre Patry
> Fix For: 2.1.1ruta
>
>
> *Steps to reproduce*
> # Create a RUTA script containing the rule {{W {-> T1}}}
> # Add this script to an aggregate whose type system contains {{conflicting.W}}
> # Run the script on the text _word_
> *Expected behaviour*
> _word_ is annotated with {{T1}}
> *Observed behaviour*
> Depending on the on the order in which the types iterated on in
> RutaEnvironment#initializeTypes, one of the following is observed:
> * {{W}} is resolved to {{org.apache.uima.ruta.type.W}} and _word_ is
> annotated with {{T1}}
> * {{W}} is resolved to {{conflicting.W}} and no {{T1}} annotation is created.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
