January 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4939) Add generics to declared types

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-4939?page=com.atlassian.jira.plug... ] Mario Fusco resolved DROOLS-4939. --------------------------------- Resolution: Done Implemented by https://github.com/kiegroup/drools/commit/11d9533564b410d50fd22319715de5e... > Add generics to declared types > ------------------------------ > > Key: DROOLS-4939 > URL: https://issues.redhat.com/browse/DROOLS-4939 > Project: Drools > Issue Type: Feature Request > Reporter: Edoardo Vacchi > Assignee: Mario Fusco > Priority: Major > Labels: drools-core > > add support to declare generic types (e.g. List<Foo>) in declared types > e.g. > {code} > declare Baz > List<Foo> foos > end > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

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

by Emmanuel Hugonnet (Jira)

Emmanuel Hugonnet created WFCORE-4808: ----------------------------------------- Summary: Upgrade JGit to 5.6.0.201912101111-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 Updating JGit and all its dependencies -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2436) Diagnostics: enable TCP by default

by Bela Ban (Jira)

Bela Ban created JGRP-2436: ------------------------------ Summary: Diagnostics: enable TCP by default Key: JGRP-2436 URL: https://issues.redhat.com/browse/JGRP-2436 Project: JGroups Issue Type: Task Reporter: Bela Ban Assignee: Bela Ban Fix For: 5.0, 4.2.0 Set {{diag_enable_tcp}} to true by default; a lot of deployments happen in the cloud today, and if we don't enable this, {{probe -addr ADDR}} will only retturn a response from the local member. This will open a UDP *and* TCP diagnostics socket, but if {{enable_diagnostics}} is false, then no socket will be opened -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13004) Upgrade jgroups-kubernetes to 1.0.14.Final

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFLY-13004?page=com.atlassian.jira.plugi... ] Radoslav Husar updated WFLY-13004: ---------------------------------- Priority: Optional (was: Major) > Upgrade jgroups-kubernetes to 1.0.14.Final > ------------------------------------------ > > Key: WFLY-13004 > URL: https://issues.redhat.com/browse/WFLY-13004 > Project: WildFly > Issue Type: Component Upgrade > Components: Clustering > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Optional > > No functional changes. > https://github.com/jgroups-extras/jgroups-kubernetes/compare/1.0.14.Final... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13004) Upgrade jgroups-kubernetes to 1.0.14.Final

by Radoslav Husar (Jira)

Radoslav Husar created WFLY-13004: ------------------------------------- Summary: Upgrade jgroups-kubernetes to 1.0.14.Final Key: WFLY-13004 URL: https://issues.redhat.com/browse/WFLY-13004 Project: WildFly Issue Type: Component Upgrade Components: Clustering Reporter: Radoslav Husar Assignee: Radoslav Husar No functional changes. https://github.com/jgroups-extras/jgroups-kubernetes/compare/1.0.14.Final... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4807) Add option to route log messages based on the current thread's class loader

by James Perkins (Jira)

