February 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELYWEB-93) Upgrade WildFly Elytron to 1.11.2.Final

by Darran Lofthouse (Jira)

Darran Lofthouse created ELYWEB-93: -------------------------------------- Summary: Upgrade WildFly Elytron to 1.11.2.Final Key: ELYWEB-93 URL: https://issues.redhat.com/browse/ELYWEB-93 Project: Elytron Web Issue Type: Component Upgrade Components: Parent Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.8.0.CR1 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELYWEB-92) Upgrade WildFly Common to 1.5.3.Final

by Darran Lofthouse (Jira)

Darran Lofthouse created ELYWEB-92: -------------------------------------- Summary: Upgrade WildFly Common to 1.5.3.Final Key: ELYWEB-92 URL: https://issues.redhat.com/browse/ELYWEB-92 Project: Elytron Web Issue Type: Component Upgrade Components: Parent Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.8.0.CR1 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4994) Highlight better that expression and graphical collection editor are different

by Elizabeth Clayton (Jira)

[ https://issues.redhat.com/browse/DROOLS-4994?page=com.atlassian.jira.plug... ] Elizabeth Clayton updated DROOLS-4994: -------------------------------------- Sprint: 2020 Week 04-06 (from Jan 20) > Highlight better that expression and graphical collection editor are different > ------------------------------------------------------------------------------ > > Key: DROOLS-4994 > URL: https://issues.redhat.com/browse/DROOLS-4994 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Affects Versions: 7.32.0.Final > Reporter: Anna Dupliak > Assignee: Elizabeth Clayton > Priority: Minor > Labels: UX, UXTeam, drools-tools > Attachments: Screenshot from 2020-01-17 13-56-02.png, Screenshot from 2020-01-17 13-56-10.png, collection-infotip.png, collection-inline.png > > > Revealed during testing of https://issues.redhat.com/browse/DROOLS-4698 > We need a way to tell a user that using the guided editor, you can only add one ore more check to the collection as list of conditions while in the expression user can write whatever he wants so the semantic is completely custom. > Suggested solution: > - to explain the difference directly in the popup, somewhere close to radio buttons create/define. > Example: > [1] > !Screenshot from 2020-01-17 13-56-02.png|thumbnail! > [2] > !Screenshot from 2020-01-17 13-56-10.png|thumbnail! > How that works now: > Each element defined in the graphical editor will be considered as a check to perform: the first screenshot means "check if an element equals to 2 exists in the collection" while the expression means "is the list equals to [2] list?" > What expression should be to make test pass: > (2 in ?) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4994) Highlight better that expression and graphical collection editor are different

by Elizabeth Clayton (Jira)

[ https://issues.redhat.com/browse/DROOLS-4994?page=com.atlassian.jira.plug... ] Elizabeth Clayton updated DROOLS-4994: -------------------------------------- Labels: UX UXTeam drools-tools (was: drools-tools) > Highlight better that expression and graphical collection editor are different > ------------------------------------------------------------------------------ > > Key: DROOLS-4994 > URL: https://issues.redhat.com/browse/DROOLS-4994 > Project: Drools > Issue Type: Enhancement > Components: Scenario Simulation and Testing > Affects Versions: 7.32.0.Final > Reporter: Anna Dupliak > Assignee: Elizabeth Clayton > Priority: Minor > Labels: UX, UXTeam, drools-tools > Attachments: Screenshot from 2020-01-17 13-56-02.png, Screenshot from 2020-01-17 13-56-10.png, collection-infotip.png, collection-inline.png > > > Revealed during testing of https://issues.redhat.com/browse/DROOLS-4698 > We need a way to tell a user that using the guided editor, you can only add one ore more check to the collection as list of conditions while in the expression user can write whatever he wants so the semantic is completely custom. > Suggested solution: > - to explain the difference directly in the popup, somewhere close to radio buttons create/define. > Example: > [1] > !Screenshot from 2020-01-17 13-56-02.png|thumbnail! > [2] > !Screenshot from 2020-01-17 13-56-10.png|thumbnail! > How that works now: > Each element defined in the graphical editor will be considered as a check to perform: the first screenshot means "check if an element equals to 2 exists in the collection" while the expression means "is the list equals to [2] list?" > What expression should be to make test pass: > (2 in ?) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-1928) Upgrade WildFly Common to 1.5.3.Final

by Darran Lofthouse (Jira)

Darran Lofthouse created ELY-1928: ------------------------------------- Summary: Upgrade WildFly Common to 1.5.3.Final Key: ELY-1928 URL: https://issues.redhat.com/browse/ELY-1928 Project: WildFly Elytron Issue Type: Component Upgrade Components: Build Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.11.3.CR1 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1063) Fix incorrect parameter types

by Filip Brychta (Jira)

[ https://issues.redhat.com/browse/SWSQE-1063?page=com.atlassian.jira.plugi... ] Filip Brychta updated SWSQE-1063: --------------------------------- Description: Some jobs are passing boolean params as strings, we need to fix that. It's causing warnings like: The parameter 'DELETE_MAISTRA_OPERATOR' did not have the type expected by clean-environment. Converting to Boolean Parameter. was:Some jobs are passing boolean params as strings, we need to fix that. > Fix incorrect parameter types > ----------------------------- > > Key: SWSQE-1063 > URL: https://issues.redhat.com/browse/SWSQE-1063 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > > Some jobs are passing boolean params as strings, we need to fix that. > It's causing warnings like: The parameter 'DELETE_MAISTRA_OPERATOR' did not have the type expected by clean-environment. Converting to Boolean Parameter. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1064) Execution time optimalization

by Filip Brychta (Jira)

[ https://issues.redhat.com/browse/SWSQE-1064?page=com.atlassian.jira.plugi... ] Filip Brychta updated SWSQE-1064: --------------------------------- Description: It would be good to test if given resource exists before deleting it which can take some time even if the resource doesn't exist. Also some simple resource do not need to be cleaned every time e.g. registry puller and installation when already exists should not fail was: It would be good to test if given resource exists before deleting it which can take some time even if the resource doesn't exist. Also some simple resource do not need to be cleaned every time e.g. registry puller > Execution time optimalization > ----------------------------- > > Key: SWSQE-1064 > URL: https://issues.redhat.com/browse/SWSQE-1064 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Major > > It would be good to test if given resource exists before deleting it which can take some time even if the resource doesn't exist. > Also some simple resource do not need to be cleaned every time e.g. registry puller and installation when already exists should not fail -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1064) Execution time optimalization

by Filip Brychta (Jira)

Filip Brychta created SWSQE-1064: ------------------------------------ Summary: Execution time optimalization Key: SWSQE-1064 URL: https://issues.redhat.com/browse/SWSQE-1064 Project: Kiali QE Issue Type: Sub-task Reporter: Filip Brychta Assignee: Filip Brychta It would be good to test if given resource exists before deleting it which can take some time even if the resource doesn't exist. Also some simple resource do not need to be cleaned every time e.g. registry puller -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1063) Fix incorrect parameter types

by Filip Brychta (Jira)

Filip Brychta created SWSQE-1063: ------------------------------------ Summary: Fix incorrect parameter types Key: SWSQE-1063 URL: https://issues.redhat.com/browse/SWSQE-1063 Project: Kiali QE Issue Type: Sub-task Reporter: Filip Brychta Assignee: Filip Brychta Some jobs are passing boolean params as strings, we need to fix that. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2102) Improve deployment annotation parsing error message

by Lukas Vydra (Jira)

[ https://issues.redhat.com/browse/WFLY-2102?page=com.atlassian.jira.plugin... ] Lukas Vydra reassigned WFLY-2102: --------------------------------- Assignee: Lukas Vydra > Improve deployment annotation parsing error message > ----------------------------------------------------- > > Key: WFLY-2102 > URL: https://issues.redhat.com/browse/WFLY-2102 > Project: WildFly > Issue Type: Enhancement > Components: EE > Reporter: Brad Maxwell > Assignee: Lukas Vydra > Priority: Major > Attachments: test-WFLY-2102.jar > > > Improve deployment annotation parsing error message > Code such as this below, will error with IllegalArgumentException: Empty name segment is not allowed for env. The env is not enough information to identify what the issue is. > @Singleton > @Startup > public class TestEJB { > @Resource(name="/queue/test") > private Queue queue; > } > Caused by: java.lang.IllegalArgumentException: Empty name segment is not allowed for env > at org.jboss.msc.service.ServiceName.of(ServiceName.java:85) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1] > at org.jboss.msc.service.ServiceName.append(ServiceName.java:112) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1] > at org.jboss.as.naming.deployment.ContextNames.buildServiceName(ContextNames.java:183) > at org.jboss.as.naming.deployment.ContextNames$BindInfo.<init>(ContextNames.java:195) > at org.jboss.as.naming.deployment.ContextNames$BindInfo.<init>(ContextNames.java:186) > at org.jboss.as.naming.deployment.ContextNames.bindInfoFor(ContextNames.java:141) > at org.jboss.as.ee.component.OptionalLookupInjectionSource.getResourceValue(OptionalLookupInjectionSource.java:84) > at org.jboss.as.ee.component.ComponentDescription$InjectedConfigurator.configureDependency(ComponentDescription.java:1019) > at org.jboss.as.ee.component.ComponentDescription$InjectedConfigurator.configureDependency(ComponentDescription.java:998) > at org.jboss.as.ee.component.deployers.ComponentInstallProcessor.deployComponent(ComponentInstallProcessor.java:138) > at org.jboss.as.ee.component.deployers.ComponentInstallProcessor.deploy(ComponentInstallProcessor.java:95) > ... 6 more -- 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 February 2020