August 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-397) Kiali Checker Not Working - Not Handling SSL

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/SWSQE-397?page=com.atlassian.jira.plugin.... ] Matt Mahoney reassigned SWSQE-397: ---------------------------------- Assignee: Sunil kondkar (was: Michael Foley) > Kiali Checker Not Working - Not Handling SSL > -------------------------------------------- > > Key: SWSQE-397 > URL: https://issues.jboss.org/browse/SWSQE-397 > Project: Kiali QE > Issue Type: Bug > Reporter: Matt Mahoney > Assignee: Sunil kondkar > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-397) Kiali Checker Not Working - Not Handling SSL

by Matt Mahoney (JIRA)

Matt Mahoney created SWSQE-397: ---------------------------------- Summary: Kiali Checker Not Working - Not Handling SSL Key: SWSQE-397 URL: https://issues.jboss.org/browse/SWSQE-397 Project: Kiali QE Issue Type: Bug Reporter: Matt Mahoney Assignee: Michael Foley -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10784) WeldStartCompletionService failed when optional components not installed

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-10784?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFLY-10784: ----------------------------------------- [~mkouba] You're right. Sorry, and thanks for realizing this. Another possibility is to use a org.jboss.msc.service.StabilityMonitor in a Phase.CLEANUP DUP or perhaps better in WeldStartCompletionService.start. Instead of depending on services you register their ServiceController with the StabilityMonitor and then awaitStability. Doing it in a service means that other DUPs in that same Phase won't have to wait to execute until stability is reached. It shouldn't be done in a Phase.INSTALL DUP. > WeldStartCompletionService failed when optional components not installed > ------------------------------------------------------------------------ > > Key: WFLY-10784 > URL: https://issues.jboss.org/browse/WFLY-10784 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Affects Versions: 12.0.0.Final, 13.0.0.Final > Reporter: Alexander Kudrevatykh > Assignee: Matej Novotny > Attachments: arq-test.tar.xz > > > WebComponents are optional and fail in initialising it not causes fail of deployment, but when starting EAR application with included WAR fail in deployment since Wildfly 12 because WeldStartCompletionService depends on all components regardless of their type -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-396) Kiali UI Tests to support SSL

by Hayk Hovsepyan (JIRA)

