July 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-5282) Client side FEEL

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5282?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5282: ----------------------------------- Sprint: 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25), 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6), 2020 Week 31-33 (from Jul 27) (was: 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25), 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6)) > Client side FEEL > ---------------- > > Key: DROOLS-5282 > URL: https://issues.redhat.com/browse/DROOLS-5282 > Project: Drools > Issue Type: Epic > Components: DMN Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > Make kie-dmn-feel usable in the client side. > Notes: > * FEEL functions use reflection, but many if not all of them can be hard coded -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5259) DMN Validation takes 15s in the BC while the same file takes half a second as an unit test

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5259?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5259: ----------------------------------- Sprint: 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25), 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6), 2020 Week 31-33 (from Jul 27) (was: 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25), 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6)) > DMN Validation takes 15s in the BC while the same file takes half a second as an unit test > ------------------------------------------------------------------------------------------ > > Key: DROOLS-5259 > URL: https://issues.redhat.com/browse/DROOLS-5259 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > Problem might be related to some limitation with Wildfly. It felt even slower with drools-wb-showcase, but need to time it. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5203) Make DMN Validator use generic V&V module for conflicting, misleading, masked and overlapping rows

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5203?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5203: ----------------------------------- Sprint: 2020 Week 13-15 (from Mar 23), 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25), 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6), 2020 Week 31-33 (from Jul 27) (was: 2020 Week 13-15 (from Mar 23), 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25), 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6)) > Make DMN Validator use generic V&V module for conflicting, misleading, masked and overlapping rows > -------------------------------------------------------------------------------------------------- > > Key: DROOLS-5203 > URL: https://issues.redhat.com/browse/DROOLS-5203 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > Goal is to merge and reuse the existing generic validator for the issue types in the title. The user should see no difference in the workbench use, but this will help us to reduce reduncancy and improve future V&V coverage for both DMN and DRL at the same time. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5240) Remove MVEL from Drools

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5240?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5240: ----------------------------------- Sprint: 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25), 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6), 2020 Week 31-33 (from Jul 27) (was: 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25), 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6)) > Remove MVEL from Drools > ----------------------- > > Key: DROOLS-5240 > URL: https://issues.redhat.com/browse/DROOLS-5240 > Project: Drools > Issue Type: Epic > Components: core engine > Reporter: Luca Molteni > Assignee: Luca Molteni > Priority: Major > Labels: MDP_BRAINFARTS > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4865) Add i18n reporting for DMN V&V

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4865?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4865: ----------------------------------- Sprint: 2020 Week 07-09 (from Feb 10), 2020 Week 10-12 (from Mar 2), 2020 Week 13-15 (from Mar 23), 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25), 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6), 2020 Week 31-33 (from Jul 27) (was: 2020 Week 07-09 (from Feb 10), 2020 Week 10-12 (from Mar 2), 2020 Week 13-15 (from Mar 23), 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25), 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6)) > Add i18n reporting for DMN V&V > ------------------------------ > > Key: DROOLS-4865 > URL: https://issues.redhat.com/browse/DROOLS-4865 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > The current reporting from the shared V&V is showing debug messages that are not meant for user to see and the custom DMN V&V is not i18n. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4461) Use date picker for LocalDate

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4461?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4461: ----------------------------------- Sprint: 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25), 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6), 2020 Week 31-33 (from Jul 27) (was: 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25), 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6)) > Use date picker for LocalDate > ----------------------------- > > Key: DROOLS-4461 > URL: https://issues.redhat.com/browse/DROOLS-4461 > Project: Drools > Issue Type: Enhancement > Components: Guided Decision Table Editor, Guided Rule Editor, Test Scenarios Editor > Reporter: Toni Rikkola > Assignee: Jozef Marko > Priority: Major > Labels: drools-tools > > We should use the date picker for LocalDate like we do for Date. > h2. Acceptance test > - Guided rule condition (/) > - Guided rule action (/) > - Guided rule template condition (/) > - Guided rule template action (/) > - Guided decision table simple condition (/) > - Guided decision table BRL condition (/) > - Guided decision table simple action (/) > - Guided decision table BRL action (/) -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4367) Tests in drools coverage are not really using the executable model

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4367?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4367: ----------------------------------- Sprint: 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9), 2020 Week 13-15 (from Mar 23), 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6), 2020 Week 31-33 (from Jul 27) (was: 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9), 2020 Week 13-15 (from Mar 23), 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6)) > Tests in drools coverage are not really using the executable model > ------------------------------------------------------------------ > > Key: DROOLS-4367 > URL: https://issues.redhat.com/browse/DROOLS-4367 > Project: Drools > Issue Type: Bug > Reporter: Luca Molteni > Assignee: Daniel Rosa > Priority: Minor > > Such as > https://github.com/kiegroup/drools/blob/ba9c79c4bfaf9cfc1ec2363bee3865c3d... > Even if the test itself is parametrized, in the body it calls directly buildAll therefore discarding the executable model -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5394) Coverage Report Improvements (CVS File)

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5394?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5394: ----------------------------------- Sprint: 2020 Week 22-24 (from May 25), 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6), 2020 Week 31-33 (from Jul 27) (was: 2020 Week 22-24 (from May 25), 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6)) > Coverage Report Improvements (CVS File) > --------------------------------------- > > Key: DROOLS-5394 > URL: https://issues.redhat.com/browse/DROOLS-5394 > Project: Drools > Issue Type: Enhancement > Reporter: Yeser Amer > Assignee: Yeser Amer > Priority: Major > Labels: ScenarioSimulation, drools-tools > > Proposed solution tohttps://issues.redhat.com/browse/RHPAM-2616, is to put the same data shown on Coverage Report inside the generated CSV Report file. > This means to add following data: > Overall Stats (Available rules, executed rules, coverage percentage); > Rules counters -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5502) DMN Generate Strongly Typed Output Set

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5502?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5502: ----------------------------------- Sprint: 2020 Week 28-30 (from Jul 6), 2020 Week 31-33 (from Jul 27) (was: 2020 Week 28-30 (from Jul 6)) > DMN Generate Strongly Typed Output Set > -------------------------------------- > > Key: DROOLS-5502 > URL: https://issues.redhat.com/browse/DROOLS-5502 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Affects Versions: 7.40.0.Final > Reporter: Luca Molteni > Assignee: Toshiya Kobayashi > Priority: Major > > Currently DMN output values are rapresented as a map. > > By levering the strongly typed functionality we can provide a strongly typed output that can be used in swagger to document the output of a REST endpoint -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5378) Alpha Node ordering

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-5378?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-5378: ----------------------------------- Sprint: 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6), 2020 Week 31-33 (from Jul 27) (was: 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6)) > Alpha Node ordering > ------------------- > > Key: DROOLS-5378 > URL: https://issues.redhat.com/browse/DROOLS-5378 > Project: Drools > Issue Type: Enhancement > Components: core engine > Affects Versions: 7.38.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > Re-order Alpha Node based on some strategies: > - Expression usage count > - Other strategies : Chapter 9 "Ordering Conditions" in http://i.stanford.edu/pub/cstr/reports/cs/tr/86/1124/CS-TR-86-1124.pdf > It would contribute to maximise sharing and minimise the number of evaluations. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2020