March 2020 - jboss-jira - Jboss List Archives

[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 edited comment on DROOLS-5185 at 3/30/20 10:53 AM: --------------------------------------------------------------- {{uberfire-message-console-client}} can not be removed, required by {{KieEditor}} {code} [INFO] [ERROR] Line 115: No source code is available for type org.guvnor.messageconsole.client.console.widget.button.AlertsButtonMenuItemBuilder; did you forget to inherit a required module? [INFO] Tracing compile failure path for type 'org.kie.workbench.common.services.shared.messageconsole.MessageConsoleWhiteListImpl' {code} was (Author: jomarko): `uberfire-message-console-client` can not be removed, required by `KieEditor` {code} [INFO] [ERROR] Line 115: No source code is available for type org.guvnor.messageconsole.client.console.widget.button.AlertsButtonMenuItemBuilder; did you forget to inherit a required module? [INFO] Tracing compile failure path for type 'org.kie.workbench.common.services.shared.messageconsole.MessageConsoleWhiteListImpl' {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] (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 commented on DROOLS-5185: ------------------------------------- {kie-wb-config-resource-widget} can not be removed, it is required by {KieEditor} {code} [INFO] [ERROR] Line 98: No source code is available for type org.kie.workbench.common.widgets.configresource.client.widget.bound.ImportsWidgetPresenter; did you forget to inherit a required module? [INFO] [ERROR] Aborting compile due to errors in some input files {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] (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 commented on DROOLS-5185: ------------------------------------- `uberfire-message-console-client` can not be removed, required by `KieEditor` {code} [INFO] [ERROR] Line 115: No source code is available for type org.guvnor.messageconsole.client.console.widget.button.AlertsButtonMenuItemBuilder; did you forget to inherit a required module? [INFO] Tracing compile failure path for type 'org.kie.workbench.common.services.shared.messageconsole.MessageConsoleWhiteListImpl' {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] (WFCORE-4895) Bootable jar runtime module

by Jean Francois Denise (Jira)

Jean Francois Denise created WFCORE-4895: -------------------------------------------- Summary: Bootable jar runtime module Key: WFCORE-4895 URL: https://issues.redhat.com/browse/WFCORE-4895 Project: WildFly Core Issue Type: Feature Request Components: Build System Reporter: Jean Francois Denise Assignee: Jean Francois Denise bootable jar runtime module is not a new feature per se, it is an enabler for Wildfly bootable jar feature. We propose to add a new "bootable-jar" maven parent module with 2 new sub modules: org.wildfly.core:wildfly-jar-boot and org.wildfly.core:wildfly-jar-runtime. wildfly-jar-boot artifact would be shaded inside the bootable jar (done by tooling), wildfly-jar-runtime artifact is executed from the modular classloader and starts the actual server. To run tests against a bootable jar, ts.bootable profile is added. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELYWEB-102) Upgrade WildFly Elytron 1.11.3.Final

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELYWEB-102?page=com.atlassian.jira.plugi... ] Farah Juma updated ELYWEB-102: ------------------------------ Fix Version/s: 1.8.0.CR1 > Upgrade WildFly Elytron 1.11.3.Final > ------------------------------------ > > Key: ELYWEB-102 > URL: https://issues.redhat.com/browse/ELYWEB-102 > Project: Elytron Web > Issue Type: Component Upgrade > Components: Parent > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Fix For: 1.8.0.CR1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELYWEB-102) Upgrade WildFly Elytron 1.11.3.Final

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELYWEB-102?page=com.atlassian.jira.plugi... ] Farah Juma updated ELYWEB-102: ------------------------------ Component/s: Parent > Upgrade WildFly Elytron 1.11.3.Final > ------------------------------------ > > Key: ELYWEB-102 > URL: https://issues.redhat.com/browse/ELYWEB-102 > Project: Elytron Web > Issue Type: Component Upgrade > Components: Parent > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Fix For: 1.8.0.CR1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELYWEB-102) Upgrade WildFly Elytron 1.11.3.Final

by Farah Juma (Jira)

Farah Juma created ELYWEB-102: --------------------------------- Summary: Upgrade WildFly Elytron 1.11.3.Final Key: ELYWEB-102 URL: https://issues.redhat.com/browse/ELYWEB-102 Project: Elytron Web Issue Type: Component Upgrade Reporter: Farah Juma Assignee: Farah Juma -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-4916) Wrongly parse method chain in modify block in executable model

by Luca Molteni (Jira)

[ https://issues.redhat.com/browse/DROOLS-4916?page=com.atlassian.jira.plug... ] Luca Molteni commented on DROOLS-4916: -------------------------------------- Thanks [~tkobayashi] > Wrongly parse method chain in modify block in executable model > -------------------------------------------------------------- > > Key: DROOLS-4916 > URL: https://issues.redhat.com/browse/DROOLS-4916 > Project: Drools > Issue Type: Bug > Components: executable model > Reporter: Luca Molteni > Assignee: Toshiya Kobayashi > Priority: Major > Labels: good-first-issue > > {noformat} > declare Application > categories : Set = new HashSet() > end > {noformat} > Then I had a modify statement scattered about: > {noformat} > modify ($a) { > $a.getCategories().add("hello"); > } > {noformat} > The ExecutableModel did not seem to like any of those. I changed it to: > {noformat} > $a.getCategories().add("hello"); > update($a); > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5204) Replace DMN Validator with generic validator for subsumption and redundancy

by Toni Rikkola (Jira)

Toni Rikkola created DROOLS-5204: ------------------------------------ Summary: Replace DMN Validator with generic validator for subsumption and redundancy Key: DROOLS-5204 URL: https://issues.redhat.com/browse/DROOLS-5204 Project: Drools Issue Type: Task Reporter: Toni Rikkola Assignee: Mario Fusco -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-5031) Use general V&V modularity for all DMN Validation

by Toni Rikkola (Jira)

[ https://issues.redhat.com/browse/DROOLS-5031?page=com.atlassian.jira.plug... ] Toni Rikkola updated DROOLS-5031: --------------------------------- Summary: Use general V&V modularity for all DMN Validation (was: Use general V&V modularity for DMN Validation) > Use general V&V modularity for all DMN Validation > ------------------------------------------------- > > Key: DROOLS-5031 > URL: https://issues.redhat.com/browse/DROOLS-5031 > Project: Drools > Issue Type: Enhancement > Components: verifier > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > Modularity here means. Any part of the validation can be activated or deactivated. This is an existing feature in general verifier used by GDST. This allows for example two range check implementations to work next to each other making each check type a module. > Other benefits of this approach is for example any future needs that might require running the rules. Allowing static and dynamic validation to exist side by side. -- 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