October 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4574) Scenario test: UX to add an expression-based value.

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-4574?page=com.atlassian.jira.plugi... ] Elizabeth Clayton commented on DROOLS-4574: ------------------------------------------- Note: I made the checkboxes in the list row static images, because [~danielezonca] let me know that true checkbox selection is out of scope for the near-term. > Scenario test: UX to add an expression-based value. > ---------------------------------------------------- > > Key: DROOLS-4574 > URL: https://issues.jboss.org/browse/DROOLS-4574 > Project: Drools > Issue Type: Story > Components: Scenario Simulation and Testing > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam > Attachments: Screen Shot 2019-10-01 at 8.27.30 AM.png, long_value.gif > > > As a technical/advanced user (Cameron), I want to be able to input expression-based values in scenario given/expect row cells, so that I can define inputs for complex objects and logic. > Note: Syntax highlighting and etc., are out of scope. Refer to: https://issues.jboss.org/browse/DROOLS-3514 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4602) kie-maven-plugin fails with nested kbases and dependency versions declared in bom

by Martin Weiler (Jira)

[ https://issues.jboss.org/browse/DROOLS-4602?page=com.atlassian.jira.plugi... ] Martin Weiler updated DROOLS-4602: ---------------------------------- Attachment: hierarchical-kbase-bom.zip > kie-maven-plugin fails with nested kbases and dependency versions declared in bom > --------------------------------------------------------------------------------- > > Key: DROOLS-4602 > URL: https://issues.jboss.org/browse/DROOLS-4602 > Project: Drools > Issue Type: Bug > Components: tools > Affects Versions: 7.27.0.Final > Reporter: Martin Weiler > Assignee: Mario Fusco > Priority: Major > Labels: support > Attachments: hierarchical-kbase-bom.zip > > > When we build 2 kjars and one kbase "includes" another, kie-maven-plugin fails to resolve the sub kbase if the dependency version is declared in a common bom: > {noformat} > Running test with rules version 7.23.0.Final-redhat-00003 and -DgenerateModel=NO > 12:41:58,315 [ERROR] Unable to build KieBase, could not find include: subkbase > 12:41:58,320 [ERROR] Failed to execute goal org.kie:kie-maven-plugin:7.23.0.Final-redhat-00003:build (default-build) on project kbase-parent: Execution default-build of goal org.kie:kie-maven-plugin:7.23.0.Final-redhat-00003:build failed: Unable to get KieModule, Errors Existed: Error Messages: > 12:41:58,323 [ERROR] Message [id=1, kieBase=parentkbase, level=ERROR, path=src/main/resources/META-INF/kmodule.xml, line=0, column=0 > 12:41:58,324 [ERROR] text=Unable to build KieBase, could not find include: subkbase] > {noformat} > Note that such a build is successful with RHDM 7.3.1 if the executable model is *not* used (see reproducer). -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4602) kie-maven-plugin fails with nested kbases and dependency versions declared in bom

by Martin Weiler (Jira)

[ https://issues.jboss.org/browse/DROOLS-4602?page=com.atlassian.jira.plugi... ] Martin Weiler updated DROOLS-4602: ---------------------------------- Description: When we build 2 kjars and one kbase "includes" another, kie-maven-plugin fails to resolve the sub kbase if the dependency version is declared in a common bom: {noformat} Running test with rules version 7.27.0.Final and -DgenerateModel=NO 13:01:05,903 [ERROR] Unable to build KieBase, could not find include: subkbase 13:01:05,908 [ERROR] Failed to execute goal org.kie:kie-maven-plugin:7.27.0.Final:build (default-build) on project kbase-parent: Execution default-build of goal org.kie:kie-maven-plugin:7.27.0.Final:build failed: Unable to get KieModule, Errors Existed: Error Messages: 13:01:05,910 [ERROR] Message [id=1, kieBase=parentkbase, level=ERROR, path=src/main/resources/META-INF/kmodule.xml, line=0, column=0 13:01:05,911 [ERROR] text=Unable to build KieBase, could not find include: subkbase] {noformat} Note that such a build is successful with RHDM 7.3.1 if the executable model is *not* used (see reproducer). was: When we build 2 kjars and one kbase "includes" another, kie-maven-plugin fails to resolve the sub kbase if the dependency version is declared in a common bom: {noformat} Running test with rules version 7.23.0.Final-redhat-00003 and -DgenerateModel=NO 12:41:58,315 [ERROR] Unable to build KieBase, could not find include: subkbase 12:41:58,320 [ERROR] Failed to execute goal org.kie:kie-maven-plugin:7.23.0.Final-redhat-00003:build (default-build) on project kbase-parent: Execution default-build of goal org.kie:kie-maven-plugin:7.23.0.Final-redhat-00003:build failed: Unable to get KieModule, Errors Existed: Error Messages: 12:41:58,323 [ERROR] Message [id=1, kieBase=parentkbase, level=ERROR, path=src/main/resources/META-INF/kmodule.xml, line=0, column=0 12:41:58,324 [ERROR] text=Unable to build KieBase, could not find include: subkbase] {noformat} Note that such a build is successful with RHDM 7.3.1 if the executable model is *not* used (see reproducer). > kie-maven-plugin fails with nested kbases and dependency versions declared in bom > --------------------------------------------------------------------------------- > > Key: DROOLS-4602 > URL: https://issues.jboss.org/browse/DROOLS-4602 > Project: Drools > Issue Type: Bug > Components: tools > Affects Versions: 7.27.0.Final > Reporter: Martin Weiler > Assignee: Mario Fusco > Priority: Major > Labels: support > Attachments: hierarchical-kbase-bom.zip > > > When we build 2 kjars and one kbase "includes" another, kie-maven-plugin fails to resolve the sub kbase if the dependency version is declared in a common bom: > {noformat} > Running test with rules version 7.27.0.Final and -DgenerateModel=NO > 13:01:05,903 [ERROR] Unable to build KieBase, could not find include: subkbase > 13:01:05,908 [ERROR] Failed to execute goal org.kie:kie-maven-plugin:7.27.0.Final:build (default-build) on project kbase-parent: Execution default-build of goal org.kie:kie-maven-plugin:7.27.0.Final:build failed: Unable to get KieModule, Errors Existed: Error Messages: > 13:01:05,910 [ERROR] Message [id=1, kieBase=parentkbase, level=ERROR, path=src/main/resources/META-INF/kmodule.xml, line=0, column=0 > 13:01:05,911 [ERROR] text=Unable to build KieBase, could not find include: subkbase] > {noformat} > Note that such a build is successful with RHDM 7.3.1 if the executable model is *not* used (see reproducer). -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4602) kie-maven-plugin fails with nested kbases and dependency versions declared in bom

by Martin Weiler (Jira)

[ https://issues.jboss.org/browse/DROOLS-4602?page=com.atlassian.jira.plugi... ] Martin Weiler moved RHDM-1108 to DROOLS-4602: --------------------------------------------- Project: Drools (was: Red Hat Decision Manager) Key: DROOLS-4602 (was: RHDM-1108) Workflow: GIT Pull Request workflow (was: CDW with docs v1) Docs QE Status: NEW Component/s: tools (was: BRE) Affects Version/s: 7.27.0.Final (was: 7.4.1.GA) QE Status: NEW > kie-maven-plugin fails with nested kbases and dependency versions declared in bom > --------------------------------------------------------------------------------- > > Key: DROOLS-4602 > URL: https://issues.jboss.org/browse/DROOLS-4602 > Project: Drools > Issue Type: Bug > Components: tools > Affects Versions: 7.27.0.Final > Reporter: Martin Weiler > Assignee: Mario Fusco > Priority: Major > Labels: support > > When we build 2 kjars and one kbase "includes" another, kie-maven-plugin fails to resolve the sub kbase if the dependency version is declared in a common bom: > {noformat} > Running test with rules version 7.23.0.Final-redhat-00003 and -DgenerateModel=NO > 12:41:58,315 [ERROR] Unable to build KieBase, could not find include: subkbase > 12:41:58,320 [ERROR] Failed to execute goal org.kie:kie-maven-plugin:7.23.0.Final-redhat-00003:build (default-build) on project kbase-parent: Execution default-build of goal org.kie:kie-maven-plugin:7.23.0.Final-redhat-00003:build failed: Unable to get KieModule, Errors Existed: Error Messages: > 12:41:58,323 [ERROR] Message [id=1, kieBase=parentkbase, level=ERROR, path=src/main/resources/META-INF/kmodule.xml, line=0, column=0 > 12:41:58,324 [ERROR] text=Unable to build KieBase, could not find include: subkbase] > {noformat} > Note that such a build is successful with RHDM 7.3.1 if the executable model is *not* used (see reproducer). -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4574) Scenario test: UX to add an expression-based value.

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-4574?page=com.atlassian.jira.plugi... ] Elizabeth Clayton updated DROOLS-4574: -------------------------------------- Attachment: long_value.gif > Scenario test: UX to add an expression-based value. > ---------------------------------------------------- > > Key: DROOLS-4574 > URL: https://issues.jboss.org/browse/DROOLS-4574 > Project: Drools > Issue Type: Story > Components: Scenario Simulation and Testing > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam > Attachments: Screen Shot 2019-10-01 at 8.27.30 AM.png, long_value.gif > > > As a technical/advanced user (Cameron), I want to be able to input expression-based values in scenario given/expect row cells, so that I can define inputs for complex objects and logic. > Note: Syntax highlighting and etc., are out of scope. Refer to: https://issues.jboss.org/browse/DROOLS-3514 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4574) Scenario test: UX to add an expression-based value.

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-4574?page=com.atlassian.jira.plugi... ] Elizabeth Clayton commented on DROOLS-4574: ------------------------------------------- [~danielezonca] [~tirelli] [~ibek] I updated the click-thru (see Marvel attachment) to include input for long values, and have attached a video example as well. The design proposal is ready for review, thanks! * Marvel: https://marvelapp.com/5ab248j * Example of long value input !long_value.gif! > Scenario test: UX to add an expression-based value. > ---------------------------------------------------- > > Key: DROOLS-4574 > URL: https://issues.jboss.org/browse/DROOLS-4574 > Project: Drools > Issue Type: Story > Components: Scenario Simulation and Testing > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam > Attachments: Screen Shot 2019-10-01 at 8.27.30 AM.png, long_value.gif > > > As a technical/advanced user (Cameron), I want to be able to input expression-based values in scenario given/expect row cells, so that I can define inputs for complex objects and logic. > Note: Syntax highlighting and etc., are out of scope. Refer to: https://issues.jboss.org/browse/DROOLS-3514 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4601) Escape characters added to code after editing comma separated list in guided rule editor

by Toni Rikkola (Jira)

Toni Rikkola created DROOLS-4601: ------------------------------------ Summary: Escape characters added to code after editing comma separated list in guided rule editor Key: DROOLS-4601 URL: https://issues.jboss.org/browse/DROOLS-4601 Project: Drools Issue Type: Bug Components: Guided Rule Editor Reporter: Toni Rikkola Assignee: Toni Rikkola -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4601) Escape characters added to code after editing comma separated list in guided rule editor

by Toni Rikkola (Jira)

[ https://issues.jboss.org/browse/DROOLS-4601?page=com.atlassian.jira.plugi... ] Toni Rikkola updated DROOLS-4601: --------------------------------- Description: In guided rules, if you create a rule with a comma separated list, quotes are automatically added to the text box when saving the rule. If you then need to edit the values, quotes are again added, which results in escape characters in the source code making the rule no longer work > Escape characters added to code after editing comma separated list in guided rule editor > ---------------------------------------------------------------------------------------- > > Key: DROOLS-4601 > URL: https://issues.jboss.org/browse/DROOLS-4601 > Project: Drools > Issue Type: Bug > Components: Guided Rule Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > > In guided rules, if you create a rule with a comma separated list, quotes are automatically added to the text box when saving the rule. If you then need to edit the values, quotes are again added, which results in escape characters in the source code making the rule no longer work -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-4574) Scenario test: UX to add an expression-based value.

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-4574?page=com.atlassian.jira.plugi... ] Elizabeth Clayton commented on DROOLS-4574: ------------------------------------------- [~danielezonca] [~gabriolo] [~ibek] I posted a click-thru proposal, here are the key features: * Any scenario cell can support an expression based value, if the user starts the value declaration with the appropriate symbol (tbd). I used # in my examples. * A statement column may be set to accept complex expressions that reference any field in the Data Object. To set the column in this way the user needs to select the parent Data Object for that column, which will declare the property value as "expression." - If the column is set as an expression, each cell in that column will include the symbol to set the expression by default, as this is a required format for the whole column. The symbol will be present both as hint text and will pre-populate the editable field view. If the user backs it out, the system will add it back in. - To support List, I maintained the current interaction using the dialog. I added a radio set input selection to toggle between either Create a list using the guided experience, or to Define an expression. I believe this current mock covers all of the Required elements, but I will be updating it to also include a minimal solution for inputting long values, as discussed with [~danielezonca] > Scenario test: UX to add an expression-based value. > ---------------------------------------------------- > > Key: DROOLS-4574 > URL: https://issues.jboss.org/browse/DROOLS-4574 > Project: Drools > Issue Type: Story > Components: Scenario Simulation and Testing > Reporter: Elizabeth Clayton > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam > Attachments: Screen Shot 2019-10-01 at 8.27.30 AM.png > > > As a technical/advanced user (Cameron), I want to be able to input expression-based values in scenario given/expect row cells, so that I can define inputs for complex objects and logic. > Note: Syntax highlighting and etc., are out of scope. Refer to: https://issues.jboss.org/browse/DROOLS-3514 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (JGRP-2389) Message from a non-member causes FD_ALL to continually suspect it

by Pedro Zapata Fernandez (Jira)

Pedro Zapata Fernandez created JGRP-2389: -------------------------------------------- Summary: Message from a non-member causes FD_ALL to continually suspect it Key: JGRP-2389 URL: https://issues.jboss.org/browse/JGRP-2389 Project: JGroups Issue Type: Bug Affects Versions: 4.0.1 Reporter: Pedro Zapata Fernandez Assignee: Bela Ban Fix For: 4.1.6 If an FD_ALL control message from a non-member is seen by FD_ALL, it will start continually suspecting that node. If msg_counts_as_heartbeat=true then any message from a non-member triggers the issue. The issue is cleared on the next view change. This does not cause any functional issues in the cluster, but can cause repeated WARN logs in some cases. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

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 October 2019