December 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4847) [DMN Designer] Entries are expanded when user edit structures in a row

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4847?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4847: ----------------------------------- Sprint: 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30) (was: 2019 Week 50-52 (from Dec 9)) > [DMN Designer] Entries are expanded when user edit structures in a row > ----------------------------------------------------------------------- > > Key: DROOLS-4847 > URL: https://issues.redhat.com/browse/DROOLS-4847 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.31.0.Final > Reporter: Jozef Marko > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Attachments: edit-in-a-row.webm > > > Data types entries are unexpectedly expanded when user click edit button of structures in a row. See the attached video. > The issue was found during DROOLS-4795 review, however probably it is not related. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4817) Raise the timeout for generated tests

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4817?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4817: ----------------------------------- Sprint: 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30) (was: 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9)) > Raise the timeout for generated tests > ------------------------------------- > > Key: DROOLS-4817 > URL: https://issues.redhat.com/browse/DROOLS-4817 > Project: Drools > Issue Type: Bug > Reporter: Daniel Rosa > Assignee: Daniel Rosa > Priority: Major > > On Jenkins the generated tests are slower so we need to raise the timeout. If this doesn't help we need to investigate more. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4835) Raise the timeout for generated tests - backport only this changes to 7.6

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4835?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4835: ----------------------------------- Sprint: 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30) (was: 2019 Week 50-52 (from Dec 9)) > Raise the timeout for generated tests - backport only this changes to 7.6 > ------------------------------------------------------------------------- > > Key: DROOLS-4835 > URL: https://issues.redhat.com/browse/DROOLS-4835 > Project: Drools > Issue Type: Bug > Reporter: Daniel Rosa > Assignee: Daniel Rosa > Priority: Major > > On Jenkins the generated tests are slower so we need to raise the timeout. If this doesn't help we need to investigate more. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4834) Raise the timeout for concurrency tests

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4834?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4834: ----------------------------------- Sprint: 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30) (was: 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9)) > Raise the timeout for concurrency tests > ---------------------------------------- > > Key: DROOLS-4834 > URL: https://issues.redhat.com/browse/DROOLS-4834 > Project: Drools > Issue Type: Bug > Reporter: Daniel Rosa > Assignee: Daniel Rosa > Priority: Major > > On Jenkins the tests are slower so we need to raise the timeout. If this doesn't help we need to investigate more. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4856) Raise the timeout for concurrency tests - backport to 7.6

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4856?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4856: ----------------------------------- Sprint: 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30) (was: 2019 Week 50-52 (from Dec 9)) > Raise the timeout for concurrency tests - backport to 7.6 > --------------------------------------------------------- > > Key: DROOLS-4856 > URL: https://issues.redhat.com/browse/DROOLS-4856 > Project: Drools > Issue Type: Bug > Reporter: Daniel Rosa > Assignee: Daniel Rosa > Priority: Major > > On Jenkins the tests are slower so we need to raise the timeout. If this doesn't help we need to investigate more. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4736) Invalid JPMS module names

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4736?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4736: ----------------------------------- Sprint: 2019 Week 44-46 (from Okt 28), 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30) (was: 2019 Week 44-46 (from Okt 28), 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9)) > Invalid JPMS module names > ------------------------- > > Key: DROOLS-4736 > URL: https://issues.redhat.com/browse/DROOLS-4736 > Project: Drools > Issue Type: Bug > Affects Versions: 7.29.0.Final > Environment: Java 9+ > Reporter: Martin Kröning > Assignee: Jiri Petrlik > Priority: Major > > The drools-model modules contain dashes in their JPMS module name, making it impossible to use them on the module path: > {code} > org.drools.canonical-model > org.drools.mvel-compiler > org.drools.mvel-parser > org.drools.model-compiler > {code} > See [sormuras/modules|https://github.com/sormuras/modules#about-java-module-names] for details about Java module names. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4733) [DMN Designer] Code Completion - Improve list of functions

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4733?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4733: ----------------------------------- Sprint: 2019 Week 44-46 (from Okt 28), 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30) (was: 2019 Week 44-46 (from Okt 28), 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9)) > [DMN Designer] Code Completion - Improve list of functions > ---------------------------------------------------------- > > Key: DROOLS-4733 > URL: https://issues.redhat.com/browse/DROOLS-4733 > Project: Drools > Issue Type: Enhancement > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > > Currently the code completion uses a small set of functions. However it must have all functions listed in the following classes: > - https://github.com/kiegroup/drools/blob/master/kie-dmn/kie-dmn-feel/src/m... > - https://github.com/kiegroup/drools/blob/master/kie-dmn/kie-dmn-feel/src/m... -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4507) Ability to externally execute project defined tests.

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4507?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4507: ----------------------------------- Sprint: 2019 Week 41-43 (from Okt 7), 2019 Week 44-46 (from Okt 28), 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30) (was: 2019 Week 41-43 (from Okt 7), 2019 Week 44-46 (from Okt 28), 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9)) > Ability to externally execute project defined tests. > ---------------------------------------------------- > > Key: DROOLS-4507 > URL: https://issues.redhat.com/browse/DROOLS-4507 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Reporter: Paul Brown > Assignee: Daniele Zonca > Priority: Major > Labels: drools-tools > > Provide the ability to externally invoke project define tests scenario i.e via a rest api. > This is required in order for project defined tests to be reused and executed as part of a delivery pipeline and not from within business central. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4636) Update Scenario Cheatsheet to mention MVEL and Background

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4636?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4636: ----------------------------------- Sprint: 2019 Week 44-46 (from Okt 28), 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30) (was: 2019 Week 44-46 (from Okt 28), 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9)) > Update Scenario Cheatsheet to mention MVEL and Background > --------------------------------------------------------- > > Key: DROOLS-4636 > URL: https://issues.redhat.com/browse/DROOLS-4636 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Affects Versions: 7.27.0.Final > Reporter: Anna Dupliak > Assignee: Daniele Zonca > Priority: Minor > Labels: CustomerFocus, drools-tools > > Update Scenario Cheatsheet for MVEL expression usage. > h3. Here are some topics that could be mentioned: > Expressions for Rule based scenarios for simple types > * Starts from "*#*" > * Runs for +properties+ > * Runs for +duplicated+ properties > * Returns the +same+ type as property type in *GIVEN* > * Returns boolean in *EXPECTED* > * Receives rule processed value as a *parameter* in *EXPECTED* via keyword "*actualValue*" > * Applies java.util.Objects.equals(actualValue, expression result) on the expression result if the *EXPECTED* value not a *boolean* > * Could run any of java function for the project > * Exports and imports as any other value > Limitations > 1. Mvel expression results +not property same+ type - drives scenario +failure, error reason and highlighted+ > Use case: > User inputs 1/2 to Integer property > 2.Mvel execution throws +exception+ - drives scenario execution +stopping, failure, error alert+ > Use case: > User inputs inexistent MVEL function in one of the properties > 3.Mvel expression +exception stops+ expression +execution+ for all *EXPECT* colons > Use case: > User got one of the GIVEN fact expression excepted > 4.Mvel +cannot be mixed+ with simple expressions in one cell > Use case: > For cell inputs : > {code:java} > [#4+4,68] > #actualvalue>1 > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4618) Test Scenario: refactor ExpressionEvaluator implementations

by Kris Verlaenen (Jira)

[ https://issues.redhat.com/browse/DROOLS-4618?page=com.atlassian.jira.plug... ] Kris Verlaenen updated DROOLS-4618: ----------------------------------- Sprint: 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9), 2020 Week 01-03 (from Dec 30) (was: 2019 Week 47-49 (from Nov 18), 2019 Week 50-52 (from Dec 9)) > Test Scenario: refactor ExpressionEvaluator implementations > ----------------------------------------------------------- > > Key: DROOLS-4618 > URL: https://issues.redhat.com/browse/DROOLS-4618 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Minor > Labels: ScenarioSimulation, drools-tools > > Refactor ExpressionEvaluator implementations moving from Object to String for rawExpression (and move as much as possible logic to common class) > See https://github.com/kiegroup/drools/pull/2563#discussion_r331352927 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2019