[ https://issues.redhat.com/browse/WFCORE-4807?page=com.atlassian.jira.plug... ] James Perkins moved EAP7-1421 to WFCORE-4807: --------------------------------------------- Project: WildFly Core (was: JBoss EAP Planning for version 7 and above) Key: WFCORE-4807 (was: EAP7-1421) Issue Type: Feature Request (was: Requirement) Workflow: GIT Pull Request workflow (was: EAP Agile Workflow 2.0) Component/s: Logging (was: Logging) EAP Testing By: (was: Engineering) EAP PT Pre-Checked (PC): (was: TODO) Target Release: (was: 7.4.0.GA) EAP PT Community Docs (CD): (was: TODO) EAP PT Product Docs (PD): (was: New) EAP PT Test Dev (TD): (was: TODO) EAP PT Docs Analysis (DA): (was: TODO) EAP PT Test Plan (TP): (was: TODO) EAP PT Analysis Document (AD): (was: TODO) > Add option to route log messages based on the current thread's class loader > --------------------------------------------------------------------------- > > Key: WFCORE-4807 > URL: https://issues.redhat.com/browse/WFCORE-4807 > Project: WildFly Core > Issue Type: Feature Request > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Major > > Currently any modules that log generally log onto the system log context. In some cases, see WFCORE-3376, loggers in modules may be created on the wrong log context. This means logs may be routed to the wrong log context. > LOGMR-264 can introduce a way to route log messages based on the log context. This would allow messages from modules to be routed to deployment specific log contexts. It would also introduce a change in behavior which is the reason for an RFE. A new attribute should be introduce to disable the new routing and allow the old behavior. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13003) Support the SameSite cookie attribute

by Stuart Douglas (Jira)

Stuart Douglas created WFLY-13003: ------------------------------------- Summary: Support the SameSite cookie attribute Key: WFLY-13003 URL: https://issues.redhat.com/browse/WFLY-13003 Project: WildFly Issue Type: Feature Request Components: Web (Undertow) Reporter: Stuart Douglas Assignee: Flavia Rainone Chrome 80 is going to significantly change how cookies are handled, as per this notice at [1], with a bit of an explanation of what the same site attribute means at [2]. At the moment the Servlet specification has no way of setting this particular attribute, and it is not possible to configure it via container specific configuration in WildFly at present (it can only be done by writing some Undertow specific code). I propose we add a same-site-cookie-attribute predicated handler to undertow, which takes an optional cookie name regex, and the value for the attribute to set. This would allow users to configure the SameSite attribute based on cookie name, and also potentially based on any other attributes including user agent, as it sounds like some browsers may have bugs that means this might need to be set on a per user agent basis. [1] https://www.chromestatus.com/feature/5088147346030592 [2] https://web.dev/samesite-cookies-explained/ -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4806) Upgrade jboss-logmanager from 2.1.14.Final to 2.2.0.Ginal

by James Perkins (Jira)

James Perkins created WFCORE-4806: ------------------------------------- Summary: Upgrade jboss-logmanager from 2.1.14.Final to 2.2.0.Ginal Key: WFCORE-4806 URL: https://issues.redhat.com/browse/WFCORE-4806 Project: WildFly Core Issue Type: Component Upgrade Components: Logging Reporter: James Perkins Assignee: James Perkins Upgrade the {{org.jboss.logmanager:jboss-logmanager}} to 2.2.0.Final. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4806) Upgrade jboss-logmanager from 2.1.14.Final to 2.2.0.Final

by James Perkins (Jira)

[ https://issues.redhat.com/browse/WFCORE-4806?page=com.atlassian.jira.plug... ] James Perkins updated WFCORE-4806: ---------------------------------- Summary: Upgrade jboss-logmanager from 2.1.14.Final to 2.2.0.Final (was: Upgrade jboss-logmanager from 2.1.14.Final to 2.2.0.Ginal) > Upgrade jboss-logmanager from 2.1.14.Final to 2.2.0.Final > --------------------------------------------------------- > > Key: WFCORE-4806 > URL: https://issues.redhat.com/browse/WFCORE-4806 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Major > > Upgrade the {{org.jboss.logmanager:jboss-logmanager}} to 2.2.0.Final. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4778) [DMN Designer] Multiple DRDs Support (Backlog)

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-4778?page=com.atlassian.jira.plug... ] Michael Anstis commented on DROOLS-4778: ---------------------------------------- [~uxdlc] [~porcelli] [~tirelli] FYI I raised https://issues.redhat.com/browse/KOGITO-937 to handle positioning of the Decision Navigator in different _channels_. > [DMN Designer] Multiple DRDs Support (Backlog) > ---------------------------------------------- > > Key: DROOLS-4778 > URL: https://issues.redhat.com/browse/DROOLS-4778 > Project: Drools > Issue Type: Epic > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > > This is an umbrella for all JIRAs related to the Multiple DRDs Support feature. -- 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 January 2020