You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Beni Santos (Jira)" <de...@uima.apache.org> on 2021/12/29 12:09:00 UTC
[jira] [Created] (UIMA-6405) Local variable not captured properly in a wildcard matching condition.
Beni Santos created UIMA-6405:
---------------------------------
Summary: Local variable not captured properly in a wildcard matching condition.
Key: UIMA-6405
URL: https://issues.apache.org/jira/browse/UIMA-6405
Project: UIMA
Issue Type: Bug
Components: Ruta
Affects Versions: 3.1.0ruta, 3.0.1ruta, 2.8.1ruta
Environment: Environment:
- SO: macOS 10.14.6
- AdoptOpenJDK 1.8.0_252-b09
- uimaj-core 3.2.0
- ruta-core 3.1.0
Reporter: Beni Santos
Suppose there is a rule such as:
{code:java}
t1:MyType.featX="foo" # t2:MyType.featX="_pending"{-> SETFEATURE("featX", t1.featX)};{code}
If there is other annotation of type MyType with {{featX!="foo"}} between t1 and t2, all feats captured in the t1 variable are null.
It fails with Ruta 3.0.1, 3.1.0, 2.8.1, 2.8.0. It works with Ruta 2.7.0, 2.6.1.
A complete junit test is provided here: [https://github.com/benisantos/ruta3-wildcard-bug]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)