October 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-478) Install Istioctl on the demand when is needed

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-478?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo resolved SWSQE-478. ------------------------------------------- Resolution: Done > Install Istioctl on the demand when is needed > --------------------------------------------- > > Key: SWSQE-478 > URL: https://issues.jboss.org/browse/SWSQE-478 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > Priority: Major > > When it is pre-installed instioctl, sometimes it may lead to a situation that istioctl uses a different version than istio files > See SWSQE-475 for that situation. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-474) Update Upstream Pipeline to Support Istio 1.0.3

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-474?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo resolved SWSQE-474. ------------------------------------------- Resolution: Done > Update Upstream Pipeline to Support Istio 1.0.3 > ----------------------------------------------- > > Key: SWSQE-474 > URL: https://issues.jboss.org/browse/SWSQE-474 > Project: Kiali QE > Issue Type: Task > Reporter: Matt Mahoney > Assignee: Guilherme Baufaker Rêgo > Priority: Major > > Update Pipeline Jobs > - Istio Upstream > - Bookinfo > - Complex mesh -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3192) Change popover menus to launch on single, left mouse click.

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3192?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-3192: ------------------------------------- [~manstis] OK thanks, I lost track of that one. Do we need a jira for restyling the "decision logic" selector menu (logic type: Literal expression, Context, etc.) to align with the data type pop-over (the one with the arrow.) If so, I could repurpose this to be that. If not, then yes please feel free to close given it's a duplicate. > Change popover menus to launch on single, left mouse click. > ------------------------------------------------------------ > > Key: DROOLS-3192 > URL: https://issues.jboss.org/browse/DROOLS-3192 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Michael Anstis > Priority: Major > Labels: drools-tools > > Popover menus should launch on single, left mouse click to match PatternFly pattern: https://www.patternfly.org/pattern-library/widgets/#popover > Including: > * The decision table "decision logic" selector (menu to select logic type: Literal expression, Context, etc.) currently uses a double-left mouse click to launch the menu. Given the menu is closer in spirit (and intention) to a popover menu - to provide a more consistent and predictable user experience it would be preferable to launch this menu on a single, left mouse click. > * Decision table Data type selection popover. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3218) [DMN Designer] UX for Parameters popover

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3218?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-3218: -------------------------------- Labels: UX UXTeam drools-tools (was: drools-tools) > [DMN Designer] UX for Parameters popover > ---------------------------------------- > > Key: DROOLS-3218 > URL: https://issues.jboss.org/browse/DROOLS-3218 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.14.0.Final > Reporter: Michael Anstis > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: DROOLS-3218.png > > > The "Function Grid" allows for the definition of "parameters". > For 7.14.0 (7.2) we went quick and dirty and have the attached (see screenshot) popover. > The popover is launched by double-clicking the "parameters" cell in the grid. > Could UX please work their magic? -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3218) [DMN Designer] UX for Parameters popover

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-3218?page=com.atlassian.jira.plugi... ] Michael Anstis updated DROOLS-3218: ----------------------------------- Attachment: DROOLS-3218.png > [DMN Designer] UX for Parameters popover > ---------------------------------------- > > Key: DROOLS-3218 > URL: https://issues.jboss.org/browse/DROOLS-3218 > Project: Drools > Issue Type: Task > Components: DMN Editor > Affects Versions: 7.14.0.Final > Reporter: Michael Anstis > Assignee: Liz Clayton > Priority: Major > Labels: drools-tools > Attachments: DROOLS-3218.png > > > The "Function Grid" allows for the definition of "parameters". > For 7.14.0 (7.2) we went quick and dirty and have the attached (see screenshot) popover. > The popover is launched by double-clicking the "parameters" cell in the grid. > Could UX please work their magic? -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3218) [DMN Designer] UX for Parameters popover

by Michael Anstis (Jira)

Michael Anstis created DROOLS-3218: -------------------------------------- Summary: [DMN Designer] UX for Parameters popover Key: DROOLS-3218 URL: https://issues.jboss.org/browse/DROOLS-3218 Project: Drools Issue Type: Task Components: DMN Editor Affects Versions: 7.14.0.Final Reporter: Michael Anstis Assignee: Liz Clayton The "Function Grid" allows for the definition of "parameters". For 7.14.0 (7.2) we went quick and dirty and have the attached (see screenshot) popover. The popover is launched by double-clicking the "parameters" cell in the grid. Could UX please work their magic? -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-6918) Unnecessary NoSuchMethodException during JSF app deployment

by Ian Roskam (Jira)

