July 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-5518) DMN strongly typed class compile errors for capitalized/non-capitalized properties conflict

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5518?page=com.atlassian.jira.plug... ] Toshiya Kobayashi updated DROOLS-5518: -------------------------------------- Sprint: 2020 Week 31-33 (from Jul 27) > DMN strongly typed class compile errors for capitalized/non-capitalized properties conflict > ------------------------------------------------------------------------------------------- > > Key: DROOLS-5518 > URL: https://issues.redhat.com/browse/DROOLS-5518 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.40.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > If we have node names where the difference is only "First letter is capitalized or not" (e.g. "myPerson" and "MyPerson"), it will cause a compile error for InputSet and OutputSet. Note that it works fine without typesafe. > - DMNRuntimeTypesTest.testCapitalLetterConflict() > - DMNRuntimeTypesTest.testCapitalLetterConflictWithInputAndDecision() > https://github.com/kiegroup/drools/pull/2993#discussion_r456300584 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5517) Enhance DMNResult/DMNContext to be able to return strongly typed OutputSet

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5517?page=com.atlassian.jira.plug... ] Toshiya Kobayashi updated DROOLS-5517: -------------------------------------- Sprint: 2020 Week 31-33 (from Jul 27) > Enhance DMNResult/DMNContext to be able to return strongly typed OutputSet > -------------------------------------------------------------------------- > > Key: DROOLS-5517 > URL: https://issues.redhat.com/browse/DROOLS-5517 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Affects Versions: 7.40.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > DROOLS-5502 was to generate OutputSet class and convert DMNResult.getContext().getAll() to the OutputSet externally. This JIRA aims to convert it inside DMNRuntime so that we can get the OutputSet from DMNResult.getContext().getXXX() directly. > https://github.com/kiegroup/drools/pull/2993#pullrequestreview-451150317 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5519) Improve OutputSet to have FEELFunction fields rather than Object

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5519?page=com.atlassian.jira.plug... ] Toshiya Kobayashi updated DROOLS-5519: -------------------------------------- Sprint: 2020 Week 31-33 (from Jul 27) > Improve OutputSet to have FEELFunction fields rather than Object > ---------------------------------------------------------------- > > Key: DROOLS-5519 > URL: https://issues.redhat.com/browse/DROOLS-5519 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Affects Versions: 7.40.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Minor > > Currently OutputSet have Object fields to store FEELFunction for DecisionService/BKM context values. This Jira is to enhance to have org.kie.dmn.feel.runtime.FEELFunction in the generated OutputSet. > https://github.com/kiegroup/drools/pull/2993/files#r455626598 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5232) Improve DMNDI validation rule

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5232?page=com.atlassian.jira.plug... ] Toshiya Kobayashi updated DROOLS-5232: -------------------------------------- Sprint: 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25), 2020 Week 25-27 (from Jun 15) (was: 2020 Week 16-18 (from Apr 13), 2020 Week 19-21 (from May 4), 2020 Week 22-24 (from May 25), 2020 Week 25-27 (from Jun 15), 2020 Week 28-30 (from Jul 6)) > Improve DMNDI validation rule > ----------------------------- > > Key: DROOLS-5232 > URL: https://issues.redhat.com/browse/DROOLS-5232 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Minor > > Improve DMNDI validation rule not to use eval function. > Idea: Add a static java function which takes Definitions and will produce as output all descendant children. So we can write a rule to get them by single "from". > https://github.com/kiegroup/drools/pull/2839#discussion_r405998284 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5062) Bootable JAR doesn't create install directories

by James Perkins (Jira)

