January 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4994) Highlight better that expression and graphical collection editor are different

by Anna Dupliak (Jira)

[ https://issues.redhat.com/browse/DROOLS-4994?page=com.atlassian.jira.plug... ] Anna Dupliak updated DROOLS-4994: --------------------------------- Labels: drools-tools (was: BusinessCentral) > Highlight better that expression and graphical collection editor are different > ------------------------------------------------------------------------------ > > Key: DROOLS-4994 > URL: https://issues.redhat.com/browse/DROOLS-4994 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Affects Versions: 7.32.0.Final > Reporter: Anna Dupliak > Assignee: Yeser Amer > Priority: Minor > Labels: drools-tools > Attachments: Screenshot from 2020-01-17 13-56-02.png, Screenshot from 2020-01-17 13-56-10.png > > > Revealed during testing of https://issues.redhat.com/browse/DROOLS-4698 > We need a way to tell a user that using the guided editor, you can only add one ore more check to the collection as list of conditions while in the expression user can write whatever he wants so the semantic is completely custom. > Suggested solution: > - to explain the difference directly in the popup, somewhere close to radio buttons create/define. > Example: > How that works: > Each element defined in the graphical editor will be considered as a check to perform: the first screenshot means "check if an element equals to 2 exists in the collection" while the expression means "is the list equals to [2] list?" -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4972) Buttons stay disabled when switching to textual collection editor

by Elizabeth Clayton (Jira)

[ https://issues.redhat.com/browse/DROOLS-4972?page=com.atlassian.jira.plug... ] Elizabeth Clayton commented on DROOLS-4972: ------------------------------------------- Sounds good [~yamer], thank you! > Buttons stay disabled when switching to textual collection editor > ----------------------------------------------------------------- > > Key: DROOLS-4972 > URL: https://issues.redhat.com/browse/DROOLS-4972 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.32.0.Final > Reporter: Jozef Marko > Assignee: Yeser Amer > Priority: Minor > Labels: drools-tools > Attachments: Screen Shot 2020-01-30 at 1.24.18 PM.png, define-list-and-save.webm > > > If user starts to create list using UI editor, then he decides to switch to textual editor - define list as expression, the buttons are disabled if user didn't canceled items 'in progress' in the UI editor. See the attached video. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4993) [DMN Designer] Code Completion - add keywords

by Donato Marrazzo (Jira)

Donato Marrazzo created DROOLS-4993: --------------------------------------- Summary: [DMN Designer] Code Completion - add keywords Key: DROOLS-4993 URL: https://issues.redhat.com/browse/DROOLS-4993 Project: Drools Issue Type: Feature Request Components: DMN Editor Reporter: Donato Marrazzo Assignee: Guilherme Gomes Manage FEEL expression keywords: * in * or * and * between * if ... then ... else ... * for ... in ... return ... -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-255) Boot time only system properties should not modify the runtime only the model

by Bartosz Spyrko (Jira)

[ https://issues.redhat.com/browse/WFCORE-255?page=com.atlassian.jira.plugi... ] Bartosz Spyrko updated WFCORE-255: ---------------------------------- Labels: domain-mode downstream_dependency (was: domain-mode) > Boot time only system properties should not modify the runtime only the model > ----------------------------------------------------------------------------- > > Key: WFCORE-255 > URL: https://issues.redhat.com/browse/WFCORE-255 > Project: WildFly Core > Issue Type: Bug > Components: Management > Reporter: James Perkins > Assignee: James Perkins > Priority: Major > Labels: domain-mode, downstream_dependency > > The three properties {{jboss.server.base.dir}}, {{jboss.server.config.dir}} and {{jboss.server.log.dir}} are allowed to be overridden for servers. For a domain server, these values need to be allowed to be set as a {{boot-time=true}} system property. > These properties should also be allowed to be set as a system-property resource or overridden via {{JAVA_OPTS}} or the {{launch-command}}. > The {{add}}, {{write-attribute}} and {{remove}} operations should not modify the runtime, but should modify the model. It's debatable whether the server should be put in a {{restart-required}} state. Currently similar resources do _not_ set the server state to {{restart-required}}. For now we should stick with the same state. > {code} > [domain@localhost:9999 /] /host=master/system-property=jboss.server.log.dir:add(boot-time=true,value="/var/log") > { > "outcome" => "failed", > "result" => undefined, > "failure-description" => "JBAS010839: Operation failed or was rolled back on all servers.", > "rolled-back" => true, > "server-groups" => {"main-server-group" => {"host" => {"master" => { > "server-one" => {"response" => { > "outcome" => "failed", > "failure-description" => "JBAS015845: System property jboss.server.log.dir cannot be set via the xml configuration file or from a management client; it's value must be known at initial process start so it can only set from the commmand line", > > "rolled-back" => true > }}, > "server-two" => {"response" => { > "outcome" => "failed", > "failure-description" => "JBAS015845: System property jboss.server.log.dir cannot be set via the xml configuration file or from a management client; it's value must be known at initial process start so it can only set from the commmand line", > "rolled-back" => true > }} > }}}} > } > {code} > These properties should also be allowed to be set in the {{/host=\*/server-config=\*/jvm=\*/}} resource on the {{jvm-options}} and likely {{launch-command}} attributes. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4822) Upgrade Management API Version to 12.0

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFCORE-4822?page=com.atlassian.jira.plug... ] Darran Lofthouse commented on WFCORE-4822: ------------------------------------------ I have had some similar cases where I have not been 100% sure CI ran with the commit I wanted it to. I know CI has been cut back regarding how much it comments on PRs but it may be useful to log the details of the merge commit under test to verify the two SHAs. > Upgrade Management API Version to 12.0 > -------------------------------------- > > Key: WFCORE-4822 > URL: https://issues.redhat.com/browse/WFCORE-4822 > Project: WildFly Core > Issue Type: Bug > Components: Management > Reporter: Jeff Mesnil > Assignee: Yeray Borges > Priority: Blocker > Fix For: 11.0.0.Beta8 > > > We need to fix the version state before WildFly 19 is released. > * The KernelAPIVersion must be bumped to 12.0 > * We also need to release wildly-config-12.0.xsd with the proper host-exclude for > * WildFlY18, Version.10 > * EAP73, Version.10 > (and add those to KnownRelease too) -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4992) Buildtime benchmark regression

by Tibor Zimanyi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4992?page=com.atlassian.jira.plug... ] Tibor Zimanyi deleted DROOLS-4992: ---------------------------------- > Buildtime benchmark regression > ------------------------------ > > Key: DROOLS-4992 > URL: https://issues.redhat.com/browse/DROOLS-4992 > Project: Drools > Issue Type: Bug > Reporter: Daniel Rosa > Assignee: Daniel Rosa > Priority: Major > > The experimental nightly benchmark dashboard has shown a performance loss 46.01% on the org.drools.benchmarks.buildtime.BuildKJarFromResourceBenchmark.createKJarFromResource benchmark after the merge to the master. It is probably due the change to default to executable model in the kie-maven-plugin issue (DROOLS-4092). -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4992) Buildtime benchmark regression

by Daniel Rosa (Jira)

[ https://issues.redhat.com/browse/DROOLS-4992?page=com.atlassian.jira.plug... ] Daniel Rosa commented on DROOLS-4992: ------------------------------------- Since the new default is use executable model, we need to set the old behaviour as an argument to the buildAll function. > Buildtime benchmark regression > ------------------------------ > > Key: DROOLS-4992 > URL: https://issues.redhat.com/browse/DROOLS-4992 > Project: Drools > Issue Type: Bug > Reporter: Daniel Rosa > Assignee: Daniel Rosa > Priority: Major > Attachments: nightly_regression.png > > > The experimental nightly benchmark dashboard has shown a performance loss 46.01% on the org.drools.benchmarks.buildtime.BuildKJarFromResourceBenchmark.createKJarFromResource benchmark after the merge to the master. It is probably due the change to default to executable model in the kie-maven-plugin issue (DROOLS-4092). -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4992) Buildtime benchmark regression

by Daniel Rosa (Jira)

Daniel Rosa created DROOLS-4992: ----------------------------------- Summary: Buildtime benchmark regression Key: DROOLS-4992 URL: https://issues.redhat.com/browse/DROOLS-4992 Project: Drools Issue Type: Bug Reporter: Daniel Rosa Assignee: Daniel Rosa Attachments: nightly_regression.png The experimental nightly benchmark dashboard has shown a performance loss 46.01% on the org.drools.benchmarks.buildtime.BuildKJarFromResourceBenchmark.createKJarFromResource benchmark after the merge to the master. It is probably due the change to default to executable model in the kie-maven-plugin issue (DROOLS-4092). -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4822) Upgrade Management API Version to 12.0

by Yeray Borges (Jira)

[ https://issues.redhat.com/browse/WFCORE-4822?page=com.atlassian.jira.plug... ] Yeray Borges reopened WFCORE-4822: ---------------------------------- [~jmesnil] It looks like CI took the wrong commit, I just rebased and I am getting a checkstyle error on StandaloneXml_11 I reopen the issue to fix it up. > Upgrade Management API Version to 12.0 > -------------------------------------- > > Key: WFCORE-4822 > URL: https://issues.redhat.com/browse/WFCORE-4822 > Project: WildFly Core > Issue Type: Bug > Components: Management > Reporter: Jeff Mesnil > Assignee: Yeray Borges > Priority: Blocker > Fix For: 11.0.0.Beta8 > > > We need to fix the version state before WildFly 19 is released. > * The KernelAPIVersion must be bumped to 12.0 > * We also need to release wildly-config-12.0.xsd with the proper host-exclude for > * WildFlY18, Version.10 > * EAP73, Version.10 > (and add those to KnownRelease too) -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12093) bug in tutorial "batch-processing" with column "End Time"

by Eduardo Martins (Jira)

[ https://issues.redhat.com/browse/WFLY-12093?page=com.atlassian.jira.plugi... ] Eduardo Martins commented on WFLY-12093: ---------------------------------------- [~parsharma] not working on it, please reassign to you if you want [~jamezp] is this issue valid? > bug in tutorial "batch-processing" with column "End Time" > --------------------------------------------------------- > > Key: WFLY-12093 > URL: https://issues.redhat.com/browse/WFLY-12093 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Environment: batch-processing > Reporter: Святослав Кремлёв > Assignee: Eduardo Martins > Priority: Major > Attachments: 2019-05-18 23_16_51-Batch Processing.png > > > in file > org/jboss/as/quickstarts/batch/controller/JobData.java > {code} > public Date getEndTime() { > endTime = new Date(); > return endTime.getTime() == 0 ? null : endTime; > } > {code} > its returns current time every time, not the job endTime -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 3 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 January 2020