August 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-5581) Add groupBy feature to executable model DSL

by Mario Fusco (Jira)

Mario Fusco created DROOLS-5581: ----------------------------------- Summary: Add groupBy feature to executable model DSL Key: DROOLS-5581 URL: https://issues.redhat.com/browse/DROOLS-5581 Project: Drools Issue Type: Feature Request Reporter: Mario Fusco Assignee: Mario Fusco Optaplanner's CS-D requires that the executable model should provide a construct to build an efficient groupBy implementation. More details are available here [https://docs.google.com/document/d/1IxL2HNMNf_OYxOGGzkVjwXc7NW5ZEear-kz4O...] We already measured that an implementation based on a 3-rules solution as sketched here [https://github.com/triceo/groupby/blob/master/src/main/resources/org/opta...] fulfills the expected performance requirements, so we need # a convenient method in the executable model DSL to define a groupBy # an implementation that internally translates the groupBy defined with 1. into the equivalent of that 3-rules based solution -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13771) Create a Galleon layers for the messaging subsystem

by Yeray Borges Santana (Jira)

Yeray Borges Santana created WFLY-13771: ------------------------------------------- Summary: Create a Galleon layers for the messaging subsystem Key: WFLY-13771 URL: https://issues.redhat.com/browse/WFLY-13771 Project: WildFly Issue Type: Feature Request Components: Build System, JMS Reporter: Yeray Borges Santana Assignee: Emmanuel Hugonnet We have three possible messaging-activemq configuration options that should be supplied via Galleon layers: # messaging-activemq subsystem configuration ready to be used as an Embedded broker. This configuration is useful to run quick demos only, it should not be used in production environments or cloud environments. # messaging-activemq subsystem configuration ready to be used with an external broker. # An empty messaging-activemq subsystem configuration and capabilities to deploy a Resource Adapter file to connect to an external broker. This .rar file has to be deployed by the user. The existing jms-activemq layer was meant to allow client-side JMS, it is almost covering the third option, however, the user should be able to deploy .rar files. The analysis document should clarify whether these capabilities should be included in a Galleon layer itself or by contrast, users should add the resource-adapters Galleon layer to provide it. Another point to clear up is if the Galleon layers will supply capabilities to invoke remote objects configured in the WildFly JNDI tree, hence the need for remoting naming. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5580) Drools repo-wide .gitignore update

by Matteo Mortari (Jira)

Matteo Mortari created DROOLS-5580: -------------------------------------- Summary: Drools repo-wide .gitignore update Key: DROOLS-5580 URL: https://issues.redhat.com/browse/DROOLS-5580 Project: Drools Issue Type: Task Reporter: Matteo Mortari Assignee: Matteo Mortari -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5554) Enhance generated sources annotation for DMNTypes

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5554?page=com.atlassian.jira.plug... ] Toshiya Kobayashi updated DROOLS-5554: -------------------------------------- Sprint: 2020 Week 34-36 (from Aug 17) > Enhance generated sources annotation for DMNTypes > ------------------------------------------------- > > Key: DROOLS-5554 > URL: https://issues.redhat.com/browse/DROOLS-5554 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Affects Versions: 7.40.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > Add annotation to describe DMNTypes in generated sources (InputSet, OutputSet, composite types) for Swagger/OpenAPI. Especially, time related DMN types like time, duration are treated as Java interfaces like Temporal or TemporalAmount in order to accept several Java classes (for output purpose). So this kind of description is needed. > FYI) > https://github.com/kiegroup/drools/pull/2993#issuecomment-660898266 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5561) Add DMN strongly typed tests for collection of collection

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5561?page=com.atlassian.jira.plug... ] Toshiya Kobayashi updated DROOLS-5561: -------------------------------------- Sprint: 2020 Week 34-36 (from Aug 17) > Add DMN strongly typed tests for collection of collection > --------------------------------------------------------- > > Key: DROOLS-5561 > URL: https://issues.redhat.com/browse/DROOLS-5561 > Project: Drools > Issue Type: Task > Components: dmn engine > Affects Versions: 7.41.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > Add tests for collection of collection (of collection)* in DMNRuntimeTypesTest > https://github.com/kiegroup/drools/pull/3030#discussion_r465987525 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1203) Use FC (Feature Candidate) instead of nightlies for LP testing

by Filip Brychta (Jira)

