July 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-5539) Review dmn examples version in codebase

by Matteo Mortari (Jira)

[ https://issues.redhat.com/browse/DROOLS-5539?page=com.atlassian.jira.plug... ] Matteo Mortari updated DROOLS-5539: ----------------------------------- Description: Motivation: avoid a User might find *easily* an outdated version (DMN v1.1) in the examples from our codebase. Goal: review dmn examples version in codebase to make sure there are no "default" v1.1 model to be found, that are properly isolated in specific packages and/or specific test infrastructure. Impacts: kie-dmn codebase in drools.git and downstream repos to be assessed. was:Review dmn example version in codebase to make sure there are no "default" v1.1 model to be found, that are properly isolated in specific packages or specific test infrastructure. > Review dmn examples version in codebase > --------------------------------------- > > Key: DROOLS-5539 > URL: https://issues.redhat.com/browse/DROOLS-5539 > Project: Drools > Issue Type: Epic > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > > Motivation: avoid a User might find *easily* an outdated version (DMN v1.1) in the examples from our codebase. > Goal: review dmn examples version in codebase to make sure there are no "default" v1.1 model to be found, that are properly isolated in specific packages and/or specific test infrastructure. > Impacts: kie-dmn codebase in drools.git and downstream repos to be assessed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5539) Review dmn examples version in codebase

by Matteo Mortari (Jira)

[ https://issues.redhat.com/browse/DROOLS-5539?page=com.atlassian.jira.plug... ] Matteo Mortari updated DROOLS-5539: ----------------------------------- Description: *Motivation*: avoid a User might find *_easily_* an outdated version (DMN v1.1) in the examples from our codebase. *Goal*: review dmn examples version in codebase to make sure there are no "default" v1.1 model to be found, that are properly isolated in specific packages and/or specific test infrastructure. *Impacts*: kie-dmn codebase in drools.git and downstream repos to be assessed. was: Motivation: avoid a User might find *easily* an outdated version (DMN v1.1) in the examples from our codebase. Goal: review dmn examples version in codebase to make sure there are no "default" v1.1 model to be found, that are properly isolated in specific packages and/or specific test infrastructure. Impacts: kie-dmn codebase in drools.git and downstream repos to be assessed. > Review dmn examples version in codebase > --------------------------------------- > > Key: DROOLS-5539 > URL: https://issues.redhat.com/browse/DROOLS-5539 > Project: Drools > Issue Type: Epic > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > > *Motivation*: avoid a User might find *_easily_* an outdated version (DMN v1.1) in the examples from our codebase. > *Goal*: review dmn examples version in codebase to make sure there are no "default" v1.1 model to be found, that are properly isolated in specific packages and/or specific test infrastructure. > *Impacts*: kie-dmn codebase in drools.git and downstream repos to be assessed. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5539) Review dmn examples version in codebase

by Matteo Mortari (Jira)

[ https://issues.redhat.com/browse/DROOLS-5539?page=com.atlassian.jira.plug... ] Matteo Mortari updated DROOLS-5539: ----------------------------------- Issue Type: Epic (was: Story) > Review dmn examples version in codebase > --------------------------------------- > > Key: DROOLS-5539 > URL: https://issues.redhat.com/browse/DROOLS-5539 > Project: Drools > Issue Type: Epic > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > > Review dmn example version in codebase to make sure there are no "default" v1.1 model to be found, that are properly isolated in specific packages or specific test infrastructure. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5539) Review dmn examples version in codebase

by Matteo Mortari (Jira)

Matteo Mortari created DROOLS-5539: -------------------------------------- Summary: Review dmn examples version in codebase Key: DROOLS-5539 URL: https://issues.redhat.com/browse/DROOLS-5539 Project: Drools Issue Type: Story Components: dmn engine Reporter: Matteo Mortari Assignee: Matteo Mortari Review dmn example version in codebase to make sure there are no "default" v1.1 model to be found, that are properly isolated in specific packages or specific test infrastructure. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13351) Add a Galleon layer for the Mail subsystem

by Yeray Borges Santana (Jira)

[ https://issues.redhat.com/browse/WFLY-13351?page=com.atlassian.jira.plugi... ] Yeray Borges Santana updated WFLY-13351: ---------------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/13349 (was: https://github.com/wildfly/wildfly/pull/13233) > Add a Galleon layer for the Mail subsystem > ------------------------------------------ > > Key: WFLY-13351 > URL: https://issues.redhat.com/browse/WFLY-13351 > Project: WildFly > Issue Type: Feature Request > Components: Build System, Mail > Reporter: Brian Stansberry > Assignee: Yeray Borges Santana > Priority: Major > Fix For: 21.0.0.Beta1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5538) DMN strongly typed class compile errors for collection types

by Toshiya Kobayashi (Jira)

Toshiya Kobayashi created DROOLS-5538: ----------------------------------------- Summary: DMN strongly typed class compile errors for collection types Key: DROOLS-5538 URL: https://issues.redhat.com/browse/DROOLS-5538 Project: Drools Issue Type: Bug Components: dmn engine Affects Versions: 7.40.0.Final Reporter: Toshiya Kobayashi Assignee: Toshiya Kobayashi If we have an itemDefinition with isCollection="true", it will cause a compile error for InputSet and OutputSet when typesafe is enabled. Note that itemComponent with isCollection="true" works fine. DMNRuntimeTypesTest.testCollectionType() {code:xml} <semantic:itemDefinition label="tPersonList" name="tPersonList" isCollection="true"> <semantic:typeRef>tPerson</semantic:typeRef> </semantic:itemDefinition> {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13707) Upgrade smallrye-open-api to 2.0.6

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-13707?page=com.atlassian.jira.plugi... ] Paul Ferraro updated WFLY-13707: -------------------------------- Summary: Upgrade smallrye-open-api to 2.0.6 (was: Upgrade smallrye-open-api to 2.0.5) > Upgrade smallrye-open-api to 2.0.6 > ---------------------------------- > > Key: WFLY-13707 > URL: https://issues.redhat.com/browse/WFLY-13707 > Project: WildFly > Issue Type: Component Upgrade > Components: MP OpenAPI > Affects Versions: 20.0.1.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > > Fixes: > [https://github.com/smallrye/smallrye-open-api/issues/404] > > Release notes: > [https://github.com/smallrye/smallrye-open-api/releases/tag/2.0.4|https://...] > [https://github.com/smallrye/smallrye-open-api/releases/tag/2.0.5|https://...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5070) List to Set ParameterCorrectors and ParameterValidators

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFCORE-5070?page=com.atlassian.jira.plug... ] Brian Stansberry updated WFCORE-5070: ------------------------------------- Description: The management API doesn't have a "SET" attribute/parameter type but use cases like JBEAP-19958 shows there's some need for a bit of set-like behavior. Idea here is the controller module could expose some static factories for ParameterCorrectors and ParameterValidators to impose set semantics on a ModelType.LIST attribute. A validator would be used to reject lists with duplicates. A corrector would be used to remove dups from a list without failing. For a corrector construction could perhaps be parameterized by allowing passing in the name of the attribute and a log level. Those would be used to log when the corrector removes duplicates. The corrector would definitely need to know the attribute name to log an appropriate message. The appropriate level for a message may vary based on the attribute. was: The management API doesn't have a "SET" attribute/parameter type but use cases like JBEAP-19958 shows there's some need. Idea here is the controller module could expose some static factories for ParameterCorrectors and ParameterValidators to impose set semantics on a ModelType.LIST attribute. A validator would be used to reject lists with duplicates. A corrector would be used to remove dups from a list without failing. For a corrector construction could perhaps be parameterized by allowing passing in the name of the attribute and a log level. Those would be used to log when the corrector removes duplicates. The corrector would definitely need to know the attribute name to log an appropriate message. The appropriate level for a message may vary based on the attribute. > List to Set ParameterCorrectors and ParameterValidators > ------------------------------------------------------- > > Key: WFCORE-5070 > URL: https://issues.redhat.com/browse/WFCORE-5070 > Project: WildFly Core > Issue Type: Enhancement > Components: Management > Reporter: Brian Stansberry > Assignee: Jeff Mesnil > Priority: Minor > > The management API doesn't have a "SET" attribute/parameter type but use cases like JBEAP-19958 shows there's some need for a bit of set-like behavior. > Idea here is the controller module could expose some static factories for ParameterCorrectors and ParameterValidators to impose set semantics on a ModelType.LIST attribute. > A validator would be used to reject lists with duplicates. > A corrector would be used to remove dups from a list without failing. > For a corrector construction could perhaps be parameterized by allowing passing in the name of the attribute and a log level. Those would be used to log when the corrector removes duplicates. The corrector would definitely need to know the attribute name to log an appropriate message. The appropriate level for a message may vary based on the attribute. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5070) List to Set ParameterCorrectors and ParameterValidators

by Brian Stansberry (Jira)

Brian Stansberry created WFCORE-5070: ---------------------------------------- Summary: List to Set ParameterCorrectors and ParameterValidators Key: WFCORE-5070 URL: https://issues.redhat.com/browse/WFCORE-5070 Project: WildFly Core Issue Type: Enhancement Components: Management Reporter: Brian Stansberry Assignee: Jeff Mesnil The management API doesn't have a "SET" attribute/parameter type but use cases like JBEAP-19958 shows there's some need. Idea here is the controller module could expose some static factories for ParameterCorrectors and ParameterValidators to impose set semantics on a ModelType.LIST attribute. A validator would be used to reject lists with duplicates. A corrector would be used to remove dups from a list without failing. For a corrector construction could perhaps be parameterized by allowing passing in the name of the attribute and a log level. Those would be used to log when the corrector removes duplicates. The corrector would definitely need to know the attribute name to log an appropriate message. The appropriate level for a message may vary based on the attribute. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5067) Wildfly as Windows Service fails to stop in a timely fashion

by Cedric HENRY (Jira)

[ https://issues.redhat.com/browse/WFCORE-5067?page=com.atlassian.jira.plug... ] Cedric HENRY updated WFCORE-5067: --------------------------------- Affects Version/s: 2.2.0.Final > Wildfly as Windows Service fails to stop in a timely fashion > ------------------------------------------------------------ > > Key: WFCORE-5067 > URL: https://issues.redhat.com/browse/WFCORE-5067 > Project: WildFly Core > Issue Type: Bug > Affects Versions: 2.2.0.Final > Reporter: Cedric HENRY > Assignee: Jeff Mesnil > Priority: Major > > As already discussed under WFCORE-1719, there a problem when stopping the 'Wildfly' Windows service resulting in error dialog about the service not stopping in a timely fashion. > Further details got also provided in the comment https://issues.redhat.com/browse/WFCORE-1719?focusedCommentId=143... -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 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