[ https://issues.redhat.com/browse/WFCORE-5062?page=com.atlassian.jira.plug... ] James Perkins updated WFCORE-5062: ---------------------------------- Component/s: Bootable JAR > Bootable JAR doesn't create install directories > ----------------------------------------------- > > Key: WFCORE-5062 > URL: https://issues.redhat.com/browse/WFCORE-5062 > Project: WildFly Core > Issue Type: Bug > Components: Bootable JAR > Reporter: Jean Francois Denise > Assignee: James Perkins > Priority: Critical > > The issue occurs with --install-dir Bootable JAR option, > In case the first entry to be unzipped is not a directory, the unzip fails because the install dir doesn't exist. > This issue is hidden on some platforms where the first entries are directories, in such case, directories hierarchy is created. > This issue impacts Arquilian container for Bootable JAR that contains a workaround for it. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5062) Bootable JAR doesn't create install directories

by James Perkins (Jira)

[ https://issues.redhat.com/browse/WFCORE-5062?page=com.atlassian.jira.plug... ] James Perkins reassigned WFCORE-5062: ------------------------------------- Assignee: James Perkins (was: Jeff Mesnil) > Bootable JAR doesn't create install directories > ----------------------------------------------- > > Key: WFCORE-5062 > URL: https://issues.redhat.com/browse/WFCORE-5062 > Project: WildFly Core > Issue Type: Bug > Reporter: Jean Francois Denise > Assignee: James Perkins > Priority: Critical > > The issue occurs with --install-dir Bootable JAR option, > In case the first entry to be unzipped is not a directory, the unzip fails because the install dir doesn't exist. > This issue is hidden on some platforms where the first entries are directories, in such case, directories hierarchy is created. > This issue impacts Arquilian container for Bootable JAR that contains a workaround for it. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5063) Upgrade jboss-parent pom from 35 to 37

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFCORE-5063?page=com.atlassian.jira.plug... ] Brian Stansberry moved WFLY-13702 to WFCORE-5063: ------------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-5063 (was: WFLY-13702) Component/s: Build System (was: Build System) > Upgrade jboss-parent pom from 35 to 37 > -------------------------------------- > > Key: WFCORE-5063 > URL: https://issues.redhat.com/browse/WFCORE-5063 > Project: WildFly Core > Issue Type: Bug > Components: Build System > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Major > > https://github.com/jboss/jboss-parent-pom/compare/jboss-parent-35...jboss... > Particularly pick up https://github.com/jboss/jboss-parent-pom/issues/93 which brings in the fix for https://nvd.nist.gov/vuln/detail/CVE-2019-10782 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13701) Upgrade jboss-parent pom from 35 to 37

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-13701: --------------------------------------- Summary: Upgrade jboss-parent pom from 35 to 37 Key: WFLY-13701 URL: https://issues.redhat.com/browse/WFLY-13701 Project: WildFly Issue Type: Bug Components: Build System Reporter: Brian Stansberry Assignee: Brian Stansberry https://github.com/jboss/jboss-parent-pom/compare/jboss-parent-35...jboss... Particularly pick up https://github.com/jboss/jboss-parent-pom/issues/93 which brings in the fix for https://nvd.nist.gov/vuln/detail/CVE-2019-10782 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13702) Upgrade jboss-parent pom from 35 to 37

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-13702: --------------------------------------- Summary: Upgrade jboss-parent pom from 35 to 37 Key: WFLY-13702 URL: https://issues.redhat.com/browse/WFLY-13702 Project: WildFly Issue Type: Bug Components: Build System Reporter: Brian Stansberry Assignee: Brian Stansberry https://github.com/jboss/jboss-parent-pom/compare/jboss-parent-35...jboss... Particularly pick up https://github.com/jboss/jboss-parent-pom/issues/93 which brings in the fix for https://nvd.nist.gov/vuln/detail/CVE-2019-10782 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5062) Bootable JAR doesn't create install directories

by Jean Francois Denise (Jira)

[ https://issues.redhat.com/browse/WFCORE-5062?page=com.atlassian.jira.plug... ] Jean Francois Denise updated WFCORE-5062: ----------------------------------------- Description: The issue occurs with --install-dir Bootable JAR option, In case the first entry to be unzipped is not a directory, the unzip fails because the install dir doesn't exist. This issue is hidden on some platforms where the first entries are directories, in such case, directories hierarchy is created. This issue impacts Arquilian container for Bootable JAR that contains a workaround for it. was: The issue occurs with --install-dir Bootable JAR option, In case the first entry to be unzipped is not a directory, the unzip fails because the install dir doesn't exist. This issue is hidden on some platforms where the first entries are directories, in such case, directories hierarchy is created. This issue blocks Arquilian container for Bootable JAR. > Bootable JAR doesn't create install directories > ----------------------------------------------- > > Key: WFCORE-5062 > URL: https://issues.redhat.com/browse/WFCORE-5062 > Project: WildFly Core > Issue Type: Bug > Reporter: Jean Francois Denise > Assignee: Jeff Mesnil > Priority: Critical > > The issue occurs with --install-dir Bootable JAR option, > In case the first entry to be unzipped is not a directory, the unzip fails because the install dir doesn't exist. > This issue is hidden on some platforms where the first entries are directories, in such case, directories hierarchy is created. > This issue impacts Arquilian container for Bootable JAR that contains a workaround for it. -- 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 July 2020