April 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4912) Upgrade Galleon from 4.2.4.Final to 4.2.5.Final

by Jean Francois Denise (Jira)

[ https://issues.redhat.com/browse/WFCORE-4912?page=com.atlassian.jira.plug... ] Jean Francois Denise moved WFLY-13348 to WFCORE-4912: ----------------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-4912 (was: WFLY-13348) Component/s: Build System (was: Build System) > Upgrade Galleon from 4.2.4.Final to 4.2.5.Final > ----------------------------------------------- > > Key: WFCORE-4912 > URL: https://issues.redhat.com/browse/WFCORE-4912 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Build System > Reporter: Jean Francois Denise > Assignee: Jean Francois Denise > Priority: Minor > > Upgrade Galleon from 4.2.4.Final to 4.2.5.Final. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13217) Upgrade wildfly-transaction-client to 1.1.10.Final

by Ingo Weiss (Jira)

[ https://issues.redhat.com/browse/WFLY-13217?page=com.atlassian.jira.plugi... ] Ingo Weiss updated WFLY-13217: ------------------------------ Labels: downstream_dependency (was: ) > Upgrade wildfly-transaction-client to 1.1.10.Final > -------------------------------------------------- > > Key: WFLY-13217 > URL: https://issues.redhat.com/browse/WFLY-13217 > Project: WildFly > Issue Type: Component Upgrade > Components: Transactions > Affects Versions: 19.0.0.Beta3 > Reporter: Tomasz Adamski > Assignee: Tomasz Adamski > Priority: Major > Labels: downstream_dependency > Fix For: 20.0.0.Beta1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2465) Remove use_ip_addrs

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2465?page=com.atlassian.jira.plugin... ] Bela Ban resolved JGRP-2465. ---------------------------- Resolution: Done > Remove use_ip_addrs > ------------------- > > Key: JGRP-2465 > URL: https://issues.redhat.com/browse/JGRP-2465 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 5.0.0.Alpha4 > > > Remove {{use_ip_addrs}}; nobody uses this and it complicates the code. Also remove {{NAMING}}. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2465) Remove use_ip_addrs

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2465?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-2465: --------------------------- Description: Remove {{use_ip_addrs}}; nobody uses this and it complicates the code. Also remove {{NAMING}}. (was: Remove {{use_ip_addrs}}; nobody uses this and it complicates the code) > Remove use_ip_addrs > ------------------- > > Key: JGRP-2465 > URL: https://issues.redhat.com/browse/JGRP-2465 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 5.0.0.Alpha4 > > > Remove {{use_ip_addrs}}; nobody uses this and it complicates the code. Also remove {{NAMING}}. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11905) Move module org.apache.xml-resolver from WildFly Core to WildFly

by Kabir Khan (Jira)

[ https://issues.redhat.com/browse/WFLY-11905?page=com.atlassian.jira.plugi... ] Kabir Khan commented on WFLY-11905: ----------------------------------- [~brian.stansberry] I cloned this to WFCORE-4911 > Move module org.apache.xml-resolver from WildFly Core to WildFly > ---------------------------------------------------------------- > > Key: WFLY-11905 > URL: https://issues.redhat.com/browse/WFLY-11905 > Project: WildFly > Issue Type: Task > Components: Web Services > Reporter: Brian Stansberry > Assignee: Parul Sharma > Priority: Minor > > The org.apache.xml-resolver module is not used by WildFly Core. Only use is in full: > {code} > $ git grep xml-resolver | grep module.x > feature-pack/src/main/resources/modules/system/layers/base/org/apache/cxf/impl/main/module.xml: <module name="org.apache.xml-resolver" /> > feature-pack/src/main/resources/modules/system/layers/base/org/apache/cxf/main/module.xml: <module name="org.apache.xml-resolver" /> > feature-pack/src/main/resources/modules/system/layers/base/org/apache/cxf/services-sts/main/module.xml: <module name="org.apache.xml-resolver" /> > feature-pack/src/main/resources/modules/system/layers/base/org/apache/cxf/ws-security/main/module.xml: <module name="org.apache.xml-resolver" /> > {code} > Moving it will tidy things up some and perhaps avoid any special handling for it as Galleon layers work continues. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4911) Remove org.apache.xml-resolver (it has been moved to WildFly)

by Kabir Khan (Jira)

[ https://issues.redhat.com/browse/WFCORE-4911?page=com.atlassian.jira.plug... ] Kabir Khan moved WFLY-13347 to WFCORE-4911: ------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-4911 (was: WFLY-13347) Component/s: XML Frameworks (was: Web Services) > Remove org.apache.xml-resolver (it has been moved to WildFly) > ------------------------------------------------------------- > > Key: WFCORE-4911 > URL: https://issues.redhat.com/browse/WFCORE-4911 > Project: WildFly Core > Issue Type: Task > Components: XML Frameworks > Reporter: Brian Stansberry > Assignee: Parul Sharma > Priority: Minor > > The org.apache.xml-resolver module is not used by WildFly Core. Only use is in full: > {code} > $ git grep xml-resolver | grep module.x > feature-pack/src/main/resources/modules/system/layers/base/org/apache/cxf/impl/main/module.xml: <module name="org.apache.xml-resolver" /> > feature-pack/src/main/resources/modules/system/layers/base/org/apache/cxf/main/module.xml: <module name="org.apache.xml-resolver" /> > feature-pack/src/main/resources/modules/system/layers/base/org/apache/cxf/services-sts/main/module.xml: <module name="org.apache.xml-resolver" /> > feature-pack/src/main/resources/modules/system/layers/base/org/apache/cxf/ws-security/main/module.xml: <module name="org.apache.xml-resolver" /> > {code} > Moving it will tidy things up some and perhaps avoid any special handling for it as Galleon layers work continues. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13347) Remove org.apache.xml-resolver (it has been moved to WildFly)

by Kabir Khan (Jira)

Kabir Khan created WFLY-13347: --------------------------------- Summary: Remove org.apache.xml-resolver (it has been moved to WildFly) Key: WFLY-13347 URL: https://issues.redhat.com/browse/WFLY-13347 Project: WildFly Issue Type: Task Components: Web Services Reporter: Brian Stansberry Assignee: Parul Sharma The org.apache.xml-resolver module is not used by WildFly Core. Only use is in full: {code} $ git grep xml-resolver | grep module.x feature-pack/src/main/resources/modules/system/layers/base/org/apache/cxf/impl/main/module.xml: <module name="org.apache.xml-resolver" /> feature-pack/src/main/resources/modules/system/layers/base/org/apache/cxf/main/module.xml: <module name="org.apache.xml-resolver" /> feature-pack/src/main/resources/modules/system/layers/base/org/apache/cxf/services-sts/main/module.xml: <module name="org.apache.xml-resolver" /> feature-pack/src/main/resources/modules/system/layers/base/org/apache/cxf/ws-security/main/module.xml: <module name="org.apache.xml-resolver" /> {code} Moving it will tidy things up some and perhaps avoid any special handling for it as Galleon layers work continues. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5132) DMN Drools TCK runner updates

by Matteo Mortari (Jira)

[ https://issues.redhat.com/browse/DROOLS-5132?page=com.atlassian.jira.plug... ] Matteo Mortari commented on DROOLS-5132: ---------------------------------------- When resolving this jira, evaluate to move upstream DMN TCK Drools runner to use "typecheck" flag, instead of "strictconformance" flag > DMN Drools TCK runner updates > ----------------------------- > > Key: DROOLS-5132 > URL: https://issues.redhat.com/browse/DROOLS-5132 > Project: Drools > Issue Type: Task > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > > Activities on upstream DMN TCK is on hold as no meetings are being held -> no PRs merged on DMN TCK repo. > Hence this PR is pending: https://github.com/dmn-tck/tck/pull/360 > In that branch/PR, I am aligning with the original TCK intention that "errorResult" flag is an hint, but cannot be enforced, over the runners. > Example, in case > * the result from a DMN expression evaluation is null, > * the TCK expect a null, > * IFF TCK did not flagged as "errorResult", we no longer just fail simply because the Drools DMN engine reported an error (which was not indicated by the TCK test). > https://github.com/dmn-tck/tck/pull/360/files#diff-49ce6a21913fba22bc06e7... > Before, if the Drools DMN engine raised an error, but the TCK did not indicated as "errorResult" we were reporting a failure, even if the actual value was consistent with the expected one! > Now is aligned as explained. > Naturally, I've in parallel raised already PR to TCK to fix the test and to provide the proper "errorResult" hint. (https://github.com/dmn-tck/tck/pull/359) > Once the DMN-TCK-upstream PR for the Drools TCK runner is merged, the commit https://github.com/kiegroup/drools/commit/ca70199cf5edccf5261f153dde3296c... can be reverted. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5203) Make DMN Validator use generic V&V module for conflicting, misleading, masked and overlapping rows

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-5203?page=com.atlassian.jira.plug... ] Toni Rikkola commented on DROOLS-5203: -------------------------------------- [~jomarko] I'll use this ticket as the main ticket describing and delivering the PRs. > Make DMN Validator use generic V&V module for conflicting, misleading, masked and overlapping rows > -------------------------------------------------------------------------------------------------- > > Key: DROOLS-5203 > URL: https://issues.redhat.com/browse/DROOLS-5203 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > Goal is to merge and reuse the existing generic validator for the issue types in the title. The user should see no difference in the workbench use, but this will help us to reduce reduncancy and improve future V&V coverage for both DMN and DRL at the same time. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5203) Make DMN Validator use generic V&V module for conflicting, misleading, masked and overlapping rows

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-5203?page=com.atlassian.jira.plug... ] Toni Rikkola updated DROOLS-5203: --------------------------------- Tester: Jozef Marko > Make DMN Validator use generic V&V module for conflicting, misleading, masked and overlapping rows > -------------------------------------------------------------------------------------------------- > > Key: DROOLS-5203 > URL: https://issues.redhat.com/browse/DROOLS-5203 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > Goal is to merge and reuse the existing generic validator for the issue types in the title. The user should see no difference in the workbench use, but this will help us to reduce reduncancy and improve future V&V coverage for both DMN and DRL at the same time. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 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 April 2020