October 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBRULES-3445) DSL expander expands lines in /* */comment block

by Mario Fusco (JIRA)

Mario Fusco created JBRULES-3445: ------------------------------------ Summary: DSL expander expands lines in /* */comment block Key: JBRULES-3445 URL: https://issues.jboss.org/browse/JBRULES-3445 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Mario Fusco Assignee: Mario Fusco When you comment some code in dslr file, the expander still tries to expand it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

2 months, 2 weeks

3
10
0 / 0

[JBoss JIRA] (WFLY-12461) Can't use smallrye-health without weld extension

by Florian Sailer (Jira)

Florian Sailer created WFLY-12461: ------------------------------------- Summary: Can't use smallrye-health without weld extension Key: WFLY-12461 URL: https://issues.jboss.org/browse/WFLY-12461 Project: WildFly Issue Type: Bug Components: MP Health Affects Versions: 17.0.1.Final Reporter: Florian Sailer Assignee: Jeff Mesnil Since this commit in the smallrye implementation it was possible to use smallrye without CDI. https://github.com/smallrye/smallrye-health/commit/a6a7812877d74d2c3f5b29... I'm trying to migrate from Wildfly 15.0.1-Final to 17.0.1-Final, where the smallrye-health extension unfortunately needs weld to startup. It's not possbible for me to activate weld on my sever, because there are some problems using the org.apache.cxf.jaxrs framework with weld. I am getting the following exception while starting: 14:16:04,960 ERROR [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0362: Capabilities required by resource '/subsystem=microprofile-health-smallrye' are not available: org.wildfly.weld; There are no known registration points which can provide this capability. -- This message was sent by Atlassian Jira (v7.13.5#713005)

3 months

3
2
0 / 0

[JBoss JIRA] (DROOLS-3944) DMN Editor: Data type usability study

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3944?page=com.atlassian.jira.plugi... ] Elizabeth Clayton updated DROOLS-3944: -------------------------------------- Sprint: 2019 Week 23-25 > DMN Editor: Data type usability study > ------------------------------------- > > Key: DROOLS-3944 > URL: https://issues.jboss.org/browse/DROOLS-3944 > Project: Drools > Issue Type: Task > Components: DMN Editor > Environment: Version 7.4 > Reporter: Elizabeth Clayton > Assignee: Sarahjane Clark > Priority: Major > Labels: UX, UXTeam, Usability, drools-tools > > Lightweight usability study to test the ease of use in viewing, creating, editing and deleting data types, particularly structured data types. > GOALS: Access the Data Type editor in terms of productivity and usability. > * Ease of use when creating a complex type (concern: minimizing the mouse usage.) > * Ease of use when saving a basic data type (e.g. age: number) > * Discoverability of actions in the kebab menu, especially, insert nested, delete. > * Ease of use/accuracy: Type-ahead of the data type selector. -- This message was sent by Atlassian Jira (v7.12.1#712002)

10 months, 3 weeks

2
1
0 / 0

[Red Hat JIRA] (DROOLS-5730) Profile and if possible improve runtime performances of executable model based rule evaluation

by Mario Fusco (Jira)

Mario Fusco created DROOLS-5730: ----------------------------------- Summary: Profile and if possible improve runtime performances of executable model based rule evaluation Key: DROOLS-5730 URL: https://issues.redhat.com/browse/DROOLS-5730 Project: Drools Issue Type: Task Reporter: Mario Fusco Assignee: Mario Fusco -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5729) Reorganize drools unit tests

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5729?page=com.atlassian.jira.plug... ] Toshiya Kobayashi updated DROOLS-5729: -------------------------------------- Description: Motivation: The motivation is to increase test coverage. For example, unit tests which exist under drools-mvel are not tested against executable-model. "Which module is suitable for the unit test?" depends on each test so we may occasionally need to discuss. But basically drools-test-coverage is a good place for DRL based tests because drools-test-coverage may have all dependencies so is flexible to test with any configurations (e.g. alpha compiler network). Goals: Increase test coverage. More stable product. Impact: During this work, we may find new bugs (because of increased tests). Will need to fix them one-by-one as separated JIRAs. was: Motivation: The motivation is to increase test coverage. For example, unit tests which exist under drools-mvel are not tested against executable-model. "Which module is suitable for the unit test?" depends on each test so we may occasionally need to discuss. But basically drools-test-coverage is a good place for DRL based tests because drools-test-coverage may have all dependencies so is flexible to test with any configurations (e.g. alpha compiler network). Goals: Increase test coverage. More stable product. Impact: While this work, we may find new bugs (because of increased tests). Will need to fix them one-by-one as separated JIRAs. > Reorganize drools unit tests > ---------------------------- > > Key: DROOLS-5729 > URL: https://issues.redhat.com/browse/DROOLS-5729 > Project: Drools > Issue Type: Story > Components: core engine > Affects Versions: 7.44.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > Motivation: The motivation is to increase test coverage. For example, unit tests which exist under drools-mvel are not tested against executable-model. "Which module is suitable for the unit test?" depends on each test so we may occasionally need to discuss. But basically drools-test-coverage is a good place for DRL based tests because drools-test-coverage may have all dependencies so is flexible to test with any configurations (e.g. alpha compiler network). > Goals: Increase test coverage. More stable product. > Impact: During this work, we may find new bugs (because of increased tests). Will need to fix them one-by-one as separated JIRAs. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5729) Reorganize drools unit tests

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5729?page=com.atlassian.jira.plug... ] Toshiya Kobayashi reassigned DROOLS-5729: ----------------------------------------- Assignee: Toshiya Kobayashi (was: Mario Fusco) > Reorganize drools unit tests > ---------------------------- > > Key: DROOLS-5729 > URL: https://issues.redhat.com/browse/DROOLS-5729 > Project: Drools > Issue Type: Story > Components: core engine > Affects Versions: 7.44.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > Motivation: The motivation is to increase test coverage. For example, unit tests which exist under drools-mvel are not tested against executable-model. "Which module is suitable for the unit test?" depends on each test so we may occasionally need to discuss. But basically drools-test-coverage is a good place for DRL based tests because drools-test-coverage may have all dependencies so is flexible to test with any configurations (e.g. alpha compiler network). > Goals: Increase test coverage. More stable product. > Impact: While this work, we may find new bugs (because of increased tests). Will need to fix them one-by-one as separated JIRAs. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5729) Reorganize drools unit tests

