June 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4094) Replace DmnName input element in SettingsDock to DropDown widget

by Kris Verlaenen (Jira)

[ https://issues.jboss.org/browse/DROOLS-4094?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-4094: ----------------------------------- Sprint: 2019 Week 23-25, 2019 Week 26-28 (was: 2019 Week 23-25) > Replace DmnName input element in SettingsDock to DropDown widget > ---------------------------------------------------------------- > > Key: DROOLS-4094 > URL: https://issues.jboss.org/browse/DROOLS-4094 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Reporter: Yeser Amer > Assignee: Yeser Amer > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4072) Search query is not empty but all data objects listed

by Kris Verlaenen (Jira)

[ https://issues.jboss.org/browse/DROOLS-4072?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-4072: ----------------------------------- Sprint: 2019 Week 23-25, 2019 Week 26-28 (was: 2019 Week 23-25) > Search query is not empty but all data objects listed > ----------------------------------------------------- > > Key: DROOLS-4072 > URL: https://issues.jboss.org/browse/DROOLS-4072 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.23.0.Final > Reporter: Jozef Marko > Assignee: Yeser Amer > Priority: Major > Labels: drools-tools > Attachments: search.webm > > > In the attached video is shown sequence of steps that shows search query is ignored. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3743) Implement Test scenario coverage report for RULE

by Kris Verlaenen (Jira)

[ https://issues.jboss.org/browse/DROOLS-3743?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-3743: ----------------------------------- Sprint: 2019 Week 23-25, 2019 Week 26-28 (was: 2019 Week 23-25) > Implement Test scenario coverage report for RULE > ------------------------------------------------ > > Key: DROOLS-3743 > URL: https://issues.jboss.org/browse/DROOLS-3743 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Major > Labels: ScenarioSimulation > > Use this ticket as specs > https://issues.jboss.org/browse/DROOLS-3516 -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3954) DM UX solutions for communicating errors in graphs & grids.

by Kris Verlaenen (Jira)

[ https://issues.jboss.org/browse/DROOLS-3954?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-3954: ----------------------------------- Sprint: 2019 Week 17-19, 2019 Week 20-22, 2019 Week 23-25, 2019 Week 26-28 (was: 2019 Week 17-19, 2019 Week 20-22, 2019 Week 23-25) > DM UX solutions for communicating errors in graphs & grids. > ------------------------------------------------------------ > > Key: DROOLS-3954 > URL: https://issues.jboss.org/browse/DROOLS-3954 > Project: Drools > Issue Type: Epic > Components: DMN Editor, Scenario Simulation and Testing > Reporter: Elizabeth Clayton > Assignee: Tao Zhu > Priority: Major > Labels: ScenarioSimulation, Stunner, UX, UXTeam, drools-tools > > Scenario and DMN editors share design solutions for displaying errors in graphs (models) and grids (scenario test, dmn boxed expressions.) Support design consistency where applicable, while also documenting unique solutions per context. > Current DM context specific "design pattern" document: https://docs.google.com/document/d/1fX9K_fDjEO4_wDLK9EDDb0OtEFir7S6nFH9cn... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3957) Make verifier panel use docks

by Kris Verlaenen (Jira)

[ https://issues.jboss.org/browse/DROOLS-3957?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-3957: ----------------------------------- Sprint: 2019 Week 17-19, 2019 Week 20-22, 2019 Week 23-25, 2019 Week 26-28 (was: 2019 Week 17-19, 2019 Week 20-22, 2019 Week 23-25) > Make verifier panel use docks > ----------------------------- > > Key: DROOLS-3957 > URL: https://issues.jboss.org/browse/DROOLS-3957 > Project: Drools > Issue Type: Enhancement > Components: Guided Decision Table Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > Pretty sure we had a ticket for this, but could not find it. Here it is. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3879) Create Submarine version of Scesim editor

by Kris Verlaenen (Jira)

[ https://issues.jboss.org/browse/DROOLS-3879?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-3879: ----------------------------------- Sprint: 2019 Week 17-19, 2019 Week 20-22, 2019 Week 23-25, 2019 Week 26-28 (was: 2019 Week 17-19, 2019 Week 20-22, 2019 Week 23-25) > Create Submarine version of Scesim editor > ----------------------------------------- > > Key: DROOLS-3879 > URL: https://issues.jboss.org/browse/DROOLS-3879 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > > Create the *Submarine* (standalone) version of scesim editor. > No Home Page, no Library, No preferences, no other editors. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1705) Audit remaining Class.forName in static factory methods

by Kris Verlaenen (Jira)

[ https://issues.jboss.org/browse/DROOLS-1705?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-1705: ----------------------------------- Sprint: 2019 Week 23-25, 2019 Week 26-28 (was: 2019 Week 23-25) > Audit remaining Class.forName in static factory methods > ------------------------------------------------------- > > Key: DROOLS-1705 > URL: https://issues.jboss.org/browse/DROOLS-1705 > Project: Drools > Issue Type: Task > Components: core engine > Reporter: Matteo Mortari > Assignee: Edoardo Vacchi > Priority: Minor > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3819) Rule Units 2.0: evaluate 7.x behavior and consider new design

by Kris Verlaenen (Jira)

[ https://issues.jboss.org/browse/DROOLS-3819?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-3819: ----------------------------------- Sprint: 2019 Week 23-25, 2019 Week 26-28 (was: 2019 Week 23-25) > Rule Units 2.0: evaluate 7.x behavior and consider new design > ------------------------------------------------------------- > > Key: DROOLS-3819 > URL: https://issues.jboss.org/browse/DROOLS-3819 > Project: Drools > Issue Type: Task > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: drools-core, submarine > Fix For: 8.0.0.Final > > > I have disabled generation of `unit()` API invocation on DRL compiler in order to make the Unit prototype work quickly. We are now assuming that 1 unit === 1 session, therefore some previous assumptions do not hold anymore. Previous assertions are therefore broken. It is also a good time to re-evaluate some previous considerations on how rule units are supposed to work (e.g. reconsider how guards work etc) > *Deliverable*: design document -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4067) Add before/afterNodeEvaluated to enable monitoring of engine performance

by Kris Verlaenen (Jira)

[ https://issues.jboss.org/browse/DROOLS-4067?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-4067: ----------------------------------- Sprint: 2019 Week 23-25, 2019 Week 26-28 (was: 2019 Week 23-25) > Add before/afterNodeEvaluated to enable monitoring of engine performance > ------------------------------------------------------------------------ > > Key: DROOLS-4067 > URL: https://issues.jboss.org/browse/DROOLS-4067 > Project: Drools > Issue Type: Enhancement > Components: core engine > Reporter: Mario Fusco > Assignee: Mario Fusco > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3923) (C)DI detection should be more reliable/standard for codegen

by Kris Verlaenen (Jira)

[ https://issues.jboss.org/browse/DROOLS-3923?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-3923: ----------------------------------- Sprint: 2019 Week 23-25, 2019 Week 26-28 (was: 2019 Week 23-25) > (C)DI detection should be more reliable/standard for codegen > ------------------------------------------------------------ > > Key: DROOLS-3923 > URL: https://issues.jboss.org/browse/DROOLS-3923 > Project: Drools > Issue Type: Bug > Reporter: Edoardo Vacchi > Assignee: Edoardo Vacchi > Priority: Major > Labels: drools-core, submarine > > we are currently doing {{ try { Class.forName("...ApplicationScoped") } }} which is > (1) pretty hackish (2) won't work in Maven because maven's ClassPath is not the same of the target application > We should rather use a config param or any better way to detect if we're going to use DI. Currently we have added a config param + "auto detect" using the technique above (in maven only the config param works) but auto-detect should be better. > Besides ApplicationScoped only work for CDI, while JSR-330 @Inject is independent from CDI so using ApplicationScoped as a signal is too limited. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 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 June 2019