September 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4808) Upgrade JGit to 5.9.0.202009080501-r

by Emmanuel Hugonnet (Jira)

[ https://issues.redhat.com/browse/WFCORE-4808?page=com.atlassian.jira.plug... ] Emmanuel Hugonnet updated WFCORE-4808: -------------------------------------- Summary: Upgrade JGit to 5.9.0.202009080501-r (was: Upgrade JGit to 5.6.0.201912101111-r) > Upgrade JGit to 5.9.0.202009080501-r > ------------------------------------ > > Key: WFCORE-4808 > URL: https://issues.redhat.com/browse/WFCORE-4808 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Management > Affects Versions: 11.0.0.Beta7 > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Priority: Major > > Updating JGit and all its dependencies -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5682) Forall with empty list constraint combined with or does not fire as expected

by Matteo Casalino (Jira)

[ https://issues.redhat.com/browse/DROOLS-5682?page=com.atlassian.jira.plug... ] Matteo Casalino updated DROOLS-5682: ------------------------------------ Description: As of Drools {{7.32.0.Final}}, {{forall}} patterns with "empty list" constraints combined with other constraints through {{||}} will fail to match as expected. For example the following rule: {noformat} rule "forall with not equal" when forall($p : Pojo(y == 1) Pojo(x.empty || x contains 2, z == 3, this == $p)) then end {noformat} will not fire against following facts: {noformat} Pojo{x=[2], y=0, z=0} Pojo{x=[], y=1, z=3} Pojo{x=[3], y=0, z=3} Pojo{x=[2], y=1, z=3} {noformat} We suspect a problem with the rewriting of the {{forall}} clause. It appears the clause is rewritten as: {{not Pojo(y == 1, (x.empty && !(x contains 2)) || !(z == 3))}} instead of the expected: {{not Pojo(y == 1, (!(x.empty) && !(x contains 2)) || !(z == 3))}} This is working fine when using Drools {{<= 7.31.0.Final}}. was: As of Drools 7.32.0.Final, {{forall}} patterns with "empty list" constraints combined with other constraints through {{or}} will fail to match as expected. For example the following rule: {noformat} rule "forall with not equal" when forall($p : Pojo(y == 1) Pojo(x.empty || x contains 2, z == 3, this == $p)) then end {noformat} will not fire against following facts: {noformat} Pojo{x=[2], y=0, z=0} Pojo{x=[], y=1, z=3} Pojo{x=[3], y=0, z=3} Pojo{x=[2], y=1, z=3} {noformat} We suspect a problem with the rewriting of the {{forall}} clause. It appears the clause is rewritten as: {{not Pojo(y == 1, (x.empty && !(x contains 2)) || !(z == 3))}} instead of the expected: {{not Pojo(y == 1, (!(x.empty) && !(x contains 2)) || !(z == 3))}} This is working fine when using Drools {{<= 7.31.0.Final}}. > Forall with empty list constraint combined with or does not fire as expected > ---------------------------------------------------------------------------- > > Key: DROOLS-5682 > URL: https://issues.redhat.com/browse/DROOLS-5682 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.32.0.Final, 7.33.0.Final, 7.34.0.Final, 7.35.0.Final, 7.36.0.Final, 7.37.0.Final, 7.38.0.Final, 7.39.0.Final, 7.40.0.Final, 7.41.0.Final, 7.42.0.Final, 7.43.0.Final > Reporter: Matteo Casalino > Assignee: Mario Fusco > Priority: Major > Attachments: forall-with-empty-list-constraint-combined-with-or.zip > > > As of Drools {{7.32.0.Final}}, {{forall}} patterns with "empty list" constraints combined with other constraints through {{||}} will fail to match as expected. > For example the following rule: > {noformat} > rule "forall with not equal" > when forall($p : Pojo(y == 1) > Pojo(x.empty || x contains 2, z == 3, this == $p)) > then > end > {noformat} > will not fire against following facts: > {noformat} > Pojo{x=[2], y=0, z=0} > Pojo{x=[], y=1, z=3} > Pojo{x=[3], y=0, z=3} > Pojo{x=[2], y=1, z=3} > {noformat} > We suspect a problem with the rewriting of the {{forall}} clause. It appears the clause is rewritten as: > {{not Pojo(y == 1, (x.empty && !(x contains 2)) || !(z == 3))}} > instead of the expected: > {{not Pojo(y == 1, (!(x.empty) && !(x contains 2)) || !(z == 3))}} > This is working fine when using Drools {{<= 7.31.0.Final}}. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5682) Forall with empty list constraint combined with or does not fire as expected

by Matteo Casalino (Jira)

Matteo Casalino created DROOLS-5682: --------------------------------------- Summary: Forall with empty list constraint combined with or does not fire as expected Key: DROOLS-5682 URL: https://issues.redhat.com/browse/DROOLS-5682 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 7.43.0.Final, 7.42.0.Final, 7.41.0.Final, 7.40.0.Final, 7.39.0.Final, 7.38.0.Final, 7.37.0.Final, 7.36.0.Final, 7.35.0.Final, 7.34.0.Final, 7.33.0.Final, 7.32.0.Final Reporter: Matteo Casalino Assignee: Mario Fusco Attachments: forall-with-empty-list-constraint-combined-with-or.zip As of Drools 7.32.0.Final, {{forall}} patterns with "empty list" constraints combined with other constraints through {{or}} will fail to match as expected. For example the following rule: {noformat} rule "forall with not equal" when forall($p : Pojo(y == 1) Pojo(x.empty || x contains 2, z == 3, this == $p)) then end {noformat} will not fire against following facts: {noformat} Pojo{x=[2], y=0, z=0} Pojo{x=[], y=1, z=3} Pojo{x=[3], y=0, z=3} Pojo{x=[2], y=1, z=3} {noformat} We suspect a problem with the rewriting of the {{forall}} clause. It appears the clause is rewritten as: {{not Pojo(y == 1, (x.empty && !(x contains 2)) || !(z == 3))}} instead of the expected: {{not Pojo(y == 1, (!(x.empty) && !(x contains 2)) || !(z == 3))}} This is working fine when using Drools {{<= 7.31.0.Final}}. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5095) [DMN Designer] Investigate performance switching between editor instances

by Michael Biarnes Kiefer (Jira)

[ https://issues.redhat.com/browse/DROOLS-5095?page=com.atlassian.jira.plug... ] Michael Biarnes Kiefer updated DROOLS-5095: ------------------------------------------- Fix Version/s: 7.45.0.Final (was: 7.44.0.Final) > [DMN Designer] Investigate performance switching between editor instances > ------------------------------------------------------------------------- > > Key: DROOLS-5095 > URL: https://issues.redhat.com/browse/DROOLS-5095 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.33.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Gomes > Priority: Minor > Labels: drools-tools > Fix For: 7.45.0.Final > > Attachments: switch-dmn.webm > > > This JIRA is to investigate the reported performance issue switching between different DMN Designer instances in Business Central. > The issue was noticed by [~jomarko] when testing DROOLS-5058 (although the fix therein should have had *zero* affect on switching). > For more details see the video [^switch-dmn.webm] > h2. Manual acceptance test > - Prepare 5 DMN models in project > - Open all in parallel > - Try to switch between them, keep all opened -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 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.45.0.Final (was: 7.44.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.45.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, 7 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.45.0.Final (was: 7.44.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.45.0.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13914) Add Maven repos to BOMs

by Eduardo Martins (Jira)

Eduardo Martins created WFLY-13914: -------------------------------------- Summary: Add Maven repos to BOMs Key: WFLY-13914 URL: https://issues.redhat.com/browse/WFLY-13914 Project: WildFly Issue Type: Enhancement Components: BOM Reporter: Eduardo Martins Assignee: Eduardo Martins The BOM Builder maven plugin should have a feature to add Maven repos to built BOMs. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5681) ByteArrayResource bytes attribute read/write twice

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-5681?page=com.atlassian.jira.plug... ] Mario Fusco commented on DROOLS-5681: ------------------------------------- [~slem1] thanks for reporting it. Yes, fixing it in the next release will be ok, please feel free to send a pull request with the fix if you can. > ByteArrayResource bytes attribute read/write twice > -------------------------------------------------- > > Key: DROOLS-5681 > URL: https://issues.redhat.com/browse/DROOLS-5681 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.43.1.Final > Reporter: Sylvain Lemoine > Assignee: Mario Fusco > Priority: Major > > When using Java standard serialization mechanism, we can see that ByteArrayResource is now written twice > in ByteArrayResource > {code:java} > @Override > public void writeExternal(ObjectOutput out) throws IOException { > super.writeExternal( out ); > out.writeObject( bytes ); > out.writeObject(this.encoding); > }{code} > And super class writeExternal: > {code:java} > public void writeExternal(ObjectOutput out) throws IOException { > //... > out.writeObject( bytes ); > }{code} > It works as it also read twice in ByteArrayResource#readExternal and ByteArrayResource#readExternal. > Anyway, moving the bytes attribute from child class to super class in [bb5e421df|https://github.com/kiegroup/drools/commit/bb5e421df8950cb23... broke our project serialization as we rely on java serialization for our KieBase resources. Seems ok as we'll address it by some tweaking on serialVersionUID, but fixing this issue (read/write once instead of twice) will also break deserialization for projects which rely on it from 7.34.0.Final. > Don't know if it's ok to fix it in the next version. I can make a PR for this case. > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5426) Code completion with C3 for FEEL

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-5426?page=com.atlassian.jira.plug... ] Toni Rikkola updated DROOLS-5426: --------------------------------- Sprint: 2020 Week 40-42 (from Sep 28) > Code completion with C3 for FEEL > -------------------------------- > > Key: DROOLS-5426 > URL: https://issues.redhat.com/browse/DROOLS-5426 > Project: Drools > Issue Type: Feature Request > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5681) ByteArrayResource bytes attribute read/write twice

by Sylvain Lemoine (Jira)

[ https://issues.redhat.com/browse/DROOLS-5681?page=com.atlassian.jira.plug... ] Sylvain Lemoine updated DROOLS-5681: ------------------------------------ Description: When using Java standard serialization mechanism, we can see that ByteArrayResource is now written twice in ByteArrayResource {code:java} @Override public void writeExternal(ObjectOutput out) throws IOException { super.writeExternal( out ); out.writeObject( bytes ); out.writeObject(this.encoding); }{code} And super class writeExternal: {code:java} public void writeExternal(ObjectOutput out) throws IOException { //... out.writeObject( bytes ); }{code} It works as it also read twice in ByteArrayResource#readExternal and ByteArrayResource#readExternal. Anyway, moving the bytes attribute from child class to super class in [bb5e421df|https://github.com/kiegroup/drools/commit/bb5e421df8950cb23... broke our project serialization as we rely on java serialization for our KieBase resources. Seems ok as we'll address it by some tweaking on serialVersionUID, but fixing this issue (read/write once instead of twice) will also break deserialization for projects which rely on it from 7.34.0.Final. Don't know if it's ok to fix it in the next version. I can make a PR for this case. was: When using Java standard serialization mechanism, we can see that ByteArrayResource is now written twice in ByteArrayResource {code:java} @Override public void writeExternal(ObjectOutput out) throws IOException { super.writeExternal( out ); out.writeObject( bytes ); out.writeObject(this.encoding); }{code} And super class writeExternal: {code:java} public void writeExternal(ObjectOutput out) throws IOException { //... out.writeObject( bytes ); }{code} It works as it also read twice in ByteArrayResource#readExternal and ByteArrayResource#readExternal. Anyway, moving the bytes attribute from child class to super class in [[bb5e421df|https://github.com/kiegroup/drools/commit/bb5e421df8950cb2... | [https://github.com/kiegroup/drools/commit/bb5e421df8950cb2355071863b2c478... broke our project serialization as we rely on java serialization for our KieBase resources. Seems ok as we'll address it by some tweaking on serialVersionUID, but fixing this issue (read/write once instead of twice) will also break deserialization for projects which rely on it from 7.34.0.Final. Don't know if it's ok to fix it in the next version. I can make a PR for this case. > ByteArrayResource bytes attribute read/write twice > -------------------------------------------------- > > Key: DROOLS-5681 > URL: https://issues.redhat.com/browse/DROOLS-5681 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.43.1.Final > Reporter: Sylvain Lemoine > Assignee: Mario Fusco > Priority: Major > > When using Java standard serialization mechanism, we can see that ByteArrayResource is now written twice > in ByteArrayResource > {code:java} > @Override > public void writeExternal(ObjectOutput out) throws IOException { > super.writeExternal( out ); > out.writeObject( bytes ); > out.writeObject(this.encoding); > }{code} > And super class writeExternal: > {code:java} > public void writeExternal(ObjectOutput out) throws IOException { > //... > out.writeObject( bytes ); > }{code} > It works as it also read twice in ByteArrayResource#readExternal and ByteArrayResource#readExternal. > Anyway, moving the bytes attribute from child class to super class in [bb5e421df|https://github.com/kiegroup/drools/commit/bb5e421df8950cb23... broke our project serialization as we rely on java serialization for our KieBase resources. Seems ok as we'll address it by some tweaking on serialVersionUID, but fixing this issue (read/write once instead of twice) will also break deserialization for projects which rely on it from 7.34.0.Final. > Don't know if it's ok to fix it in the next version. I can make a PR for this case. > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

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