Hayk Hovsepyan created SWSQE-396: ------------------------------------ Summary: Kiali UI Tests to support SSL Key: SWSQE-396 URL: https://issues.jboss.org/browse/SWSQE-396 Project: Kiali QE Issue Type: QE Task Reporter: Hayk Hovsepyan Assignee: Hayk Hovsepyan Priority: Blocker -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-378) Random TAG is being generated on deploying from kiali/kiali

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/SWSQE-378?page=com.atlassian.jira.plugin.... ] Hayk Hovsepyan resolved SWSQE-378. ---------------------------------- Resolution: Done returned back random tag for PR/branch builds > Random TAG is being generated on deploying from kiali/kiali > ----------------------------------------------------------- > > Key: SWSQE-378 > URL: https://issues.jboss.org/browse/SWSQE-378 > Project: Kiali QE > Issue Type: Bug > Reporter: Guilherme Baufaker Rêgo > Assignee: Hayk Hovsepyan > > The random tag was included because the images weren't been overridden, but when we are deploying from "kiali/kiali" the exactly tag should be matched > Example: Using Docker tag v0.6.0YWZk from Docker Repo docker.io/kiali/kiali from (http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/Kiali-on-Openshi...) > YWZk is the random component. > This need to be switched when are using kialiqe/kiali -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2876) Data Type list icons - visual design

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2876?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-2876: ------------------------------------- [~karreiro] Thanks for the definitions! Could you list the font awesome icons that we're currently using? I forgot which fa-icons we decided to use. [~bdellasc] could review and let us know if they're OK. > Data Type list icons - visual design > ------------------------------------ > > Key: DROOLS-2876 > URL: https://issues.jboss.org/browse/DROOLS-2876 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Brian Dellascio > Labels: UX, UXTeam, VisualDesign, drools-tools > Attachments: Screen Shot 2018-08-10 at 9.22.23 AM.png > > > DMN Data Types dialog uses the following PF pattern: https://www.patternfly.org/pattern-library/content-views/tree-list-view/. As such it includes a list. We need list icons for two types of list items: > - Simple custom Data Types (basically means not nested date types) > - Structured custom Data Types (basically means nested data types) > Design documented in detail at: https://issues.jboss.org/browse/DROOLS-2787 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2876) Data Type list icons - visual design

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2876?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-2876: -------------------------------- Sprint: 2018 Week 36-38 > Data Type list icons - visual design > ------------------------------------ > > Key: DROOLS-2876 > URL: https://issues.jboss.org/browse/DROOLS-2876 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Brian Dellascio > Labels: UX, UXTeam, VisualDesign, drools-tools > Attachments: Screen Shot 2018-08-10 at 9.22.23 AM.png > > > DMN Data Types dialog uses the following PF pattern: https://www.patternfly.org/pattern-library/content-views/tree-list-view/. As such it includes a list. We need list icons for two types of list items: > - Simple custom Data Types (basically means not nested date types) > - Structured custom Data Types (basically means nested data types) > Design documented in detail at: https://issues.jboss.org/browse/DROOLS-2787 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2728) UX for custom data-types

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2728?page=com.atlassian.jira.plugi... ] Liz Clayton edited comment on DROOLS-2728 at 8/29/18 2:25 PM: -------------------------------------------------------------- [~tirelli] [~karreiro] [~manstis] I believe the resolution of the last jiras (2874 & 2888) closes out this particular UX Epic. So I'm going to go ahead and mark this as Resolved as well. As [~tirelli] suggested, I will create new jiras for future iterations and enhancements. Thanks! Oops, nevermind - there are 2 stories (Visual Design and CSS) within the Epic that are still open. was (Author: uxdlc): [~tirelli] [~karreiro] [~manstis] I believe the resolution of the last jiras (2874 & 2888) closes out this particular UX Epic. So I'm going to go ahead and mark this as Resolved as well. As [~tirelli] suggested, I will create new jiras for future iterations and enhancements. Thanks! > UX for custom data-types > ------------------------ > > Key: DROOLS-2728 > URL: https://issues.jboss.org/browse/DROOLS-2728 > Project: Drools > Issue Type: Epic > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: UX, UXTeam, drools-tools > Attachments: DROOLS-2700.png, Screen Shot 2018-07-13 at 11.26.43 AM.png, Screen Shot 2018-07-13 at 11.34.15 AM.png, nested.png, prop-panel.png > > > As a practitioner I want to be able to: > * select an existing data type > * create a simple or structured data type > * create a “compound” (or complex) data type, easily. > *  expand/collapse views of compound data types, so that I can___ > *  navigate between levels in a compound data type, so that I can___ > * edit an existing data type > * remove an existing data type >  …so that I can use the data type when creating a decision related asset. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2728) UX for custom data-types

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2728?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-2728: ------------------------------------- [~tirelli] [~karreiro] [~manstis] I believe the resolution of the last jiras (2874 & 2888) closes out this particular UX Epic. So I'm going to go ahead and mark this as Resolved as well. As [~tirelli] suggested, I will create new jiras for future iterations and enhancements. Thanks! > UX for custom data-types > ------------------------ > > Key: DROOLS-2728 > URL: https://issues.jboss.org/browse/DROOLS-2728 > Project: Drools > Issue Type: Epic > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: UX, UXTeam, drools-tools > Attachments: DROOLS-2700.png, Screen Shot 2018-07-13 at 11.26.43 AM.png, Screen Shot 2018-07-13 at 11.34.15 AM.png, nested.png, prop-panel.png > > > As a practitioner I want to be able to: > * select an existing data type > * create a simple or structured data type > * create a “compound” (or complex) data type, easily. > *  expand/collapse views of compound data types, so that I can___ > *  navigate between levels in a compound data type, so that I can___ > * edit an existing data type > * remove an existing data type >  …so that I can use the data type when creating a decision related asset. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBMETA-410) IIOPMetaDataParser must support both legacy and new parsing routines

by Richard Opalka (JIRA)

[ https://issues.jboss.org/browse/JBMETA-410?page=com.atlassian.jira.plugin... ] Richard Opalka updated JBMETA-410: ---------------------------------- Git Pull Request: https://github.com/jboss/metadata/pull/124 > IIOPMetaDataParser must support both legacy and new parsing routines > -------------------------------------------------------------------- > > Key: JBMETA-410 > URL: https://issues.jboss.org/browse/JBMETA-410 > Project: JBoss Metadata > Issue Type: Bug > Components: ejb > Reporter: Richard Opalka > Assignee: Richard Opalka > Fix For: 11.0.1.Final > > > With fix of [BZ-1192591] legacy iiop config parsing routine was discontinued. > Due to backward compatibility issues we need to support both legacy and > new parsing routines. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2018