July 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-1193) Kiali make target "dep-install" No Longer Supported in with PR 2951

by Matthew Mahoney (Jira)

[ https://issues.redhat.com/browse/SWSQE-1193?page=com.atlassian.jira.plugi... ] Matthew Mahoney updated SWSQE-1193: ----------------------------------- Description: With Kiali PR [2951|https://github.com/kiali/kiali/pull/2951], make target "dep-install" will no longer be supported. Thus. the Jenkins build job must change, otherwise all kili builds will fail. See @edgarhz for more details. was: With Kiali PR [2951|https://github.com/kiali/kiali/pull/2951], make target "dep-install" will no longer be supported. Thus. the Jenkins build job must change, otherwise all kili builds will fail. See @[ehernand@redhat.com|mailto:ehernand@redhat.com] for more details. > Kiali make target "dep-install" No Longer Supported in with PR 2951 > -------------------------------------------------------------------- > > Key: SWSQE-1193 > URL: https://issues.redhat.com/browse/SWSQE-1193 > Project: Kiali QE > Issue Type: QE Task > Reporter: Matthew Mahoney > Assignee: Filip Brychta > Priority: Major > Labels: infrastructure > > With Kiali PR [2951|https://github.com/kiali/kiali/pull/2951], make target "dep-install" will no longer be supported. Thus. the Jenkins build job must change, otherwise all kili builds will fail. > > See @edgarhz for more details. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (SWSQE-1193) Kiali make target "dep-install" No Longer Supported in with PR 2951

by Matthew Mahoney (Jira)

Matthew Mahoney created SWSQE-1193: -------------------------------------- Summary: Kiali make target "dep-install" No Longer Supported in with PR 2951 Key: SWSQE-1193 URL: https://issues.redhat.com/browse/SWSQE-1193 Project: Kiali QE Issue Type: QE Task Reporter: Matthew Mahoney Assignee: Filip Brychta With Kiali PR [2951|https://github.com/kiali/kiali/pull/2951], make target "dep-install" will no longer be supported. Thus. the Jenkins build job must change, otherwise all kili builds will fail. See @[ehernand@redhat.com|mailto:ehernand@redhat.com] for more details. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-5021) Upgrade jboss-logmanager to 2.1.17.Final

by Bartosz Spyrko-Smietanko (Jira)

[ https://issues.redhat.com/browse/WFCORE-5021?page=com.atlassian.jira.plug... ] Bartosz Spyrko-Smietanko updated WFCORE-5021: --------------------------------------------- Labels: downstream_dependency (was: ) > Upgrade jboss-logmanager to 2.1.17.Final > ---------------------------------------- > > Key: WFCORE-5021 > URL: https://issues.redhat.com/browse/WFCORE-5021 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Major > Labels: downstream_dependency > > Upgrade the jboss-logmanager from 2.1.16.Final to 2.1.17.Final > https://github.com/jboss-logging/jboss-logmanager/releases/tag/2.1.17.Final -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-5458) Running tests should not affect incremental build

by Jan Stastny (Jira)

[ https://issues.redhat.com/browse/DROOLS-5458?page=com.atlassian.jira.plug... ] Jan Stastny commented on DROOLS-5458: ------------------------------------- Checked that the issue happens also when Data Objects are provided in a separate JAR through Artifact Repository. > Running tests should not affect incremental build > ------------------------------------------------- > > Key: DROOLS-5458 > URL: https://issues.redhat.com/browse/DROOLS-5458 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.39.0.Final > Reporter: Jan Stastny > Assignee: Toni Rikkola > Priority: Blocker > Labels: drools-tools > Attachments: bpms_scesim-tickets.zip > > > For a Scenario Simulation that tests DRL rule and facts having an enum property a seemingly class-loading issue occurs in Business Central. > The ultimate error is in the DRL file validation: > {code:java|title=DRL file} > package org.jboss.qa.ba.scesim; > rule "child ticket" > when > t: Ticket ( type==TicketType.CHILD) > then > t.setPrice(5.0); > end > {code} > {code:java|title=Validation error} > [KBase: defaultKieBase]: Unable to Analyse Expression type == TicketType.CHILD: > [Error: Comparison operation requires compatible types. Found class org.jboss.qa.ba.scesim.TicketType and class org.jboss.qa.ba.scesim.TicketType] > [Near : {... type == TicketType.CHILD ....}] > ^ > {code} > The issue happens in given scenario: > # import project > # go to DRL file and run validation - succeeds > # go to scenario simulation and run - succeeds > # go back to DRL file and run validation - fails with the error above > # go to scenario simulation and run again - fails due to the rule not being evaluated for given facts > The issue disappears when running Build of the project in the Project perspective. > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-5442) [Guided Decision Table] Key navigation failure in Descision table

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-5442?page=com.atlassian.jira.plug... ] Jozef Marko commented on DROOLS-5442: ------------------------------------- Sent PR is in draft state as the component is general. Checking if tests of other repositories are not affected. Then tests for actual changes will be provided. > [Guided Decision Table] Key navigation failure in Descision table > ----------------------------------------------------------------- > > Key: DROOLS-5442 > URL: https://issues.redhat.com/browse/DROOLS-5442 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Affects Versions: 7.39.0.Final > Reporter: Anna Dupliak > Assignee: Jozef Marko > Priority: Major > Labels: decision_table, drools-tools > Attachments: arrow.webm, image-2020-06-18-15-04-15-605.png, image-2020-06-18-15-06-26-220.png > > > When user navigates among columns from Description to any other - he need to push right arrow key twice to skip a hidden column introduced recently for decision tables. > !image-2020-06-18-15-04-15-605.png|thumbnail! -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-5442) [Guided Decision Table] Key navigation failure in Descision table

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-5442?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-5442: -------------------------------- Tester: Jan Stastny (was: Jozef Marko) > [Guided Decision Table] Key navigation failure in Descision table > ----------------------------------------------------------------- > > Key: DROOLS-5442 > URL: https://issues.redhat.com/browse/DROOLS-5442 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Affects Versions: 7.39.0.Final > Reporter: Anna Dupliak > Assignee: Jozef Marko > Priority: Major > Labels: decision_table, drools-tools > Attachments: arrow.webm, image-2020-06-18-15-04-15-605.png, image-2020-06-18-15-06-26-220.png > > > When user navigates among columns from Description to any other - he need to push right arrow key twice to skip a hidden column introduced recently for decision tables. > !image-2020-06-18-15-04-15-605.png|thumbnail! -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-5465) [Guided Decision Table] Key navigation failure in Descision table

by Jozef Marko (Jira)

Jozef Marko created DROOLS-5465: ----------------------------------- Summary: [Guided Decision Table] Key navigation failure in Descision table Key: DROOLS-5465 URL: https://issues.redhat.com/browse/DROOLS-5465 Project: Drools Issue Type: Bug Components: Guided Decision Table Editor Affects Versions: 7.39.0.Final Reporter: Jozef Marko Assignee: Jozef Marko Attachments: arrow.webm, image-2020-06-18-15-04-15-605.png, image-2020-06-18-15-06-26-220.png When user navigates among columns from Description to any other - he need to push right arrow key twice to skip a hidden column introduced recently for decision tables. !image-2020-06-18-15-04-15-605.png|thumbnail! -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-5442) [Guided Decision Table] Key navigation failure in Descision table

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-5442?page=com.atlassian.jira.plug... ] Jozef Marko reassigned DROOLS-5442: ----------------------------------- Assignee: Jozef Marko (was: Toni Rikkola) > [Guided Decision Table] Key navigation failure in Descision table > ----------------------------------------------------------------- > > Key: DROOLS-5442 > URL: https://issues.redhat.com/browse/DROOLS-5442 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Affects Versions: 7.39.0.Final > Reporter: Anna Dupliak > Assignee: Jozef Marko > Priority: Major > Labels: decision_table, drools-tools > Attachments: arrow.webm, image-2020-06-18-15-04-15-605.png, image-2020-06-18-15-06-26-220.png > > > When user navigates among columns from Description to any other - he need to push right arrow key twice to skip a hidden column introduced recently for decision tables. > !image-2020-06-18-15-04-15-605.png|thumbnail! -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-5272) Re-evaluate/refactor KiePMML AST factories

by Gabriele Cardosi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5272?page=com.atlassian.jira.plug... ] Gabriele Cardosi updated DROOLS-5272: ------------------------------------- Description: Re-evaluate implementation of KiePMML AST factories in the view of the mining model specifications. Reevaluate usage of fieldTypeMap - types. E.g.: inside DroolsModelProvider.getKiePMMLDroolsASTCommon the Map<String, KiePMMLOriginalTypeGeneratedType> fieldTypeMap is populated invoking addTransformationsDerivedFields. Then, a List<KiePMMLDroolsType> is created out of this map. Later the same map is also populated by KiePMMLDataDictionaryASTFactory.factory(fieldTypeMap).declareTypes(dataDictionary). and the List<KiePMMLDroolsType> retrieved by the latter are added to the one created before. That means it is not needed to have KiePMMLDerivedFieldASTFactory and KiePMMLDataDictionaryASTFactory returning List<KiePMMLDroolsType> - they can simply instantiate and return a Map<String, KiePMMLOriginalTypeGeneratedType>; the maps may be merged together, and the List<KiePMMLDroolsType> may be created out of that (merged) map. So 1) KiePMMLDataDictionaryASTFactory and KiePMMLDerivedFieldASTFactory should return only a newly instantiated Map<String, KiePMMLOriginalTypeGeneratedType> 2) inside DroolsModelProvider.getKiePMMLDroolsASTCommon those maps should be merged 3) List<KiePMMLDroolsType> should be created out of the merged map 4) merged map and List<KiePMMLDroolsType> should be propagated as parameters was:Re-evaluate implementation of KiePMML AST factories in the view of the mining model specifications. > Re-evaluate/refactor KiePMML AST factories > ------------------------------------------ > > Key: DROOLS-5272 > URL: https://issues.redhat.com/browse/DROOLS-5272 > Project: Drools > Issue Type: Task > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > Labels: TrustyAI > > Re-evaluate implementation of KiePMML AST factories in the view of the mining model specifications. > Reevaluate usage of fieldTypeMap - types. > > E.g.: inside > DroolsModelProvider.getKiePMMLDroolsASTCommon the > Map<String, KiePMMLOriginalTypeGeneratedType> fieldTypeMap is populated invoking > addTransformationsDerivedFields. Then, a List<KiePMMLDroolsType> is created out of this map. > Later the same map is also populated by > KiePMMLDataDictionaryASTFactory.factory(fieldTypeMap).declareTypes(dataDictionary). > and the List<KiePMMLDroolsType> retrieved by the latter are added to the one created before. > That means it is not needed to have KiePMMLDerivedFieldASTFactory and KiePMMLDataDictionaryASTFactory returning List<KiePMMLDroolsType> - they can simply instantiate and return a Map<String, KiePMMLOriginalTypeGeneratedType>; the maps may be merged together, and the List<KiePMMLDroolsType> may be created out of that (merged) map. > So > 1) KiePMMLDataDictionaryASTFactory and KiePMMLDerivedFieldASTFactory should return only a newly instantiated Map<String, KiePMMLOriginalTypeGeneratedType> > 2) inside DroolsModelProvider.getKiePMMLDroolsASTCommon those maps should be merged > 3) List<KiePMMLDroolsType> should be created out of the merged map > 4) merged map and List<KiePMMLDroolsType> should be propagated as parameters -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-5464) Declare kie-pmml-dependencies management

by Gabriele Cardosi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5464?page=com.atlassian.jira.plug... ] Gabriele Cardosi closed DROOLS-5464. ------------------------------------ > Declare kie-pmml-dependencies management > ---------------------------------------- > > Key: DROOLS-5464 > URL: https://issues.redhat.com/browse/DROOLS-5464 > Project: Drools > Issue Type: Feature Request > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > Labels: TrustyAI > > Declare kie-pmml-dependencies version inside kie-parent dependencyManagement -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

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