March 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-1096) Rebuild kiali test mesh and upgrade the base image

by Filip Brychta (Jira)

Filip Brychta created SWSQE-1096: ------------------------------------ Summary: Rebuild kiali test mesh and upgrade the base image Key: SWSQE-1096 URL: https://issues.redhat.com/browse/SWSQE-1096 Project: Kiali QE Issue Type: QE Task Reporter: Filip Brychta Assignee: Filip Brychta We are hitting https://github.com/operator-framework/operator-sdk/issues/2112 which is fixed in https://github.com/operator-framework/operator-sdk/releases/tag/v0.16.0 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13260) Refactor wildfly-clustering-web-spi in preparation for Servlet 5.0

by Sudeshna Sur (Jira)

[ https://issues.redhat.com/browse/WFLY-13260?page=com.atlassian.jira.plugi... ] Sudeshna Sur commented on WFLY-13260: ------------------------------------- Hi [~pferraro], Can you help me in reproducing this issue? > Refactor wildfly-clustering-web-spi in preparation for Servlet 5.0 > ------------------------------------------------------------------ > > Key: WFLY-13260 > URL: https://issues.redhat.com/browse/WFLY-13260 > Project: WildFly > Issue Type: Task > Components: Clustering > Affects Versions: No Release > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > > Because Servlet 5.0 will change package names, and because the implementations of the wildfly-clustering-web-spi must work with containers supporting earlier versions of the specification, certain interfaces will have to be made generic to support both packages names. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5185) Investigate unused dependencies of scenariossimulation-kogito-runitme

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-5185?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-5185: -------------------------------- Affects Version/s: 7.35.0.Final > Investigate unused dependencies of scenariossimulation-kogito-runitme > --------------------------------------------------------------------- > > Key: DROOLS-5185 > URL: https://issues.redhat.com/browse/DROOLS-5185 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Affects Versions: 7.35.0.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > Priority: Major > Labels: drools-tools > > There are [1] declared for 'drools-wb-scenario-simulation-editor-kogito-runtime' module. > Investigate if they can not be removed. > [1] > {code} > [WARNING] org.uberfire:uberfire-message-console-client:jar:7.35.0-SNAPSHOT:provided > [WARNING] org.kie.workbench.widgets:kie-wb-config-resource-widget:jar:7.35.0-SNAPSHOT:provided > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5185) Investigate unused dependencies of scenariossimulation-kogito-runitme

by Jozef Marko (Jira)

Jozef Marko created DROOLS-5185: ----------------------------------- Summary: Investigate unused dependencies of scenariossimulation-kogito-runitme Key: DROOLS-5185 URL: https://issues.redhat.com/browse/DROOLS-5185 Project: Drools Issue Type: Task Components: Scenario Simulation and Testing Reporter: Jozef Marko Assignee: Jozef Marko There are [1] declared for 'drools-wb-scenario-simulation-editor-kogito-runtime' module. Investigate if they can not be removed. [1] {code:xml}  <dependency> <groupId>org.dashbuilder</groupId> <artifactId>dashbuilder-widgets</artifactId> <scope>provided</scope> </dependency> <dependency> <groupId>org.dashbuilder</groupId> <artifactId>dashbuilder-validations</artifactId> <scope>provided</scope> </dependency> <dependency> <groupId>org.dashbuilder</groupId> <artifactId>dashbuilder-navigation-client</artifactId> <scope>provided</scope> <exclusions> <exclusion> <groupId>org.uberfire</groupId> <artifactId>uberfire-layout-editor-backend</artifactId> </exclusion> </exclusions> </dependency> <dependency> <groupId>org.dashbuilder</groupId> <artifactId>dashbuilder-renderer-default</artifactId> <scope>provided</scope> </dependency> {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5185) Investigate unused dependencies of scenariossimulation-kogito-runitme

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-5185?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-5185: -------------------------------- Description: There are [1] declared for 'drools-wb-scenario-simulation-editor-kogito-runtime' module. Investigate if they can not be removed. [1] {code} [WARNING] org.uberfire:uberfire-message-console-client:jar:7.35.0-SNAPSHOT:provided [WARNING] org.kie.workbench.widgets:kie-wb-config-resource-widget:jar:7.35.0-SNAPSHOT:provided {code} was: There are [1] declared for 'drools-wb-scenario-simulation-editor-kogito-runtime' module. Investigate if they can not be removed. [1] {code:xml}  <dependency> <groupId>org.dashbuilder</groupId> <artifactId>dashbuilder-widgets</artifactId> <scope>provided</scope> </dependency> <dependency> <groupId>org.dashbuilder</groupId> <artifactId>dashbuilder-validations</artifactId> <scope>provided</scope> </dependency> <dependency> <groupId>org.dashbuilder</groupId> <artifactId>dashbuilder-navigation-client</artifactId> <scope>provided</scope> <exclusions> <exclusion> <groupId>org.uberfire</groupId> <artifactId>uberfire-layout-editor-backend</artifactId> </exclusion> </exclusions> </dependency> <dependency> <groupId>org.dashbuilder</groupId> <artifactId>dashbuilder-renderer-default</artifactId> <scope>provided</scope> </dependency> {code} > Investigate unused dependencies of scenariossimulation-kogito-runitme > --------------------------------------------------------------------- > > Key: DROOLS-5185 > URL: https://issues.redhat.com/browse/DROOLS-5185 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Affects Versions: 7.35.0.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > Priority: Major > Labels: drools-tools > > There are [1] declared for 'drools-wb-scenario-simulation-editor-kogito-runtime' module. > Investigate if they can not be removed. > [1] > {code} > [WARNING] org.uberfire:uberfire-message-console-client:jar:7.35.0-SNAPSHOT:provided > [WARNING] org.kie.workbench.widgets:kie-wb-config-resource-widget:jar:7.35.0-SNAPSHOT:provided > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13260) Refactor wildfly-clustering-web-spi in preparation for Servlet 5.0

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-13260: ----------------------------------- Summary: Refactor wildfly-clustering-web-spi in preparation for Servlet 5.0 Key: WFLY-13260 URL: https://issues.redhat.com/browse/WFLY-13260 Project: WildFly Issue Type: Task Components: Clustering Affects Versions: No Release Reporter: Paul Ferraro Assignee: Paul Ferraro Because Servlet 5.0 will change package names, and because the implementations of the wildfly-clustering-web-spi must work with containers supporting earlier versions of the specification, certain interfaces will have to be made generic to support both packages names. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-533) Deprecate all legacy code

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/ELY-533?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse commented on ELY-533: -------------------------------------- TBH this issue is likely a little old now, if there is any work on this one I also think it will likely need to be a core engineer going through the projects to identify any additional code to deprecate so to answer your question we will have undertaken the task. Feel free to join the #wildfly-elytron stream in Zulip to talk about other issues that may be good to take a look at. > Deprecate all legacy code > ------------------------- > > Key: ELY-533 > URL: https://issues.redhat.com/browse/ELY-533 > Project: WildFly Elytron > Issue Type: Task > Components: API / SPI > Reporter: Darran Lofthouse > Priority: Critical > Fix For: 1.12.0.CR1 > > > In a few places we have legacy behaviour within the project to assist migration from previous JBoss / WildFly releases - this code should be flagged as deprecated to encourage minimal use. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5184) [DMN Designer] Decision table - Propose values from the enumeration constraints

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-5184?page=com.atlassian.jira.plug... ] Michael Anstis commented on DROOLS-5184: ---------------------------------------- I completely agree [~dmarrazzo] :-) > [DMN Designer] Decision table - Propose values from the enumeration constraints > ------------------------------------------------------------------------------- > > Key: DROOLS-5184 > URL: https://issues.redhat.com/browse/DROOLS-5184 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.34.0.Final > Reporter: Donato Marrazzo > Assignee: Michael Anstis > Priority: Minor > Labels: drools-tools > > In decision tables often the input values and output values are constrained to a set of options (enumeration). > The DMN spec leverage "output values" and "constraints". > It would be really handy for users to select the value from drop down list. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5184) [DMN Designer] Decision table - Propose values from the enumeration constraints

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-5184?page=com.atlassian.jira.plug... ] Michael Anstis updated DROOLS-5184: ----------------------------------- Tester: Jozef Marko > [DMN Designer] Decision table - Propose values from the enumeration constraints > ------------------------------------------------------------------------------- > > Key: DROOLS-5184 > URL: https://issues.redhat.com/browse/DROOLS-5184 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.34.0.Final > Reporter: Donato Marrazzo > Assignee: Michael Anstis > Priority: Minor > Labels: drools-tools > > In decision tables often the input values and output values are constrained to a set of options (enumeration). > The DMN spec leverage "output values" and "constraints". > It would be really handy for users to select the value from drop down list. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5183) DMN DT Analysis Validation for output values constraint

by Matteo Mortari (Jira)

[ https://issues.redhat.com/browse/DROOLS-5183?page=com.atlassian.jira.plug... ] Matteo Mortari commented on DROOLS-5183: ---------------------------------------- The DMN model is compiled correctly in such a way that if triggering an output not consistent with the list of values, it will emit an error. This jira rightfully extend the check to static time analysis > DMN DT Analysis Validation for output values constraint > ------------------------------------------------------- > > Key: DROOLS-5183 > URL: https://issues.redhat.com/browse/DROOLS-5183 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Affects Versions: 7.34.0.Final > Reporter: Donato Marrazzo > Assignee: Matteo Mortari > Priority: Minor > Attachments: completeness.dmn > > > from the spec: > {quote}The list of output values is optional. If provided, it is a list restricting output entries to the given list of values.{quote} > the validation does not highlight when if the user enters a wrong value. > Example: > [^completeness.dmn] -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

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 March 2020