[ https://issues.redhat.com/browse/SWSQE-1203?page=com.atlassian.jira.plugi... ] Filip Brychta resolved SWSQE-1203. ---------------------------------- Resolution: Done Provisioning job is now using FC builds by default > Use FC (Feature Candidate) instead of nightlies for LP testing > -------------------------------------------------------------- > > Key: SWSQE-1203 > URL: https://issues.redhat.com/browse/SWSQE-1203 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Minor > Labels: infrastructure > > {color:#000000}Hi All,{color} > {color:#000000} {color} > {color:#000000}ART will start creating FC (Feature Candidate) after feature freeze date, reason for doing it is because we want to give access to new releases to layered product teams as soon as possible. We are calling it FC and not RC (Release Candidate) because the releases are being built before code freeze and there is no potential for the release to GA. After code freeze, we will begin releasing Release Candidates as we have always done. Nightlies continue to build with the same cadence and will continue to publish the same way.{color} > > {color:#000000}FC is basically a nightly payload (signed with the Beta2 Red Hat key) which is added to the candidate channel, it does not have any signed RPM content. Once we start creating FC ART won’t stop mirroring nightlies to openshift mirror, only after RC (Release Candidate) creation that will happen because RC is actual Release Candidate and it has all the signed content.{color} > > {color:#000000}ART will publish FC once in a week, every friday. First FC for OCP 4.6 will appear in the candidate channel this friday.{color} > > {color:#000000}If you have any questions or issues related to this please reach out to ART team on slack in #aos-art channel.{color} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5579) Unwanted refiring after deserialization of a rule contaning an accumulate with more than one accumulating function

by Mario Fusco (Jira)

Mario Fusco created DROOLS-5579: ----------------------------------- Summary: Unwanted refiring after deserialization of a rule contaning an accumulate with more than one accumulating function Key: DROOLS-5579 URL: https://issues.redhat.com/browse/DROOLS-5579 Project: Drools Issue Type: Bug Reporter: Mario Fusco Assignee: Mario Fusco As demonstrated by this test [https://github.com/kiegroup/drools/blob/master/drools-compiler/src/test/j...] an accumulate rule doesn't refire after deserialization. However if the accumulate contains more than one accumulating function, e.g. the accumulate in that test is rewritten as {code:java} accumulate ( Person ( getName().startsWith(\"M\"), $age : age ); $sum : sum( $age ), $max : max( $age ) {code} it mistakenly fires once again after deserialization. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3160) adapt kie upstream reps for Thorntail 2.2 (ex WildFly Swarm)

by Michael Biarnes Kiefer (Jira)

[ https://issues.redhat.com/browse/DROOLS-3160?page=com.atlassian.jira.plug... ] Michael Biarnes Kiefer updated DROOLS-3160: ------------------------------------------- Fix Version/s: 7.43.0.Final (was: 7.42.0.Final) > adapt kie upstream reps for Thorntail 2.2 (ex WildFly Swarm) > ------------------------------------------------------------ > > Key: DROOLS-3160 > URL: https://issues.redhat.com/browse/DROOLS-3160 > Project: Drools > Issue Type: Feature Request > Reporter: Michael Biarnes Kiefer > Assignee: Toni Rikkola > Priority: Major > Fix For: 7.43.0.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2254) Automate .proto files rebuild in pom.xml

by Michael Biarnes Kiefer (Jira)

[ https://issues.redhat.com/browse/DROOLS-2254?page=com.atlassian.jira.plug... ] Michael Biarnes Kiefer updated DROOLS-2254: ------------------------------------------- Fix Version/s: 7.43.0.Final (was: 7.42.0.Final) > Automate .proto files rebuild in pom.xml > ---------------------------------------- > > Key: DROOLS-2254 > URL: https://issues.redhat.com/browse/DROOLS-2254 > Project: Drools > Issue Type: Task > Components: tools > Affects Versions: 7.5.0.Final > Reporter: Dmitry Volodin > Assignee: Dmitry Volodin > Priority: Minor > Fix For: 7.43.0.Final > > > According to contribution guide, any .proto file or protobuf version changes it's necessary to download protoc utility and regenerate Java classes based on .proto files. > This will add automation for downloading protoc utility and Java classes generation based on Maven Protocol Buffers Plugin. There is no timestamps and other build related info inside generated Java files and no changes will be added on each new build. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4830) Add a Docker composer to connect BC and Kie Server images

by Michael Biarnes Kiefer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4830?page=com.atlassian.jira.plug... ] Michael Biarnes Kiefer updated DROOLS-4830: ------------------------------------------- Fix Version/s: 7.43.0.Final (was: 7.42.0.Final) > Add a Docker composer to connect BC and Kie Server images > --------------------------------------------------------- > > Key: DROOLS-4830 > URL: https://issues.redhat.com/browse/DROOLS-4830 > Project: Drools > Issue Type: Feature Request > Components: docker images > Affects Versions: 7.30.0.Final > Reporter: Ricardo Zanini Fernandes > Assignee: Ricardo Zanini Fernandes > Priority: Major > Fix For: 7.43.0.Final > > > It's natural to have BC and KIE servers working together. Would be nice to have a Docker composer file that fires up the two instances at once. This will support use cases such authoring on BC and deploying in the connected KIE Server. > References: https://www.drools.org/download/download.html -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 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 August 2020