Jenkins build is back to stable : UIMA-Ruta #1060

[Apache Jenkins Server]

See 

Jenkins build is back to stable : UIMA-Ruta » Apache UIMA Ruta: ruta-core-ext #1060

[Apache Jenkins Server]

See 

Jenkins build is back to stable : UIMA-Ruta » Apache UIMA Ruta: ruta-core #1060

[Apache Jenkins Server]

See 

Jenkins build is back to stable : UIMA-Ruta Java 11 #50

[Apache Jenkins Server]

See 

Jenkins build is back to stable : UIMA-Ruta Java 11 » Apache UIMA Ruta: ruta-core-ext #50

[Apache Jenkins Server]

See 

Jenkins build is back to stable : UIMA-Ruta Java 11 » Apache UIMA Ruta: ruta-core #50

[Apache Jenkins Server]

See 

Jenkins build is still unstable: UIMA-Ruta #1059

[Apache Jenkins Server]

See 

Jenkins build is still unstable: UIMA-Ruta » Apache UIMA Ruta: ruta-core-ext #1059

[Apache Jenkins Server]

See 

Jenkins build is still unstable: UIMA-Ruta » Apache UIMA Ruta: ruta-core #1059

[Apache Jenkins Server]

See 

[jira] [Resolved] (UIMA-6193) Ruta: Initial assignment of list variables behaves strangely

