October 2018 - jboss-jira - Jboss List Archives

[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)

5 years, 5 months

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)

5 years, 5 months

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)

5 years, 5 months

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)

5 years, 5 months

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)

5 years, 5 months

1
0
0 / 0

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

by Guilherme Baufaker Rêgo (Jira)

Guilherme Baufaker Rêgo created SWSQE-478: --------------------------------------------- Summary: 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 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)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3216) Async dependencies resolution or add loading indicator during scesim creation

by Daniele Zonca (Jira)

Daniele Zonca created DROOLS-3216: ------------------------------------- Summary: Async dependencies resolution or add loading indicator during scesim creation Key: DROOLS-3216 URL: https://issues.jboss.org/browse/DROOLS-3216 Project: Drools Issue Type: Bug Components: Scenario Simulation and Testing Reporter: Daniele Zonca Assignee: Daniele Zonca When user create the first scesim file in the project, the system creates the JUnit activator file and it adds the needed dependencies. After that the system takes several seconds (5-6) to retrieve all the dependencies. During this time the editor still blank without any indicator or information to the user about what is going on. This happens only for the first scesim creation in the project -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-477) REST Tests failed in Istio 1.0.3

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-477?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo updated SWSQE-477: ------------------------------------------ Sprint: Kiali Sprint #13 (was: Kiali Sprint #13) > REST Tests failed in Istio 1.0.3 > -------------------------------- > > Key: SWSQE-477 > URL: https://issues.jboss.org/browse/SWSQE-477 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Michael Foley > Priority: Major > > Started happening after B12 installed with Istio 1.0.3. > http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/run-kiali-e2e-te... -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-476) PRT Output Improve

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-476?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo updated SWSQE-476: ------------------------------------------ Sprint: Kiali Sprint #13 (was: Kiali Sprint #13) > PRT Output Improve > ------------------ > > Key: SWSQE-476 > URL: https://issues.jboss.org/browse/SWSQE-476 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > > Feedback from developers. > When PRT fails because of some internal reason, e.g. bookinfo install fails, devs are confused. Or if e2e tests fail for some other reason. > What we need to do, when PRT fails due to other reason that e2e tests broken by PR, then the bot should comment in PR that "PRT is broken, contact to QE". -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 5 months

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 updated SWSQE-474: ------------------------------------------ Sprint: Kiali Sprint #13 (was: Kiali Sprint #13) > 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)

5 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2018