August 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-942) Fix jaeger installation in upstream pipeline

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-942?page=com.atlassian.jira.plugin.... ] Filip Brychta reassigned SWSQE-942: ----------------------------------- Assignee: Guilherme Baufaker Rêgo (was: Filip Brychta) > Fix jaeger installation in upstream pipeline > -------------------------------------------- > > Key: SWSQE-942 > URL: https://issues.jboss.org/browse/SWSQE-942 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Guilherme Baufaker Rêgo > Priority: Major > Labels: infrastructure > > Jaeger is not installed correctly in upstream pipeline -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4086) [DMN Designer] Search feature - DMN/GDT (7.5)

by Guilherme Gomes (Jira)

[ https://issues.jboss.org/browse/DROOLS-4086?page=com.atlassian.jira.plugi... ] Guilherme Gomes resolved DROOLS-4086. ------------------------------------- Resolution: Done > [DMN Designer] Search feature - DMN/GDT (7.5) > --------------------------------------------- > > Key: DROOLS-4086 > URL: https://issues.jboss.org/browse/DROOLS-4086 > Project: Drools > Issue Type: Epic > Components: DMN Editor > Affects Versions: 7.23.0.Final > Reporter: Yevgeniy Fomin > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Attachments: Example.png, Screen Shot 2019-05-30 at 5.14.30 PM.png > > > 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. Requirement > - The user would like to search for a text in the *Guided Decision Table editor*, in the *DMN graph*, and in the *DMN Decision Table* > - The search mechanism must return results even when users type only the part of search term. For example, if you type a text like 'test', the words 'testing', 'tester' must be displayed > h1. Documentation > - Replace picture of GDT and DMN editor where they become obsolete > 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, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4086) [DMN Designer] Search feature - DMN/GDT (7.5)

by Guilherme Gomes (Jira)

[ https://issues.jboss.org/browse/DROOLS-4086?page=com.atlassian.jira.plugi... ] Guilherme Gomes commented on DROOLS-4086: ----------------------------------------- Marking this JIRA as solved since the search feature is done, and DROOLS-4406/DROOLS-4407 represent only a visual enhancement. > [DMN Designer] Search feature - DMN/GDT (7.5) > --------------------------------------------- > > Key: DROOLS-4086 > URL: https://issues.jboss.org/browse/DROOLS-4086 > Project: Drools > Issue Type: Epic > Components: DMN Editor > Affects Versions: 7.23.0.Final > Reporter: Yevgeniy Fomin > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Attachments: Example.png, Screen Shot 2019-05-30 at 5.14.30 PM.png > > > 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. Requirement > - The user would like to search for a text in the *Guided Decision Table editor*, in the *DMN graph*, and in the *DMN Decision Table* > - The search mechanism must return results even when users type only the part of search term. For example, if you type a text like 'test', the words 'testing', 'tester' must be displayed > h1. Documentation > - Replace picture of GDT and DMN editor where they become obsolete > 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, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12409) Javaee8 BOM should include all spec artifacts directly

by Eduardo Martins (Jira)

[ https://issues.jboss.org/browse/WFLY-12409?page=com.atlassian.jira.plugin... ] Eduardo Martins edited comment on WFLY-12409 at 8/22/19 10:17 AM: ------------------------------------------------------------------ Another positive outcome of this change is that in dev javaee8 BOM is always in sync with server, while in the past it would only be correct whenever there was jboss spec import version upgrade, lasting only till next change in related spec artifacts in server. We don't re-release jboss specs as followup on every single change in server's dep management. So this also means more accurate early testing in both BOMs and Quickstarts... was (Author: emmartins): Another positive outcome of this change is that in dev javaee8 BOM is always in sync with server, while in the past it would only be correct whenever there was jboss spec import version upgrade, lasting only till next change in related spec artifacts in server. We don't re-release jboss specs as followup on every single change in server's dep management. So this also means more accurate early testing... > Javaee8 BOM should include all spec artifacts directly > ------------------------------------------------------ > > Key: WFLY-12409 > URL: https://issues.jboss.org/browse/WFLY-12409 > Project: WildFly > Issue Type: Enhancement > Components: BOM > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Priority: Major > > ... instead of importing through JBoss Specs BOM, which WildFly does not uses and thus its dependency management may be out of sync. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12409) Javaee8 BOM should include all spec artifacts directly

by Eduardo Martins (Jira)

[ https://issues.jboss.org/browse/WFLY-12409?page=com.atlassian.jira.plugin... ] Eduardo Martins commented on WFLY-12409: ---------------------------------------- Another positive outcome of this change is that in dev javaee8 BOM is always in sync with server, while in the past it would only be correct whenever there was jboss spec import version upgrade, lasting only till next change in related spec artifacts in server. We don't re-release jboss specs as followup on every single change in server's dep management. > Javaee8 BOM should include all spec artifacts directly > ------------------------------------------------------ > > Key: WFLY-12409 > URL: https://issues.jboss.org/browse/WFLY-12409 > Project: WildFly > Issue Type: Enhancement > Components: BOM > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Priority: Major > > ... instead of importing through JBoss Specs BOM, which WildFly does not uses and thus its dependency management may be out of sync. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12409) Javaee8 BOM should include all spec artifacts directly

by Eduardo Martins (Jira)

[ https://issues.jboss.org/browse/WFLY-12409?page=com.atlassian.jira.plugin... ] Eduardo Martins edited comment on WFLY-12409 at 8/22/19 10:16 AM: ------------------------------------------------------------------ Another positive outcome of this change is that in dev javaee8 BOM is always in sync with server, while in the past it would only be correct whenever there was jboss spec import version upgrade, lasting only till next change in related spec artifacts in server. We don't re-release jboss specs as followup on every single change in server's dep management. So this also means more accurate early testing... was (Author: emmartins): Another positive outcome of this change is that in dev javaee8 BOM is always in sync with server, while in the past it would only be correct whenever there was jboss spec import version upgrade, lasting only till next change in related spec artifacts in server. We don't re-release jboss specs as followup on every single change in server's dep management. > Javaee8 BOM should include all spec artifacts directly > ------------------------------------------------------ > > Key: WFLY-12409 > URL: https://issues.jboss.org/browse/WFLY-12409 > Project: WildFly > Issue Type: Enhancement > Components: BOM > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Priority: Major > > ... instead of importing through JBoss Specs BOM, which WildFly does not uses and thus its dependency management may be out of sync. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12412) Update org.apache.httpcomponents* to latest

by Tom Billiet (Jira)

Tom Billiet created WFLY-12412: ---------------------------------- Summary: Update org.apache.httpcomponents* to latest Key: WFLY-12412 URL: https://issues.jboss.org/browse/WFLY-12412 Project: WildFly Issue Type: Component Upgrade Reporter: Tom Billiet Assignee: Brian Stansberry apache httpcomponents is currently on org.apache.httpcomponents:httpclient:4.5.4 Which is almost 2 years old. We are seeing some AWS SDK issues because of that. https://github.com/aws/aws-sdk-java/issues/1919 Can it be upgraded to the latest version? -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12409) Javaee8 BOM should include all spec artifacts directly

by Eduardo Martins (Jira)

[ https://issues.jboss.org/browse/WFLY-12409?page=com.atlassian.jira.plugin... ] Eduardo Martins commented on WFLY-12409: ---------------------------------------- [~msvehla] it's just an internal impl enhancement, not a new feature or any changes to user. Importing the javaee8 BOM will provide the same dep management as before (Maven replaces any artifact import with such artefact's dep management). > Javaee8 BOM should include all spec artifacts directly > ------------------------------------------------------ > > Key: WFLY-12409 > URL: https://issues.jboss.org/browse/WFLY-12409 > Project: WildFly > Issue Type: Enhancement > Components: BOM > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Priority: Major > > ... instead of importing through JBoss Specs BOM, which WildFly does not uses and thus its dependency management may be out of sync. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4459) DMN Model popup stays on screen when navigating by keyboard to data type tab

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-4459?page=com.atlassian.jira.plugi... ] Michael Anstis reassigned DROOLS-4459: -------------------------------------- Assignee: Guilherme Gomes (was: Michael Anstis) > DMN Model popup stays on screen when navigating by keyboard to data type tab > ---------------------------------------------------------------------------- > > Key: DROOLS-4459 > URL: https://issues.jboss.org/browse/DROOLS-4459 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Reporter: Sarah Rambacher > Assignee: Guilherme Gomes > Priority: Major > Attachments: screenshot-1.png > > > If the user has a popup open, the popup remains on the screen and active even when the user switches to another tab via the keyboard. > !screenshot-1.png|thumbnail! -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12409) Javaee8 BOM should include all spec artifacts directly

by Martin Svehla (Jira)

[ https://issues.jboss.org/browse/WFLY-12409?page=com.atlassian.jira.plugin... ] Martin Svehla commented on WFLY-12409: -------------------------------------- [~emmartins] this is enhancement on product side, where is the relevant EAP7 issue? > Javaee8 BOM should include all spec artifacts directly > ------------------------------------------------------ > > Key: WFLY-12409 > URL: https://issues.jboss.org/browse/WFLY-12409 > Project: WildFly > Issue Type: Enhancement > Components: BOM > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Priority: Major > > ... instead of importing through JBoss Specs BOM, which WildFly does not uses and thus its dependency management may be out of sync. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 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