by Toshiya Kobayashi (Jira)

Toshiya Kobayashi created DROOLS-5729: ----------------------------------------- Summary: Reorganize drools unit tests Key: DROOLS-5729 URL: https://issues.redhat.com/browse/DROOLS-5729 Project: Drools Issue Type: Story Components: core engine Affects Versions: 7.44.0.Final Reporter: Toshiya Kobayashi Assignee: Mario Fusco Motivation: The motivation is to increase test coverage. For example, unit tests which exist under drools-mvel are not tested against executable-model. "Which module is suitable for the unit test?" depends on each test so we may occasionally need to discuss. But basically drools-test-coverage is a good place for DRL based tests because drools-test-coverage may have all dependencies so is flexible to test with any configurations (e.g. alpha compiler network). Goals: Increase test coverage. More stable product. Impact: While this work, we may find new bugs (because of increased tests). Will need to fix them one-by-one as separated JIRAs. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-13972) Separate testing of deprecated @SafeHtml into a separate package

by Yeray Borges Santana (Jira)

[ https://issues.redhat.com/browse/WFLY-13972?page=com.atlassian.jira.plugi... ] Yeray Borges Santana updated WFLY-13972: ---------------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/13651 > Separate testing of deprecated @SafeHtml into a separate package > ---------------------------------------------------------------- > > Key: WFLY-13972 > URL: https://issues.redhat.com/browse/WFLY-13972 > Project: WildFly > Issue Type: Task > Components: Bean Validation, Test Suite > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Major > > BootStrapValidationTestCase has a method that tests the @SafeHtml annotation that per https://hibernate.atlassian.net/browse/HV-1790 is removed in Hibernate Validator 7. > Move this test method into a subpackage so it can be easily disabled with a JUnit Assume when running with the -Dts.ee9 profile, which test a server that uses HV 7. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[Red Hat JIRA] (WFCORE-5155) A NullPointException was found in a wildfly-jar-maven-plugin test

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFCORE-5155?page=com.atlassian.jira.plug... ] Jeff Mesnil updated WFCORE-5155: -------------------------------- Fix Version/s: 13.0.2.Final > A NullPointException was found in a wildfly-jar-maven-plugin test > ----------------------------------------------------------------- > > Key: WFCORE-5155 > URL: https://issues.redhat.com/browse/WFCORE-5155 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Critical > Fix For: 13.0.2.Final, 14.0.0.Beta1 > > > WFCORE-5114 made a slight change with how the configuration API commits the logging changes. When upgrading the core version in wildfly-jar-maven-plugin a test failure occurred in the PR https://github.com/wildfly-extras/wildfly-jar-maven-plugin/pull/137. > {code} > Error: BootLoggingConfigurationTestCase.testSocketHandler:321->executeOperation:711 Operation { > "operation" => "composite", > "address" => [], > "rollback-on-runtime-failure" => true, > "steps" => [ > { > "operation" => "add", > "address" => [ > ("socket-binding-group" => "standard-sockets"), > ("remote-destination-outbound-socket-binding" => "log-server") > ], > "host" => "127.0.0.1", > "port" => 10514 > }, > { > "operation" => "add", > "address" => [ > ("subsystem" => "logging"), > ("socket-handler" => "socket") > ], > "named-formatter" => "PATTERN", > "outbound-socket-binding-ref" => "log-server" > }, > { > "operation" => "add-handler", > "address" => [ > ("subsystem" => "logging"), > ("root-logger" => "ROOT") > ], > "name" => "socket" > } > ] > } failed: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"WFLYCTL0080: Failed services" => {"org.wildfly.logging.handler.\"org.wildfly.logging.handler.socket\"" => "Failed to start service > Caused by: java.lang.NullPointerException"}}}} > {code} > The NPE is in the service where the {{DelayedHandler}} instance is used, but returns {{null}} for some reason. I could not reproduce this locally, however it did happen locally for me with the {{ascyn-handler}} in the test. This may be a way to reproduce this locally. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-13972) Separate testing of deprecated @SafeHtml into a separate package

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-13972: --------------------------------------- Summary: Separate testing of deprecated @SafeHtml into a separate package Key: WFLY-13972 URL: https://issues.redhat.com/browse/WFLY-13972 Project: WildFly Issue Type: Task Components: Bean Validation, Test Suite Reporter: Brian Stansberry Assignee: Brian Stansberry BootStrapValidationTestCase has a method that tests the @SafeHtml annotation that per https://hibernate.atlassian.net/browse/HV-1790 is removed in Hibernate Validator 7. Move this test method into a subpackage so it can be easily disabled with a JUnit Assume when running with the -Dts.ee9 profile, which test a server that uses HV 7. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 9 months

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 2020