[JBoss JIRA] (DROOLS-1767) FEEL: add compile-time cycle detection
by Kris Verlaenen (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1767?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-1767:
-----------------------------------
Sprint: 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52, 2018 Week 01-02 (was: 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52)
> FEEL: add compile-time cycle detection
> ---------------------------------------
>
> Key: DROOLS-1767
> URL: https://issues.jboss.org/browse/DROOLS-1767
> Project: Drools
> Issue Type: Enhancement
> Components: dmn engine
> Affects Versions: 7.4.1.Final
> Reporter: Fedor Gavrilov
> Assignee: Fedor Gavrilov
> Priority: Minor
>
> Similar to what's done in https://issues.jboss.org/browse/DROOLS-1730 but during validation stage
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 2 months
[JBoss JIRA] (DROOLS-1770) More FEEL runtime cycle detection tests
by Kris Verlaenen (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1770?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-1770:
-----------------------------------
Sprint: 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52, 2018 Week 01-02 (was: 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52)
> More FEEL runtime cycle detection tests
> ---------------------------------------
>
> Key: DROOLS-1770
> URL: https://issues.jboss.org/browse/DROOLS-1770
> Project: Drools
> Issue Type: Enhancement
> Components: dmn engine
> Affects Versions: 7.4.1.Final
> Reporter: Fedor Gavrilov
> Assignee: Fedor Gavrilov
> Priority: Minor
>
> Runtime cycle detecton lacks tests for false positive, such as deadly diamond topology:
> A depends on B and C
> B and C depend on D
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 2 months
[JBoss JIRA] (DROOLS-1701) FEEL code generation and compilation
by Kris Verlaenen (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1701?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-1701:
-----------------------------------
Sprint: 2017 Week 36-37, 2017 Week 38-39, 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52, 2018 Week 01-02 (was: 2017 Week 36-37, 2017 Week 38-39, 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52)
> FEEL code generation and compilation
> ------------------------------------
>
> Key: DROOLS-1701
> URL: https://issues.jboss.org/browse/DROOLS-1701
> Project: Drools
> Issue Type: Task
> Components: dmn engine
> Reporter: Matteo Mortari
> Assignee: Matteo Mortari
>
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 2 months
[JBoss JIRA] (DROOLS-1795) [Guided Decision Table] Invalid error message when renaming bound variable name in conditional BRL column.
by Kris Verlaenen (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1795?page=com.atlassian.jira.plugi... ]
Kris Verlaenen updated DROOLS-1795:
-----------------------------------
Sprint: 2017 Week 38-39, 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52, 2018 Week 01-02 (was: 2017 Week 38-39, 2017 Week 40-41-42, 2017 Week 43-44, 2017 Week 45-46, 2017 Week 47-48, 2017 Week 49-50, 2017 Week 51-52)
> [Guided Decision Table] Invalid error message when renaming bound variable name in conditional BRL column.
> ----------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-1795
> URL: https://issues.jboss.org/browse/DROOLS-1795
> Project: Drools
> Issue Type: Bug
> Components: Guided Decision Table Editor
> Affects Versions: 7.0.0.Final
> Reporter: Mark Coble
> Assignee: Mark Coble
> Priority: Minor
> Fix For: 7.0.0.Final
>
> Attachments: guvnor-3507.png
>
>
> If a condition BRL column is added to a DT with bound variables that are used in an action column and that variable name is subsequently changed, the attached error message occurs when updating the action column with the new variable name. In the attached message the original variable name is 'app'. Hitting 'ok' returns you to the DT which has actually refactored the DT with the new variable name and validation is successful.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 2 months