[Jira]

 [ 
https://issues.apache.org/jira/browse/UIMA-6193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Klügl resolved UIMA-6193.
---
Resolution: Fixed

> Ruta: Initial assignment of list variables behaves strangely
> 
>
> Key: UIMA-6193
> URL: https://issues.apache.org/jira/browse/UIMA-6193
> Project: UIMA
>  Issue Type: Bug
>  Components: Ruta
>Affects Versions: 2.8.0ruta
>Reporter: Michael Stenger
>Assignee: Peter Klügl
>Priority: Minor
> Fix For: 2.8.1ruta, 3.0.1ruta
>
>
> When list variables are declared with a list containing variables as initial 
> value, the managing VariableListExpression seems to save the variable 
> expression given with that argument list instead of the represented values. 
> E.g.
> {code:java}
> INTLIST somelist = {var};{code}
> for a variable
> {code:java}
> INT var = 1;
> {code}
> stores the expression behind var instead of the value 1. So changing the 
> value of var after the declaration of somelist still effects the value of 
> somelist[0]. That's not the case if ADD was used instead.
> Consider this example:
> {code:java}
> DECLARE testType (StringArray arr);
> STRING s = "a";
> STRINGLIST sl = {s};
> Document{ -> ADD(sl, s), s = "b", CREATE(testType, "arr" = sl)};{code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (UIMA-6193) Ruta: Initial assignment of list variables behaves strangely

[Jira]

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

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

The values of expressions in the initialization of variables should now work as 
expected.

> Ruta: Initial assignment of list variables behaves strangely
> 
>
> Key: UIMA-6193
> URL: https://issues.apache.org/jira/browse/UIMA-6193
> Project: UIMA
>  Issue Type: Bug
>  Components: Ruta
>Affects Versions: 2.8.0ruta
>Reporter: Michael Stenger
>Assignee: Peter Klügl
>Priority: Minor
> Fix For: 2.8.1ruta, 3.0.1ruta
>
>
> When list variables are declared with a list containing variables as initial 
> value, the managing VariableListExpression seems to save the variable 
> expression given with that argument list instead of the represented values. 
> E.g.
> {code:java}
> INTLIST somelist = {var};{code}
> for a variable
> {code:java}
> INT var = 1;
> {code}
> stores the expression behind var instead of the value 1. So changing the 
> value of var after the declaration of somelist still effects the value of 
> somelist[0]. That's not the case if ADD was used instead.
> Consider this example:
> {code:java}
> DECLARE testType (StringArray arr);
> STRING s = "a";
> STRINGLIST sl = {s};
> Document{ -> ADD(sl, s), s = "b", CREATE(testType, "arr" = sl)};{code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Resolved] (UIMA-6192) VariableAssignmentExpression ignores List variables

[Jira]

 [ 
https://issues.apache.org/jira/browse/UIMA-6192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Klügl resolved UIMA-6192.
---
Resolution: Fixed

> VariableAssignmentExpression ignores List variables
> ---
>
> Key: UIMA-6192
> URL: https://issues.apache.org/jira/browse/UIMA-6192
> Project: UIMA
>  Issue Type: Bug
>  Components: Ruta
>Affects Versions: 2.8.0ruta
>Reporter: Michael Stenger
>Assignee: Peter Klügl
>Priority: Minor
> Fix For: 2.8.1ruta, 3.0.1ruta
>
>
>  Action VariableAssignmentExpression seems to ignore the assignment task if a 
> list variable is given as first argument. No exception is thrown, it just 
> does nothing. Since action ASSIGN doesn't operate on list expressions too, it 
> would be great to have this one working here.
> See the following example:
> {code:java}
>  DECLARE testType (IntegerArray arr);
>  INTLIST il;
>  Document { -> il = {1,2,3}, CREATE(testType, "arr" = il)};{code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (UIMA-6192) VariableAssignmentExpression ignores List variables

[Jira]

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

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

Thanks for reporting. This should work now, also for ASSIGN.

> VariableAssignmentExpression ignores List variables
> ---
>
> Key: UIMA-6192
> URL: https://issues.apache.org/jira/browse/UIMA-6192
> Project: UIMA
>  Issue Type: Bug
>  Components: Ruta
>Affects Versions: 2.8.0ruta
>Reporter: Michael Stenger
>Assignee: Peter Klügl
>Priority: Minor
> Fix For: 2.8.1ruta, 3.0.1ruta
>
>
>  Action VariableAssignmentExpression seems to ignore the assignment task if a 
> list variable is given as first argument. No exception is thrown, it just 
> does nothing. Since action ASSIGN doesn't operate on list expressions too, it 
> would be great to have this one working here.
> See the following example:
> {code:java}
>  DECLARE testType (IntegerArray arr);
>  INTLIST il;
>  Document { -> il = {1,2,3}, CREATE(testType, "arr" = il)};{code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Jenkins build is still unstable: UIMA-Ruta Java 11 #49

[Apache Jenkins Server]

See 

Jenkins build is still unstable: UIMA-Ruta Java 11 » Apache UIMA Ruta: ruta-core-ext #49

[Apache Jenkins Server]

See 

Jenkins build is still unstable: UIMA-Ruta Java 11 » Apache UIMA Ruta: ruta-core #49

[Apache Jenkins Server]

See 

Jenkins build became unstable: UIMA-Ruta #1058

[Apache Jenkins Server]

See 

Jenkins build became unstable: UIMA-Ruta » Apache UIMA Ruta: ruta-core-ext #1058

[Apache Jenkins Server]

See 

Jenkins build became unstable: UIMA-Ruta » Apache UIMA Ruta: ruta-core #1058

[Apache Jenkins Server]

See 

Jenkins build became unstable: UIMA-Ruta Java 11 » Apache UIMA Ruta: ruta-core #48

[Apache Jenkins Server]

See 

Jenkins build became unstable: UIMA-Ruta Java 11 #48

[Apache Jenkins Server]

See 

Jenkins build became unstable: UIMA-Ruta Java 11 » Apache UIMA Ruta: ruta-core-ext #48

[Apache Jenkins Server]

See 

[jira] [Commented] (UIMA-6193) Ruta: Initial assignment of list variables behaves strangely

[Jira]

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

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

Sorry, I missed the title of the ticket! Just to clarify, the initialization 
should not remember the expression, but only its value, right?

> Ruta: Initial assignment of list variables behaves strangely
> 
>
> Key: UIMA-6193
> URL: https://issues.apache.org/jira/browse/UIMA-6193
> Project: UIMA
>  Issue Type: Bug
>  Components: Ruta
>Affects Versions: 2.8.0ruta
>Reporter: Michael Stenger
>Assignee: Peter Klügl
>Priority: Minor
> Fix For: 2.8.1ruta, 3.0.1ruta
>
>
> When list variables are declared with a list containing variables as initial 
> value, the managing VariableListExpression seems to save the variable 
> expression given with that argument list instead of the represented values. 
> E.g.
> {code:java}
> INTLIST somelist = {var};{code}
> for a variable
> {code:java}
> INT var = 1;
> {code}
> stores the expression behind var instead of the value 1. So changing the 
> value of var after the declaration of somelist still effects the value of 
> somelist[0]. That's not the case if ADD was used instead.
> Consider this example:
> {code:java}
> DECLARE testType (StringArray arr);
> STRING s = "a";
> STRINGLIST sl = {s};
> Document{ -> ADD(sl, s), s = "b", CREATE(testType, "arr" = sl)};{code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Work started] (UIMA-6192) VariableAssignmentExpression ignores List variables

[Jira]

 [ 
https://issues.apache.org/jira/browse/UIMA-6192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Work on UIMA-6192 started by Peter Klügl.
-
> VariableAssignmentExpression ignores List variables
> ---
>
> Key: UIMA-6192
> URL: https://issues.apache.org/jira/browse/UIMA-6192
> Project: UIMA
>  Issue Type: Bug
>  Components: Ruta
>Affects Versions: 2.8.0ruta
>Reporter: Michael Stenger
>Assignee: Peter Klügl
>Priority: Minor
> Fix For: 2.8.1ruta, 3.0.1ruta
>
>
>  Action VariableAssignmentExpression seems to ignore the assignment task if a 
> list variable is given as first argument. No exception is thrown, it just 
> does nothing. Since action ASSIGN doesn't operate on list expressions too, it 
> would be great to have this one working here.
> See the following example:
> {code:java}
>  DECLARE testType (IntegerArray arr);
>  INTLIST il;
>  Document { -> il = {1,2,3}, CREATE(testType, "arr" = il)};{code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (UIMA-6193) Ruta: Initial assignment of list variables behaves strangely

[Jira]

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

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

Thanks for reporting. 

I assume that you mean that ADD should behave like the initialization and not 
that the initialization should behave like ADD. I extended ADD now that it is 
able to add expressions itself. This could lead to unexpected behavior and I 
wonder if this rigth thing to do.

What do you think?

I also wonder how REMOVE should behave. I did not change its behavior now since 
it could be reasonable to remove entries based on their acutal value instead of 
their variable reference.

> Ruta: Initial assignment of list variables behaves strangely
> 
>
> Key: UIMA-6193
> URL: https://issues.apache.org/jira/browse/UIMA-6193
> Project: UIMA
>  Issue Type: Bug
>  Components: Ruta
>Affects Versions: 2.8.0ruta
>Reporter: Michael Stenger
>Assignee: Peter Klügl
>Priority: Minor
> Fix For: 2.8.1ruta, 3.0.1ruta
>
>
> When list variables are declared with a list containing variables as initial 
> value, the managing VariableListExpression seems to save the variable 
> expression given with that argument list instead of the represented values. 
> E.g.
> {code:java}
> INTLIST somelist = {var};{code}
> for a variable
> {code:java}
> INT var = 1;
> {code}
> stores the expression behind var instead of the value 1. So changing the 
> value of var after the declaration of somelist still effects the value of 
> somelist[0]. That's not the case if ADD was used instead.
> Consider this example:
> {code:java}
> DECLARE testType (StringArray arr);
> STRING s = "a";
> STRINGLIST sl = {s};
> Document{ -> ADD(sl, s), s = "b", CREATE(testType, "arr" = sl)};{code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Work stopped] (UIMA-6193) Ruta: Initial assignment of list variables behaves strangely

[Jira]

 [ 
https://issues.apache.org/jira/browse/UIMA-6193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Work on UIMA-6193 stopped by Peter Klügl.
-
> Ruta: Initial assignment of list variables behaves strangely
> 
>
> Key: UIMA-6193
> URL: https://issues.apache.org/jira/browse/UIMA-6193
> Project: UIMA
>  Issue Type: Bug
>  Components: Ruta
>Affects Versions: 2.8.0ruta
>Reporter: Michael Stenger
>Assignee: Peter Klügl
>Priority: Minor
> Fix For: 2.8.1ruta, 3.0.1ruta
>
>
> When list variables are declared with a list containing variables as initial 
> value, the managing VariableListExpression seems to save the variable 
> expression given with that argument list instead of the represented values. 
> E.g.
> {code:java}
> INTLIST somelist = {var};{code}
> for a variable
> {code:java}
> INT var = 1;
> {code}
> stores the expression behind var instead of the value 1. So changing the 
> value of var after the declaration of somelist still effects the value of 
> somelist[0]. That's not the case if ADD was used instead.
> Consider this example:
> {code:java}
> DECLARE testType (StringArray arr);
> STRING s = "a";
> STRINGLIST sl = {s};
> Document{ -> ADD(sl, s), s = "b", CREATE(testType, "arr" = sl)};{code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Work started] (UIMA-6193) Ruta: Initial assignment of list variables behaves strangely

[Jira]

 [ 
https://issues.apache.org/jira/browse/UIMA-6193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Work on UIMA-6193 started by Peter Klügl.
-
> Ruta: Initial assignment of list variables behaves strangely
> 
>
> Key: UIMA-6193
> URL: https://issues.apache.org/jira/browse/UIMA-6193
> Project: UIMA
>  Issue Type: Bug
>  Components: Ruta
>Affects Versions: 2.8.0ruta
>Reporter: Michael Stenger
>Assignee: Peter Klügl
>Priority: Minor
> Fix For: 2.8.1ruta, 3.0.1ruta
>
>
> When list variables are declared with a list containing variables as initial 
> value, the managing VariableListExpression seems to save the variable 
> expression given with that argument list instead of the represented values. 
> E.g.
> {code:java}
> INTLIST somelist = {var};{code}
> for a variable
> {code:java}
> INT var = 1;
> {code}
> stores the expression behind var instead of the value 1. So changing the 
> value of var after the declaration of somelist still effects the value of 
> somelist[0]. That's not the case if ADD was used instead.
> Consider this example:
> {code:java}
> DECLARE testType (StringArray arr);
> STRING s = "a";
> STRINGLIST sl = {s};
> Document{ -> ADD(sl, s), s = "b", CREATE(testType, "arr" = sl)};{code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Closed] (UIMA-6202) updates due to ASF change for distribution of software

[Marshall Schor (Jira)]

 [ 
https://issues.apache.org/jira/browse/UIMA-6202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Marshall Schor closed UIMA-6202.

  Assignee: Marshall Schor
Resolution: Fixed

> updates due to ASF change for distribution of software
> --
>
> Key: UIMA-6202
> URL: https://issues.apache.org/jira/browse/UIMA-6202
> Project: UIMA
>  Issue Type: Task
>Reporter: Marshall Schor
>Assignee: Marshall Schor
>Priority: Minor
>
> ASF Infra changed how artifacts are being distributed, and asks we update our 
> websites/documentation/anything-else that referes to apache/dist (which is 
> being deprecated).
> Here's a link to what's happening: 
> [https://blogs.apache.org/infra/entry/more-secure-and-robust-downloads]
> I'll scan our website docs and fix things there.  Other projects may have 
> references to dist in their build processes that may need updating.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (UIMA-6202) updates due to ASF change for distribution of software

[Marshall Schor (Jira)]

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

Marshall Schor commented on UIMA-6202:
--

While checking the website, I found the page distribution.html - which is very 
out of date, and not referenced by anything except the sidebar.  I'm adding a 
comment at the top of the page saying it's out of date, and people should look 
at release.html instead, and removing it from the sidebar.

> updates due to ASF change for distribution of software
> --
>
> Key: UIMA-6202
> URL: https://issues.apache.org/jira/browse/UIMA-6202
> Project: UIMA
>  Issue Type: Task
>Reporter: Marshall Schor
>Priority: Minor
>
> ASF Infra changed how artifacts are being distributed, and asks we update our 
> websites/documentation/anything-else that referes to apache/dist (which is 
> being deprecated).
> Here's a link to what's happening: 
> [https://blogs.apache.org/infra/entry/more-secure-and-robust-downloads]
> I'll scan our website docs and fix things there.  Other projects may have 
> references to dist in their build processes that may need updating.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)