February 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-12864) Update CodeReady Studio correct name in Quickstarts docs

by Ranabir Chakraborty (Jira)

[ https://issues.redhat.com/browse/WFLY-12864?page=com.atlassian.jira.plugi... ] Ranabir Chakraborty reassigned WFLY-12864: ------------------------------------------ Assignee: Ranabir Chakraborty (was: Eduardo Martins) > Update CodeReady Studio correct name in Quickstarts docs > -------------------------------------------------------- > > Key: WFLY-12864 > URL: https://issues.redhat.com/browse/WFLY-12864 > Project: WildFly > Issue Type: Task > Components: Quickstarts > Affects Versions: 18.0.0.Final > Reporter: Josef Kopriva > Assignee: Ranabir Chakraborty > Priority: Major > > Red Hat Developer Studio has been renamed to Red Hat CodeReady Studio(https://developers.redhat.com/products/codeready-studio/overview) some time ago, but in readme is still old name: > https://github.com/wildfly/quickstart/blob/master/README.adoc#7-run-the-q... > Please update this in all related docs. > Could be confusing for some customers. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5025) Wrong BitMask created by c

by Toshiya Kobayashi (Jira)

Toshiya Kobayashi created DROOLS-5025: ----------------------------------------- Summary: Wrong BitMask created by c Key: DROOLS-5025 URL: https://issues.redhat.com/browse/DROOLS-5025 Project: Drools Issue Type: Bug Components: executable model Affects Versions: 7.32.0.Final Reporter: Toshiya Kobayashi Assignee: Luca Molteni With a complex setter argument in modify block like this: {noformat} import org.drools.modelcompiler.domain.Person; rule R when $p: Person(address.street == "street1") then modify($p) { setLikes( String.valueOf(($p.getAddress().getStreet() + $p.getAddress().getCity()))) }; end {noformat} executable model creates BitMask for "likes" and "address" thus causes a wrong property reactivity behavior. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5024) DMN infra b/c TCK Jan edition

by Matteo Mortari (Jira)

Matteo Mortari created DROOLS-5024: -------------------------------------- Summary: DMN infra b/c TCK Jan edition Key: DROOLS-5024 URL: https://issues.redhat.com/browse/DROOLS-5024 Project: Drools Issue Type: Enhancement Components: dmn engine Reporter: Matteo Mortari Assignee: Matteo Mortari -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4942) DMN DT Analysis hit policy recommender

by Matteo Mortari (Jira)

[ https://issues.redhat.com/browse/DROOLS-4942?page=com.atlassian.jira.plug... ] Matteo Mortari updated DROOLS-4942: ----------------------------------- Description: Implement an heuristic for hit policy recommendation when dealing with single hit policies. If there are Gaps, no recommendations. If No Gaps and no Overlaps: recommend UNIQUE where possible. If No Gaps , but Overlaps with same output: recommend ANY If No Gaps , but Overlaps with different output: recommend PRIORITY where possible > DMN DT Analysis hit policy recommender > -------------------------------------- > > Key: DROOLS-4942 > URL: https://issues.redhat.com/browse/DROOLS-4942 > Project: Drools > Issue Type: Feature Request > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > > Implement an heuristic for hit policy recommendation when dealing with single hit policies. > If there are Gaps, no recommendations. > If No Gaps and no Overlaps: recommend UNIQUE where possible. > If No Gaps , but Overlaps with same output: recommend ANY > If No Gaps , but Overlaps with different output: recommend PRIORITY where possible -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2450) Enable fibers / project Loom

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2450?page=com.atlassian.jira.plugin... ] Bela Ban resolved JGRP-2450. ---------------------------- Resolution: Done > Enable fibers / project Loom > ---------------------------- > > Key: JGRP-2450 > URL: https://issues.redhat.com/browse/JGRP-2450 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 5.0 > > > Add {{use_fibers}} to {{TP}}. > When enabled, we use reflection to create fibers rather than threads in {{DefaultThreadFactory}}. > This requires Java 15/Loom. If not found, regular threads are returned instead. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2450) Enable fibers / project Loom

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2450?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-2450: --------------------------- Summary: Enable fibers / project Loom (was: Enabled fibers / project Loom) > Enable fibers / project Loom > ---------------------------- > > Key: JGRP-2450 > URL: https://issues.redhat.com/browse/JGRP-2450 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 5.0 > > > Add {{use_fibers}} to {{TP}}. > When enabled, we use reflection to create fibers rather than threads in {{DefaultThreadFactory}}. > This requires Java 15/Loom. If not found, regular threads are returned instead. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2450) Enabled fibers / project Loom

by Bela Ban (Jira)

Bela Ban created JGRP-2450: ------------------------------ Summary: Enabled fibers / project Loom Key: JGRP-2450 URL: https://issues.redhat.com/browse/JGRP-2450 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 5.0 Add {{use_fibers}} to {{TP}}. When enabled, we use reflection to create fibers rather than threads in {{DefaultThreadFactory}}. This requires Java 15/Loom. If not found, regular threads are returned instead. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[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 commented on DROOLS-4994: -------------------------------------- Thank you [~uxdlc] > 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: Elizabeth Clayton > Priority: Minor > Labels: UX, UXTeam, drools-tools > Attachments: Screenshot from 2020-01-17 13-56-02.png, Screenshot from 2020-01-17 13-56-10.png, collection-infotip.png, collection-inline.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: > [1] > !Screenshot from 2020-01-17 13-56-02.png|thumbnail! > [2] > !Screenshot from 2020-01-17 13-56-10.png|thumbnail! > How that works now: > 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?" > What expression should be to make test pass: > (2 in ?) -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

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

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-4994?page=com.atlassian.jira.plug... ] Jozef Marko commented on DROOLS-4994: ------------------------------------- Thank you [~uxdlc] > 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: Elizabeth Clayton > Priority: Minor > Labels: UX, UXTeam, drools-tools > Attachments: Screenshot from 2020-01-17 13-56-02.png, Screenshot from 2020-01-17 13-56-10.png, collection-infotip.png, collection-inline.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: > [1] > !Screenshot from 2020-01-17 13-56-02.png|thumbnail! > [2] > !Screenshot from 2020-01-17 13-56-10.png|thumbnail! > How that works now: > 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?" > What expression should be to make test pass: > (2 in ?) -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5023) executable model doesn't fire when Or with trimmed duplicate constraints

by Luca Molteni (Jira)

[ https://issues.redhat.com/browse/DROOLS-5023?page=com.atlassian.jira.plug... ] Luca Molteni updated DROOLS-5023: --------------------------------- Sprint: 2020 Week 07-09 (from Feb 10) > executable model doesn't fire when Or with trimmed duplicate constraints > ------------------------------------------------------------------------ > > Key: DROOLS-5023 > URL: https://issues.redhat.com/browse/DROOLS-5023 > Project: Drools > Issue Type: Bug > Components: executable model > Affects Versions: 7.32.0.Final > Reporter: Toshiya Kobayashi > Assignee: Luca Molteni > Priority: Major > > With a rule like this, (see that white spaces around "==" in the second rule are trimmed) > {noformat} > rule R1 when > Person( $name: name == "Mark", $age: age ) or > Person( $name: name == "Mario", $age : age ) > then > list.add( $name + " is " + $age); > end > rule R2 when > $p: Person( name=="Mark", $age: age ) or > $p: Person( name=="Mario", $age : age ) > then > list.add( $p + " has " + $age + " years"); > end > {noformat} > when you insert a fact, > {code:java} > ksession.insert( new Person( "Mark", 37 ) ); > {code} > only one rule fires. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 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 February 2020