August 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4579) Upgrade jboss-logging from 2.4.0.Final to 2.4.1.Final

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFCORE-4579?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-4579: ---------------------------------- Summary: Upgrade jboss-logging from 2.4.0.Final to 2.4.1.Final (was: Upgrade jboss-logging from 3.4.0.Final to 3.4.1.Final) > Upgrade jboss-logging from 2.4.0.Final to 2.4.1.Final > ----------------------------------------------------- > > Key: WFCORE-4579 > URL: https://issues.jboss.org/browse/WFCORE-4579 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Logging > Affects Versions: 10.0.0.Beta2 > Reporter: Chao Wang > Assignee: James Perkins > Priority: Major > Labels: downstream_dependency > > Upgrade org.jboss.logging:jboss-logging from 3.4.0.Final to 3.4.1.Final. > https://github.com/jboss-logging/jboss-logging/compare/3.4.0.Final...3.4.... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-259) Named filters throw an IllegalArgumentException if they are embedded in an expression

by James Perkins (Jira)

[ https://issues.jboss.org/browse/LOGMGR-259?page=com.atlassian.jira.plugin... ] James Perkins updated LOGMGR-259: --------------------------------- Fix Version/s: 1.3.3.Final 1.4.4.Final 1.5.10.Final 2.0.12.Final 2.1.14.Final 2.2.0.Final > Named filters throw an IllegalArgumentException if they are embedded in an expression > ------------------------------------------------------------------------------------- > > Key: LOGMGR-259 > URL: https://issues.jboss.org/browse/LOGMGR-259 > Project: JBoss Log Manager > Issue Type: Bug > Reporter: James Perkins > Assignee: James Perkins > Priority: Major > Fix For: 1.3.3.Final, 1.4.4.Final, 1.5.10.Final, 2.0.12.Final, 2.1.14.Final, 2.2.0.Final > > > A named filter, one that was added via the configuration API, will throw an {{IllegalArgumentException}} if they are embedded in a filter expression. > The following should be a valid expression as "all" is a changed filter and "test" is the manually created filter. > {code} > logContextConfiguration.addFilterConfiguration(null, "org.jboss.filter.Test", "test"); > logContextConfiguration.getLoggerConfiguration("").setFilter("all(test)"); > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-259) Named filters throw an IllegalArgumentException if they are embedded in an expression

by James Perkins (Jira)

[ https://issues.jboss.org/browse/LOGMGR-259?page=com.atlassian.jira.plugin... ] James Perkins updated LOGMGR-259: --------------------------------- Git Pull Request: https://github.com/jboss-logging/jboss-logmanager/pull/272, https://github.com/jboss-logging/jboss-logmanager/pull/273, https://github.com/jboss-logging/jboss-logmanager/pull/274, https://github.com/jboss-logging/jboss-logmanager/pull/275, https://github.com/jboss-logging/jboss-logmanager/pull/276 > Named filters throw an IllegalArgumentException if they are embedded in an expression > ------------------------------------------------------------------------------------- > > Key: LOGMGR-259 > URL: https://issues.jboss.org/browse/LOGMGR-259 > Project: JBoss Log Manager > Issue Type: Bug > Reporter: James Perkins > Assignee: James Perkins > Priority: Major > > A named filter, one that was added via the configuration API, will throw an {{IllegalArgumentException}} if they are embedded in a filter expression. > The following should be a valid expression as "all" is a changed filter and "test" is the manually created filter. > {code} > logContextConfiguration.addFilterConfiguration(null, "org.jboss.filter.Test", "test"); > logContextConfiguration.getLoggerConfiguration("").setFilter("all(test)"); > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-259) Named filters throw an IllegalArgumentException if they are embedded in an expression

by James Perkins (Jira)

James Perkins created LOGMGR-259: ------------------------------------ Summary: Named filters throw an IllegalArgumentException if they are embedded in an expression Key: LOGMGR-259 URL: https://issues.jboss.org/browse/LOGMGR-259 Project: JBoss Log Manager Issue Type: Bug Reporter: James Perkins Assignee: James Perkins A named filter, one that was added via the configuration API, will throw an {{IllegalArgumentException}} if they are embedded in a filter expression. The following should be a valid expression as "all" is a changed filter and "test" is the manually created filter. {code} logContextConfiguration.addFilterConfiguration(null, "org.jboss.filter.Test", "test"); logContextConfiguration.getLoggerConfiguration("").setFilter("all(test)"); {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12347) Upgrade jgroups-kubernetes to 1.0.12.Final

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-12347?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-12347: ---------------------------------- Fix Version/s: 18.0.0.Beta1 > Upgrade jgroups-kubernetes to 1.0.12.Final > ------------------------------------------ > > Key: WFLY-12347 > URL: https://issues.jboss.org/browse/WFLY-12347 > Project: WildFly > Issue Type: Component Upgrade > Components: Clustering > Affects Versions: 17.0.1.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > Fix For: 18.0.0.Beta1 > > > Adds support for grouping pods by {{metadata.labels.pod-template-hash}} during rolling update. > Tag/changelog > https://github.com/jgroups-extras/jgroups-kubernetes/tree/1.0.12.Final -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12347) Upgrade jgroups-kubernetes to 1.0.12.Final

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-12347?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-12347: ---------------------------------- Issue Type: Component Upgrade (was: Bug) > Upgrade jgroups-kubernetes to 1.0.12.Final > ------------------------------------------ > > Key: WFLY-12347 > URL: https://issues.jboss.org/browse/WFLY-12347 > Project: WildFly > Issue Type: Component Upgrade > Components: Clustering > Affects Versions: 17.0.1.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > Fix For: 18.0.0.Beta1 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12347) Upgrade jgroups-kubernetes to 1.0.12.Final

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-12347?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-12347: ---------------------------------- Description: Adds support for grouping pods by {{metadata.labels.pod-template-hash}} during rolling update. Tag/changelog https://github.com/jgroups-extras/jgroups-kubernetes/tree/1.0.12.Final was:https://github.com/jgroups-extras/jgroups-kubernetes/tree/1.0.12.Final adds support for grouping pods by {{metadata.labels.pod-template-hash}} during rolling update. > Upgrade jgroups-kubernetes to 1.0.12.Final > ------------------------------------------ > > Key: WFLY-12347 > URL: https://issues.jboss.org/browse/WFLY-12347 > Project: WildFly > Issue Type: Component Upgrade > Components: Clustering > Affects Versions: 17.0.1.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > Fix For: 18.0.0.Beta1 > > > Adds support for grouping pods by {{metadata.labels.pod-template-hash}} during rolling update. > Tag/changelog > https://github.com/jgroups-extras/jgroups-kubernetes/tree/1.0.12.Final -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12347) Upgrade jgroups-kubernetes to 1.0.12.Final

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/WFLY-12347?page=com.atlassian.jira.plugin... ] Radoslav Husar updated WFLY-12347: ---------------------------------- Description: https://github.com/jgroups-extras/jgroups-kubernetes/tree/1.0.12.Final adds support for grouping pods by {{metadata.labels.pod-template-hash}} during rolling update. > Upgrade jgroups-kubernetes to 1.0.12.Final > ------------------------------------------ > > Key: WFLY-12347 > URL: https://issues.jboss.org/browse/WFLY-12347 > Project: WildFly > Issue Type: Component Upgrade > Components: Clustering > Affects Versions: 17.0.1.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > Fix For: 18.0.0.Beta1 > > > https://github.com/jgroups-extras/jgroups-kubernetes/tree/1.0.12.Final adds support for grouping pods by {{metadata.labels.pod-template-hash}} during rolling update. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12347) Upgrade jgroups-kubernetes to 1.0.12.Final

by Radoslav Husar (Jira)

Radoslav Husar created WFLY-12347: ------------------------------------- Summary: Upgrade jgroups-kubernetes to 1.0.12.Final Key: WFLY-12347 URL: https://issues.jboss.org/browse/WFLY-12347 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 17.0.1.Final Reporter: Radoslav Husar Assignee: Radoslav Husar -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4304) UX design: Keyboard shortcuts for Find feature in GDST/DMN 7.5

by Guilherme Gomes (Jira)

[ https://issues.jboss.org/browse/DROOLS-4304?page=com.atlassian.jira.plugi... ] Guilherme Gomes commented on DROOLS-4304: ----------------------------------------- [~uxdlc] The slide 10 is enough. We can mark the JIRA as Done. Thank you! > UX design: Keyboard shortcuts for Find feature in GDST/DMN 7.5 > -------------------------------------------------------------- > > Key: DROOLS-4304 > URL: https://issues.jboss.org/browse/DROOLS-4304 > Project: Drools > Issue Type: Story > Components: DMN Editor > Affects Versions: 7.23.0.Final > Reporter: Elizabeth Clayton > Assignee: Sarah Rambacher > Priority: Major > Labels: UX, UXTeam, drools-tools > > This is a community epic for the [BAPL-1279|https://issues.jboss.org/browse/BAPL-1279]. The epic was created according to the [definition of ready|https://docs.google.com/document/d/1WKv_Cx7jCts7gCQCGt_323ANH_H7dv4...] that advices what needs to be agreed before each feature implementation. > h1. Requirements > See referenced document: https://docs.google.com/document/d/1VX_KhMhPgs2ZoOv7_jpfbl2o2-Y528UEImGk9... > h1. Documentation > Keyboard recommendations to be documented at: https://docs.google.com/presentation/d/1itceVe225mMtR55pqB-llpLNdU6kq4TBi... > h1. Acceptance test > - Enter to large amount of data in search box > - Search is possible when you type only the part of indicated word. For example, if you type text like 'test', the words 'testing', 'tester' should be displayed. > - Searching for non-existing result > - Result appearing once > - Result appearing multiple times > - Set of inputs: > *- A-Z > *- a-z > *- 0-9 > *- Symbols: } { ] [ ) ( ~ ! @ # $ % ^ & ` | \ : " ; ' < > ? , . ⁄ - + > *- Blank spaces -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 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 August 2019