[ https://issues.jboss.org/browse/WFLY-6918?page=com.atlassian.jira.plugin.... ] Ian Roskam commented on WFLY-6918: ---------------------------------- This issue is still present in 11.x. > Unnecessary NoSuchMethodException during JSF app deployment > ------------------------------------------------------------ > > Key: WFLY-6918 > URL: https://issues.jboss.org/browse/WFLY-6918 > Project: WildFly > Issue Type: Bug > Components: JSF > Affects Versions: 10.0.0.Final, 10.1.0.CR1 > Environment: it's same at current master > Reporter: Tomas Remes > Assignee: Farah Juma > Priority: Minor > > When you turn on TRACE logging for {{javax.enterprise.resource}} then you can notice following exception during JSF app deployment: > {noformat} > [javax.enterprise.resource.webcontainer.jsf.application] (ServerService Thread Pool -- 69) java.lang.NoSuchMethodException: org.jboss.as.jsf.injection.JandexAnnotationProvider.<init>(javax.servlet.ServletContext, com.sun.faces.spi.AnnotationProvider): java.lang.NoSuchMethodException: org.jboss.as.jsf.injection.JandexAnnotationProvider.<init>(javax.servlet.ServletContext, com.sun.faces.spi.AnnotationProvider) > at java.lang.Class.getConstructor0(Class.java:3082) > at java.lang.Class.getDeclaredConstructor(Class.java:2178) > at com.sun.faces.spi.ServiceFactoryUtils.getProviderFromEntry(ServiceFactory.java:83) > at com.sun.faces.spi.AnnotationProviderFactory.createAnnotationProvider(AnnotationProviderFactory.java:70) > at com.sun.faces.config.ConfigManager$AnnotationScanTask.<init>(ConfigManager.java:931) > at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:385) > at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:227) > at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:187) > at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:200) > at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:171) > at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:42) > at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43) > at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44) > at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44) > at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44) > at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44) > at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44) > at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:234) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:100) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:82) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > at org.jboss.threads.JBossThread.run(JBossThread.java:320) > {noformat} > Problem is that {{org.jboss.as.jsf.injection.JandexAnnotationProvider}} doesn't have corresponding constructor (with two params - javax.servlet.ServletContext, com.sun.faces.spi.AnnotationProvider) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3217) DMN compilation via kie-maven-plugin wrong lookup at runtime

by Matteo Mortari (Jira)

[ https://issues.jboss.org/browse/DROOLS-3217?page=com.atlassian.jira.plugi... ] Matteo Mortari updated DROOLS-3217: ----------------------------------- Description: When a DT is inside a BKM or nested in an expression, the name lookup looks wrong and fails to locate the correct class. Initial assessment it looks like a misalignment of name resolution algo between JIT compilation and compile-time-compilation > DMN compilation via kie-maven-plugin wrong lookup at runtime > ------------------------------------------------------------ > > Key: DROOLS-3217 > URL: https://issues.jboss.org/browse/DROOLS-3217 > Project: Drools > Issue Type: Bug > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > > When a DT is inside a BKM or nested in an expression, the name lookup looks wrong and fails to locate the correct class. > Initial assessment it looks like a misalignment of name resolution algo between JIT compilation and compile-time-compilation -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3217) DMN compilation via kie-maven-plugin wrong lookup at runtime

by Matteo Mortari (Jira)

Matteo Mortari created DROOLS-3217: -------------------------------------- Summary: DMN compilation via kie-maven-plugin wrong lookup at runtime Key: DROOLS-3217 URL: https://issues.jboss.org/browse/DROOLS-3217 Project: Drools Issue Type: Bug Components: dmn engine Reporter: Matteo Mortari Assignee: Matteo Mortari -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-4193) Maven Wildfly plugin should be working with Java 9+

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFCORE-4193?page=com.atlassian.jira.plugi... ] James Perkins moved WFLY-11226 to WFCORE-4193: ---------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-4193 (was: WFLY-11226) Affects Version/s: (was: 14.0.1.Final) > Maven Wildfly plugin should be working with Java 9+ > --------------------------------------------------- > > Key: WFCORE-4193 > URL: https://issues.jboss.org/browse/WFCORE-4193 > Project: WildFly Core > Issue Type: Bug > Reporter: Michal Jurc > Assignee: James Perkins > Priority: Blocker > Labels: java11 > > Without the workaround, the following error is thrown by JVM upon starting WildFly/JBoss CLI utilising the plugin: > {code}21:35:19 [INFO] STANDALONE server is starting up. > 21:35:20 org.jboss.modules.ModuleNotFoundException: java.se > 21:35:20 at org.jboss.modules.Module.addPaths(Module.java:1266) > 21:35:20 at org.jboss.modules.Module.link(Module.java:1622) > 21:35:20 at org.jboss.modules.Module.relinkIfNecessary(Module.java:1650) > 21:35:20 at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:296) > 21:35:20 at org.jboss.modules.Main.main(Main.java:437){code} > This is pretty cumbersome and a blocker to migrating application without change of configuration. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

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 October 2018