June 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4219) Configure Kafka/Zookeper cluster on openshift

by Massimiliano Dessi (Jira)

Massimiliano Dessi created DROOLS-4219: ------------------------------------------ Summary: Configure Kafka/Zookeper cluster on openshift Key: DROOLS-4219 URL: https://issues.jboss.org/browse/DROOLS-4219 Project: Drools Issue Type: Task Reporter: Massimiliano Dessi Assignee: Massimiliano Dessi https://github.com/desmax74/openshift-handbook/commit/d33a128aaa7ca4b4eeb... https://github.com/desmax74/openshift-handbook/commit/9f8a78c07acf3e4c330... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4213) [DMN Designer] Search feature - Define search architectural approach

by Guilherme Gomes (Jira)

[ https://issues.jboss.org/browse/DROOLS-4213?page=com.atlassian.jira.plugi... ] Guilherme Gomes updated DROOLS-4213: ------------------------------------ Summary: [DMN Designer] Search feature - Define search architectural approach (was: [DMN Designer] Search feature - Validate search architectural approach) > [DMN Designer] Search feature - Define search architectural approach > -------------------------------------------------------------------- > > Key: DROOLS-4213 > URL: https://issues.jboss.org/browse/DROOLS-4213 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > > This JIRAs refers to the discussions for different implementation approaches that can be adopted for supporting GDT editor and DMN editor. > With this JIRA done, two initial implementations will be triggered: > - https://issues.jboss.org/browse/DROOLS-4212 (DMN graph PoC) > - https://issues.jboss.org/browse/DROOLS-4211 (GDT PoC) -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4545) Incomplete fix for WFCORE-4406

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFCORE-4545?page=com.atlassian.jira.plugi... ] Jeff Mesnil updated WFCORE-4545: -------------------------------- Fix Version/s: 9.0.2.Final 10.0.0.Beta1 > Incomplete fix for WFCORE-4406 > ------------------------------ > > Key: WFCORE-4545 > URL: https://issues.jboss.org/browse/WFCORE-4545 > Project: WildFly Core > Issue Type: Bug > Components: Build System > Affects Versions: 9.0.1.Final > Reporter: Brian Stansberry > Assignee: Jeff Mesnil > Priority: Major > Fix For: 9.0.2.Final, 10.0.0.Beta1 > > > The WFCORE-4406 fix did not cover a number of dependencies that were added during the development of WF Core 9. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4217) Test Scenario: corrupted scenario when user accepts error suggestion for collection

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-4217?page=com.atlassian.jira.plugi... ] Daniele Zonca moved RHDM-996 to DROOLS-4217: -------------------------------------------- Project: Drools (was: Red Hat Decision Manager) Key: DROOLS-4217 (was: RHDM-996) Workflow: GIT Pull Request workflow (was: CDW with docs v1) Docs QE Status: NEW Affects Build: (was: CR1) Fix Build: (was: CR2) QE Status: NEW > Test Scenario: corrupted scenario when user accepts error suggestion for collection > ----------------------------------------------------------------------------------- > > Key: DROOLS-4217 > URL: https://issues.jboss.org/browse/DROOLS-4217 > Project: Drools > Issue Type: Bug > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Blocker > Labels: ScenarioSimulation > > If a scenario fails with a wrong expect value on a collection the actual value suggested to accept is wrong and if accepted the scenario corrupts -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4216) Create runtime and testing version of kogito webapp

by Gabriele Cardosi (Jira)

Gabriele Cardosi created DROOLS-4216: ---------------------------------------- Summary: Create runtime and testing version of kogito webapp Key: DROOLS-4216 URL: https://issues.jboss.org/browse/DROOLS-4216 Project: Drools Issue Type: Sub-task Components: Scenario Simulation and Testing Reporter: Gabriele Cardosi Assignee: Gabriele Cardosi For each asset there should be two *kogito* webapp: # a **development/testing** one, that should provide **VS CODE** funtionalities, # a **runtime** one, without the above, to be used inside **VS CODE** -- 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 Gabriele Cardosi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3879?page=com.atlassian.jira.plugi... ] Gabriele Cardosi updated DROOLS-3879: ------------------------------------- Description: Create the *Kogito* (standalone) version of scesim editor. No Home Page, no Library, No preferences, no other editors. was: Create the *Submarine* (standalone) version of scesim editor. No Home Page, no Library, No preferences, no other editors. > 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 *Kogito* (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-3879) Create Kogito version of Scesim editor

