July 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (LOGMGR-198) Closing attachments on a logger may result in an UnsupportedOperationException

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-198?page=com.atlassian.jira.plugin... ] James Perkins updated LOGMGR-198: --------------------------------- Fix Version/s: 2.1.4.Final > Closing attachments on a logger may result in an UnsupportedOperationException > ------------------------------------------------------------------------------ > > Key: LOGMGR-198 > URL: https://issues.jboss.org/browse/LOGMGR-198 > Project: JBoss Log Manager > Issue Type: Bug > Reporter: James Perkins > Assignee: James Perkins > Fix For: 2.1.4.Final > > > In some cases where a logger has a single attachment and the {{close()}} is invoked an {{UnsupportedOperationException}} may be thrown. This is due to the fact that a {{Collections.singletonMap()}} map is used which is immutable. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-3954) Upgrade jboss-logmanager from 2.1.3.Final to 2.1.4.Final

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3954?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-3954: ---------------------------------- Description: Upgrade {{org.jboss.logmanager:jboss-logmanager}} from 2.1.3.Final to 2.1.4.Final (was: Upgrade {{org.jboss.logmanager:jboss-logmanager}} from 2.1.2.Final to 2.1.3.Final) > Upgrade jboss-logmanager from 2.1.3.Final to 2.1.4.Final > -------------------------------------------------------- > > Key: WFCORE-3954 > URL: https://issues.jboss.org/browse/WFCORE-3954 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Fix For: 6.0.0.Alpha4 > > > Upgrade {{org.jboss.logmanager:jboss-logmanager}} from 2.1.3.Final to 2.1.4.Final -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-3954) Upgrade jboss-logmanager from 2.1.3.Final to 2.1.4.Final

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3954?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-3954: ---------------------------------- Git Pull Request: (was: https://github.com/wildfly/wildfly-core/pull/3380) > Upgrade jboss-logmanager from 2.1.3.Final to 2.1.4.Final > -------------------------------------------------------- > > Key: WFCORE-3954 > URL: https://issues.jboss.org/browse/WFCORE-3954 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Fix For: 6.0.0.Alpha4 > > > Upgrade {{org.jboss.logmanager:jboss-logmanager}} from 2.1.3.Final to 2.1.4.Final -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-3954) Upgrade jboss-logmanager from 2.1.3.Final to 2.1.4.Final

by James Perkins (JIRA)

James Perkins created WFCORE-3954: ------------------------------------- Summary: Upgrade jboss-logmanager from 2.1.3.Final to 2.1.4.Final Key: WFCORE-3954 URL: https://issues.jboss.org/browse/WFCORE-3954 Project: WildFly Core Issue Type: Component Upgrade Components: Logging Reporter: James Perkins Assignee: James Perkins Fix For: 6.0.0.Alpha4 Upgrade {{org.jboss.logmanager:jboss-logmanager}} from 2.1.2.Final to 2.1.3.Final -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (LOGMGR-198) Closing attachments on a logger may result in an UnsupportedOperationException

by James Perkins (JIRA)

James Perkins created LOGMGR-198: ------------------------------------ Summary: Closing attachments on a logger may result in an UnsupportedOperationException Key: LOGMGR-198 URL: https://issues.jboss.org/browse/LOGMGR-198 Project: JBoss Log Manager Issue Type: Bug Reporter: James Perkins Assignee: James Perkins In some cases where a logger has a single attachment and the {{close()}} is invoked an {{UnsupportedOperationException}} may be thrown. This is due to the fact that a {{Collections.singletonMap()}} map is used which is immutable. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ELY-1605) ELY05016: Unrecognized token for CCM mode cipher suites.

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/ELY-1605?page=com.atlassian.jira.plugin.s... ] Farah Juma reassigned ELY-1605: ------------------------------- Assignee: Farah Juma > ELY05016: Unrecognized token for CCM mode cipher suites. > -------------------------------------------------------- > > Key: ELY-1605 > URL: https://issues.jboss.org/browse/ELY-1605 > Project: WildFly Elytron > Issue Type: Bug > Components: SSL > Affects Versions: 1.3.3.Final > Reporter: Martin Choma > Assignee: Farah Juma > Priority: Critical > > {code} > /subsystem=elytron/server-ssl-context=a:add(cipher-suite-filter="TLS_RSA_WITH_AES_256_CCM,TLS_RSA_WITH_AES_128_CCM") > { > "outcome" => "failed", > "failure-description" => "WFLYELY01017: Invalid value for cipher-suite-filter. ELY05016: Unrecognized token \"TLS_RSA_WITH_AES_256_CCM\" in mechanism selection string \"TLS_RSA_WITH_AES_256_CCM,TLS_RSA_WITH_AES_128_CCM\"", > "rolled-back" => true > } > {code} > This is probably simply because MechanismDatabase.properties does not know CCM cipher suites. > Marking as Critical because both of ciphersuites from reproducer are listed as FIPS cipher suites for FIPS BC TLS [1] > These two ciphersuites (TLS_RSA_WITH_AES_256_CCM,TLS_RSA_WITH_AES_128_CCM) are introduced in [rfc6655|https://tools.ietf.org/html/rfc6655]. > [1] https://downloads.bouncycastle.org/fips-java/BC-FJA-(D)TLSUserGuide-1.0.5... > [2] https://tools.ietf.org/html/rfc6655 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2522) [DMN Designer] Palette css style

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2522?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-2522: -------------------------------- Labels: UX UXTeam (was: ) > [DMN Designer] Palette css style > -------------------------------- > > Key: DROOLS-2522 > URL: https://issues.jboss.org/browse/DROOLS-2522 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.8.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > Labels: UX, UXTeam > > The palette css styling has changed. There appeared margins between items in palette, what is probably not problem, however even when user click to this margin (to space between two item in palette) still some palette item is selected. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2522) [DMN Designer] Palette css style

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2522?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-2522: ------------------------------------- Adding [~srambach] > [DMN Designer] Palette css style > -------------------------------- > > Key: DROOLS-2522 > URL: https://issues.jboss.org/browse/DROOLS-2522 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.8.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > Labels: UX, UXTeam > > The palette css styling has changed. There appeared margins between items in palette, what is probably not problem, however even when user click to this margin (to space between two item in palette) still some palette item is selected. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2697) [DMN Designer] Improve readability of node labels

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2697?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-2697: ------------------------------------- [~karreiro] Seems like a good suggestion to me. Adding [~mstevens1] [~bdellasc] [~srambach] who work on the Process designer styles. > [DMN Designer] Improve readability of node labels > ------------------------------------------------- > > Key: DROOLS-2697 > URL: https://issues.jboss.org/browse/DROOLS-2697 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.8.0.Final > Reporter: Guilherme Carreiro > Assignee: Michael Anstis > > Node names are bold text without background rectangle and hence _merge_ into the node SVG. It'd be nicer to change font to regular and provide a (white) background rectangle to improve readability. See https://github.com/kiegroup/kie-wb-common/pull/1929#pullrequestreview-133... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-2656) PNGs for the toolbox icons for the different connector types.

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2656?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-2656: -------------------------------- Labels: IconRequest UX UXTeam VisualDesign drools-tools (was: IconRequest UX UXTeam VisualDesign) > PNGs for the toolbox icons for the different connector types. > ------------------------------------------------------------- > > Key: DROOLS-2656 > URL: https://issues.jboss.org/browse/DROOLS-2656 > Project: Drools > Issue Type: Sub-task > Reporter: Liz Clayton > Assignee: Brian Dellascio > Labels: IconRequest, UX, UXTeam, VisualDesign, drools-tools > > PNGs for the toolbox icons for the different connector types. > Their appearance can be seen in https://www.omg.org/spec/DMN/1.1/PDF (page 30, "Association", "Information Requirement", "Knowledge Requirement" and "Authority Requirement"). They'll only be used as icons on the toolbox (see screenshot attached). Could you please also remind me of the BAPL for the new "Node" SVGs (I'll need to make PNGs of those too for the same "toolbox" purpose.. unless UX have a tool to convert SVG to PNG?) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

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 2018