May 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JGRP-2344) Support UDP:PING on Quarkus

by Bela Ban (Jira)

[ https://issues.jboss.org/browse/JGRP-2344?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2344: --------------------------- Fix Version/s: 4.1.0 (was: 4.1.1) > Support UDP:PING on Quarkus > --------------------------- > > Key: JGRP-2344 > URL: https://issues.jboss.org/browse/JGRP-2344 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 4.1.0 > > > Currently, {{TCP:TCPPING}} is supported. Add the {{UDP:PING}} combo. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2343) Change in IPv4 versus IPv6 picking algorithm

by Bela Ban (Jira)

[ https://issues.jboss.org/browse/JGRP-2343?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2343: --------------------------- Fix Version/s: 4.1.0 (was: 4.1.1) > Change in IPv4 versus IPv6 picking algorithm > -------------------------------------------- > > Key: JGRP-2343 > URL: https://issues.jboss.org/browse/JGRP-2343 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 4.1.0 > > > When https://issues.jboss.org/browse/JGRP-2305 was implemented, IPv4 was favored unless {{java.net.preferIPv6Addresses}} was set. > However, this makes the following case fail: no {{java.net.preferXXX}} option is set and the configuration contains one or more IPv6 addresses, e.g. {{UDP bind_addr="::1"}}. > This will fail, as the new algorithm sets the stack type as IPv4 (it works when {{java.net.preferIPv6Addresses}} is set). > Change: > * Look at all IP addresses in a configuration > * If all addresses are IPv6 and the stack type is IPv4 (and IPv6 is available) -> switch to IPv6 as stack type > * If all addresses are IPv4 and the stack type is IPv6 (and IPv4 is available) -> switch to IPv4 stack type -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2344) Support UDP:PING on Quarkus

by Bela Ban (Jira)

Bela Ban created JGRP-2344: ------------------------------ Summary: Support UDP:PING on Quarkus Key: JGRP-2344 URL: https://issues.jboss.org/browse/JGRP-2344 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Fix For: 4.1.1 Currently, {{TCP:TCPPING}} is supported. Add the {{UDP:PING}} combo. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3968) Move all tests from JUnit 4 to JUnit Vintage

by Lukáš Petrovický (Jira)

Lukáš Petrovický created DROOLS-3968: ---------------------------------------- Summary: Move all tests from JUnit 4 to JUnit Vintage Key: DROOLS-3968 URL: https://issues.jboss.org/browse/DROOLS-3968 Project: Drools Issue Type: Task Reporter: Lukáš Petrovický Assignee: Lukáš Petrovický This is a fully backwards compatible change. There will be 0 lines of Java source code changed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3967) All Maven modules in all Submarine-related Maven repos need to be converted to JUnit 5

by Lukáš Petrovický (Jira)

Lukáš Petrovický created DROOLS-3967: ---------------------------------------- Summary: All Maven modules in all Submarine-related Maven repos need to be converted to JUnit 5 Key: DROOLS-3967 URL: https://issues.jboss.org/browse/DROOLS-3967 Project: Drools Issue Type: Epic Reporter: Lukáš Petrovický Assignee: Lukáš Petrovický Fix For: 8.0.0.Final -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3966) [DMN Designer] Included Models - Custom Data Types not loaded

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3966?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3966: -------------------------------- Priority: Blocker (was: Major) > [DMN Designer] Included Models - Custom Data Types not loaded > ------------------------------------------------------------- > > Key: DROOLS-3966 > URL: https://issues.jboss.org/browse/DROOLS-3966 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.21.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Blocker > Labels: drools-tools > > Issue spotted during DROOLS-3832 review. The issue is if the included node has type ref to custom data type. In this case the type ref is not loaded. On the other hand, if it the included node has type ref to built in data type (number, string ...), the type ref is loaded fine. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3966) [DMN Designer] Included Models - Custom Data Types not loaded

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3966?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3966: -------------------------------- Steps to Reproduce: # Create Dmn model: *one.dmn* # Declare there two input nodes *in-1* and *in-2* # Set type ref of *in-1* as *string* # Set type ref of *in-2* as some custom data type # Save *one.dmn* # Create *two.dmn* file and include the model *one.dmn* # In the *two.dmn* drag both *in-1* and *in-2* to canvas # Notice type ref in properties panel # For *in-1* is loaded correctly, for *in-2* is not loaded was: # Create Dmn model: *one.dmn* # Create there one decision node: *Decision-1* # Save the *one.dmn* file # Create Dmn model: *two.dmn* # In the *two.dmn* include the model *one.dmn* # In the *two.dmn* drag to canvas the *Decision-1* from *one.dmn* # Double click on *Decision-1* # Rename and confirm pop-up # The included node was renamed # Expected is included node is not renamed > [DMN Designer] Included Models - Custom Data Types not loaded > ------------------------------------------------------------- > > Key: DROOLS-3966 > URL: https://issues.jboss.org/browse/DROOLS-3966 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.21.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > > Issue spotted during DROOLS-3832 review. The issue is if the included node has type ref to custom data type. In this case the type ref is not loaded. On the other hand, if it the included node has type ref to built in data type (number, string ...), the type ref is loaded fine. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3966) [DMN Designer] Included Models - Custom Data Types not loaded

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3966?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3966: -------------------------------- Description: Issue spotted during DROOLS-3832 review. The issue is if the included node has type ref to custom data type. In this case the type ref is not loaded. On the other hand, if it the included node has type ref to built in data type (number, string ...), the type ref is loaded fine. (was: Issue spotted during DROOLS-3832 review. The included nodes should be read-only. However the included node can be renamed by double click on canvas.) > [DMN Designer] Included Models - Custom Data Types not loaded > ------------------------------------------------------------- > > Key: DROOLS-3966 > URL: https://issues.jboss.org/browse/DROOLS-3966 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.21.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > > Issue spotted during DROOLS-3832 review. The issue is if the included node has type ref to custom data type. In this case the type ref is not loaded. On the other hand, if it the included node has type ref to built in data type (number, string ...), the type ref is loaded fine. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3966) [DMN Designer] Included Models - Custom Data Types not loaded

by Jozef Marko (Jira)

Jozef Marko created DROOLS-3966: ----------------------------------- Summary: [DMN Designer] Included Models - Custom Data Types not loaded Key: DROOLS-3966 URL: https://issues.jboss.org/browse/DROOLS-3966 Project: Drools Issue Type: Bug Components: DMN Editor Affects Versions: 7.21.0.Final Reporter: Jozef Marko Assignee: Michael Anstis Issue spotted during DROOLS-3832 review. The included nodes should be read-only. However the included node can be renamed by double click on canvas. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3934) [DMN Designer] Included Models - Boxed Expressions does not work for imported DRG Elements

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3934?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3934: -------------------------------- Affects Version/s: 7.21.0.Final > [DMN Designer] Included Models - Boxed Expressions does not work for imported DRG Elements > ------------------------------------------------------------------------------------------ > > Key: DROOLS-3934 > URL: https://issues.jboss.org/browse/DROOLS-3934 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.21.0.Final > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > > Currently, users are not able to see a boxed expression from an imported node. > The DMNMarshaller must fetch information about external boxed expressions, and users must be able to see those boxed expressions in the DMN editor. > [UPDATE] > During checking DROOLS-3832 I was able to see expression of imported nodes, however I had to save and reopen the diagram. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 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 May 2019