by Gabriele Cardosi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3879?page=com.atlassian.jira.plugi... ] Gabriele Cardosi updated DROOLS-3879: ------------------------------------- Summary: Create Kogito version of Scesim editor (was: Create Submarine version of Scesim editor) > Create Kogito 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 *Kogito* (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-4195) [DMN Designer] PMML: Update Document value when Import alias changes

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-4195?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-4195: ----------------------------------- Description: When a PMML document is imported it is given an alias. When the PMML document is used in a {{Function}} the alias is used as the document name. When the import alias is changed {{Function}}'s referencing the old alias should be updated. *Acceptance tests* Document name updates in the following scenarios:- # (?) Top level {{Decision}} defined as a PMML {{FunctionDefinition}} # (?) Top level {{BusinessKnowledgeModel}} defined as a PMML {{FunctionDefinition}} # (?) {{Decision}} with nested PMML {{FunctionDefinition}} (i.e. within a {{Context}}) # (?) {{BKM}} with nested PMML {{FunctionDefinition}} (i.e. {{BKM}}s expression is a {{Context}} holding the PMML {{FunctionDefinition}}) Document name is not updated in the following scenarios:- # (?) Top level {{Decision}} defined as a FEEL {{Context}} with an {{InformationItem}} (variable) name "document" # (?) Top level {{BKM}} defined similarly to the foregoing {{Decision}} # (?) Nested variant for {{Decision}} # (?) Nested variant for {{BKM}} was: When a PMML document is imported it is given an alias. When the PMML document is used in a {{Function}} the alias is used as the document name. When the import alias is changed {{Function}}'s referencing the old alias should be updated. *Acceptance tests* Document name updates in the following scenarios:- # Top level {{Decision}} defined as a PMML {{FunctionDefinition}} # Top level {{BusinessKnowledgeModel}} defined as a PMML {{FunctionDefinition}} # {{Decision}} with nested PMML {{FunctionDefinition}} (i.e. within a {{Context}}) # {{BKM}} with nested PMML {{FunctionDefinition}} (i.e. {{BKM}}s expression is a {{Context}} holding the PMML {{FunctionDefinition}}) Document name is not updated in the following scenarios:- # Top level {{Decision}} defined as a FEEL {{Context}} with an {{InformationItem}} (variable) name "document" # Top level {{BKM}} defined similarly to the foregoing {{Decision}} # Nested variant for {{Decision}} # Nested variant for {{BKM}} > [DMN Designer] PMML: Update Document value when Import alias changes > -------------------------------------------------------------------- > > Key: DROOLS-4195 > URL: https://issues.jboss.org/browse/DROOLS-4195 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.24.0.Final > Reporter: Edson Tirelli > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > > When a PMML document is imported it is given an alias. > When the PMML document is used in a {{Function}} the alias is used as the document name. > When the import alias is changed {{Function}}'s referencing the old alias should be updated. > *Acceptance tests* > Document name updates in the following scenarios:- > # (?) Top level {{Decision}} defined as a PMML {{FunctionDefinition}} > # (?) Top level {{BusinessKnowledgeModel}} defined as a PMML {{FunctionDefinition}} > # (?) {{Decision}} with nested PMML {{FunctionDefinition}} (i.e. within a {{Context}}) > # (?) {{BKM}} with nested PMML {{FunctionDefinition}} (i.e. {{BKM}}s expression is a {{Context}} holding the PMML {{FunctionDefinition}}) > Document name is not updated in the following scenarios:- > # (?) Top level {{Decision}} defined as a FEEL {{Context}} with an {{InformationItem}} (variable) name "document" > # (?) Top level {{BKM}} defined similarly to the foregoing {{Decision}} > # (?) Nested variant for {{Decision}} > # (?) Nested variant for {{BKM}} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4195) [DMN Designer] PMML: Update Document value when Import alias changes

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-4195?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-4195: ----------------------------------- Description: When a PMML document is imported it is given an alias. When the PMML document is used in a {{Function}} the alias is used as the document name. When the import alias is changed {{Function}}'s referencing the old alias should be updated. *Acceptance tests* Document name updates in the following scenarios:- # Top level {{Decision}} defined as a PMML {{FunctionDefinition}} # Top level {{BusinessKnowledgeModel}} defined as a PMML {{FunctionDefinition}} # {{Decision}} with nested PMML {{FunctionDefinition}} (i.e. within a {{Context}}) # {{BKM}} with nested PMML {{FunctionDefinition}} (i.e. {{BKM}}s expression is a {{Context}} holding the PMML {{FunctionDefinition}}) Document name is not updated in the following scenarios:- # Top level {{Decision}} defined as a FEEL {{Context}} with an {{InformationItem}} (variable) name "document" # Top level {{BKM}} defined similarly to the foregoing {{Decision}} # Nested variant for {{Decision}} # Nested variant for {{BKM}} was: When a PMML document is imported it is given an alias. When the PMML document is used in a {{Function}} the alias is used as the document name. When the import alias is changed {{Function}}'s referencing the old alias should be updated. > [DMN Designer] PMML: Update Document value when Import alias changes > -------------------------------------------------------------------- > > Key: DROOLS-4195 > URL: https://issues.jboss.org/browse/DROOLS-4195 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.24.0.Final > Reporter: Edson Tirelli > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > > When a PMML document is imported it is given an alias. > When the PMML document is used in a {{Function}} the alias is used as the document name. > When the import alias is changed {{Function}}'s referencing the old alias should be updated. > *Acceptance tests* > Document name updates in the following scenarios:- > # Top level {{Decision}} defined as a PMML {{FunctionDefinition}} > # Top level {{BusinessKnowledgeModel}} defined as a PMML {{FunctionDefinition}} > # {{Decision}} with nested PMML {{FunctionDefinition}} (i.e. within a {{Context}}) > # {{BKM}} with nested PMML {{FunctionDefinition}} (i.e. {{BKM}}s expression is a {{Context}} holding the PMML {{FunctionDefinition}}) > Document name is not updated in the following scenarios:- > # Top level {{Decision}} defined as a FEEL {{Context}} with an {{InformationItem}} (variable) name "document" > # Top level {{BKM}} defined similarly to the foregoing {{Decision}} > # Nested variant for {{Decision}} > # Nested variant for {{BKM}} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4195) [DMN Designer] PMML: Update Document value when Import alias changes

by Kris Verlaenen (Jira)

[ https://issues.jboss.org/browse/DROOLS-4195?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-4195: ----------------------------------- Sprint: 2019 Week 23-25, 2019 Week 26-28 (was: 2019 Week 23-25) > [DMN Designer] PMML: Update Document value when Import alias changes > -------------------------------------------------------------------- > > Key: DROOLS-4195 > URL: https://issues.jboss.org/browse/DROOLS-4195 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.24.0.Final > Reporter: Edson Tirelli > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > > When a PMML document is imported it is given an alias. > When the PMML document is used in a {{Function}} the alias is used as the document name. > When the import alias is changed {{Function}}'s referencing the old alias should be updated. -- 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