June 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 weeks, 4 days

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)

1 month

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)

8 months, 3 weeks

2
1
0 / 0

[JBoss JIRA] (WFLY-13630) Scattered caches should not contain a transaction resource

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-13630: ----------------------------------- Summary: Scattered caches should not contain a transaction resource Key: WFLY-13630 URL: https://issues.redhat.com/browse/WFLY-13630 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 20.0.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro This configuration throws an error at runtime. Thus we should not registered this child resource for scattered caches, nor should such a configuration be allowed by the parser. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13629) WildFly kitchensink quickstart doesn't run test when started by Maven

by Norbert Kawiński (Jira)

[ https://issues.redhat.com/browse/WFLY-13629?page=com.atlassian.jira.plugi... ] Norbert Kawiński updated WFLY-13629: ------------------------------------ Description: Problem: When running kitchensink's tests from Maven, the script finishes with "BUILD SUCCESS" but no tests are run. Cause: {color:#172b4d}"MemberRegistrationIT" class is not used by the {color}"Maven Surefire Plugin" which is responsible for running tests. Quoting its documentation: [https://maven.apache.org/surefire/maven-surefire-plugin/examples/junit-pl...] {color:#505f79}_The Maven Surefire Plugin will scan for test classes whose fully qualified names match the following patterns._{color} * {color:#505f79}_{{**/Test*.java}}_{color} * {color:#505f79}_{{**/*Test.java}}_{color} * {color:#505f79}_{{**/*Tests.java}}_{color} * {color:#505f79}{{_**/*TestCase.java_}}{color} {color:#172b4d}{{}}This plugin runs only classes with very specific naming convention. The "MemberRegistrationIT" class doesn't fit into this convention.{color} {color:#172b4d}Solution:\{{}}{color} {color:#172b4d}Rename the "MemberRegistrationIT" class to something like "MemberRegistrationIntegrationTest".{color} was: Problem: When running tests from Maven, the script finishes with "BUILD SUCCESS" but no tests are run. Cause: {color:#172b4d}"MemberRegistrationIT" class is not used by the {color}"Maven Surefire Plugin" which is responsible for running tests. Quoting its documentation: [https://maven.apache.org/surefire/maven-surefire-plugin/examples/junit-pl...] {color:#505f79}_The Maven Surefire Plugin will scan for test classes whose fully qualified names match the following patterns._{color} * {color:#505f79}_{{**/Test*.java}}_{color} * {color:#505f79}_{{**/*Test.java}}_{color} * {color:#505f79}_{{**/*Tests.java}}_{color} * {color:#505f79}{{_**/*TestCase.java_}}{color} {color:#172b4d}{{}}This plugin runs only classes with very specific naming convention. The "MemberRegistrationIT" class doesn't fit into this convention. {color} {color:#172b4d}Solution:{{}}{color} {color:#172b4d}Rename the "MemberRegistrationIT" class to something like "MemberRegistrationIntegrationTest".{color} > WildFly kitchensink quickstart doesn't run test when started by Maven > --------------------------------------------------------------------- > > Key: WFLY-13629 > URL: https://issues.redhat.com/browse/WFLY-13629 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Affects Versions: 20.0.0.Final > Reporter: Norbert Kawiński > Assignee: Eduardo Martins > Priority: Major > > Problem: > When running kitchensink's tests from Maven, the script finishes with "BUILD SUCCESS" but no tests are run. > > Cause: > {color:#172b4d}"MemberRegistrationIT" class is not used by the {color}"Maven Surefire Plugin" which is responsible for running tests. > Quoting its documentation: [https://maven.apache.org/surefire/maven-surefire-plugin/examples/junit-pl...] > {color:#505f79}_The Maven Surefire Plugin will scan for test classes whose fully qualified names match the following patterns._{color} > * {color:#505f79}_{{**/Test*.java}}_{color} > * {color:#505f79}_{{**/*Test.java}}_{color} > * {color:#505f79}_{{**/*Tests.java}}_{color} > * {color:#505f79}{{_**/*TestCase.java_}}{color} > {color:#172b4d}{{}}This plugin runs only classes with very specific naming convention. The "MemberRegistrationIT" class doesn't fit into this convention.{color} > > {color:#172b4d}Solution:\{{}}{color} > {color:#172b4d}Rename the "MemberRegistrationIT" class to something like "MemberRegistrationIntegrationTest".{color} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13629) WildFly kitchensink quickstart doesn't run test when started by Maven

by Norbert Kawiński (Jira)

[ https://issues.redhat.com/browse/WFLY-13629?page=com.atlassian.jira.plugi... ] Norbert Kawiński updated WFLY-13629: ------------------------------------ Description: Problem: When running kitchensink's tests from Maven, the script finishes with "BUILD SUCCESS" but no tests are run. Cause: {color:#172b4d}"MemberRegistrationIT" class is not used by the {color}"Maven Surefire Plugin" which is responsible for running tests. Quoting its documentation: [https://maven.apache.org/surefire/maven-surefire-plugin/examples/junit-pl...] ??{color:#505f79}_The Maven Surefire Plugin will scan for test classes whose fully qualified names match the following patterns._{color}?? * ??{color:#505f79}_{{**/Test*.java}}_{color}?? * ??{color:#505f79}_{{**/*Test.java}}_{color}?? * ??{color:#505f79}_{{**/*Tests.java}}_{color}?? * ??{color:#505f79}{{_**/*TestCase.java_}}{color}?? {color:#172b4d}This plugin runs only classes with very specific naming convention. The "MemberRegistrationIT" class doesn't fit into this convention.{color} {color:#172b4d}Solution:{color} {color:#172b4d}Rename the "MemberRegistrationIT" class to something like "MemberRegistrationIntegrationTest".{color} was: Problem: When running kitchensink's tests from Maven, the script finishes with "BUILD SUCCESS" but no tests are run. Cause: {color:#172b4d}"MemberRegistrationIT" class is not used by the {color}"Maven Surefire Plugin" which is responsible for running tests. Quoting its documentation: [https://maven.apache.org/surefire/maven-surefire-plugin/examples/junit-pl...] {color:#505f79}_The Maven Surefire Plugin will scan for test classes whose fully qualified names match the following patterns._{color} * {color:#505f79}_{{**/Test*.java}}_{color} * {color:#505f79}_{{**/*Test.java}}_{color} * {color:#505f79}_{{**/*Tests.java}}_{color} * {color:#505f79}{{_**/*TestCase.java_}}{color} {color:#172b4d}{{}}This plugin runs only classes with very specific naming convention. The "MemberRegistrationIT" class doesn't fit into this convention.{color} {color:#172b4d}Solution:\{{}}{color} {color:#172b4d}Rename the "MemberRegistrationIT" class to something like "MemberRegistrationIntegrationTest".{color} > WildFly kitchensink quickstart doesn't run test when started by Maven > --------------------------------------------------------------------- > > Key: WFLY-13629 > URL: https://issues.redhat.com/browse/WFLY-13629 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Affects Versions: 20.0.0.Final > Reporter: Norbert Kawiński > Assignee: Eduardo Martins > Priority: Major > > Problem: > When running kitchensink's tests from Maven, the script finishes with "BUILD SUCCESS" but no tests are run. > > Cause: > {color:#172b4d}"MemberRegistrationIT" class is not used by the {color}"Maven Surefire Plugin" which is responsible for running tests. > Quoting its documentation: [https://maven.apache.org/surefire/maven-surefire-plugin/examples/junit-pl...] > ??{color:#505f79}_The Maven Surefire Plugin will scan for test classes whose fully qualified names match the following patterns._{color}?? > * ??{color:#505f79}_{{**/Test*.java}}_{color}?? > * ??{color:#505f79}_{{**/*Test.java}}_{color}?? > * ??{color:#505f79}_{{**/*Tests.java}}_{color}?? > * ??{color:#505f79}{{_**/*TestCase.java_}}{color}?? > {color:#172b4d}This plugin runs only classes with very specific naming convention. The "MemberRegistrationIT" class doesn't fit into this convention.{color} > > {color:#172b4d}Solution:{color} > {color:#172b4d}Rename the "MemberRegistrationIT" class to something like "MemberRegistrationIntegrationTest".{color} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13627) Distributed sessions/SFSBs stored in non-transactional invalidation-cache should schedule expirations locally

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-13627?page=com.atlassian.jira.plugi... ] Paul Ferraro updated WFLY-13627: -------------------------------- Summary: Distributed sessions/SFSBs stored in non-transactional invalidation-cache should schedule expirations locally (was: Distributed sessions stored in non-transactional invalidation-cache should schedule expirations locally) > Distributed sessions/SFSBs stored in non-transactional invalidation-cache should schedule expirations locally > ------------------------------------------------------------------------------------------------------------- > > Key: WFLY-13627 > URL: https://issues.redhat.com/browse/WFLY-13627 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 20.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Critical > > Currently, distributed web sessions (and SFSBs) are expired on the primary owner of the session. For non-transactional invalidation caches expiration should always be scheduled locally. This used to be the case, however, the logic for determining this has changed such that expirations happen on the owner of segment 0. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13629) WildFly kitchensink quickstart doesn't run test when started by Maven

by Norbert Kawiński (Jira)

Norbert Kawiński created WFLY-13629: --------------------------------------- Summary: WildFly kitchensink quickstart doesn't run test when started by Maven Key: WFLY-13629 URL: https://issues.redhat.com/browse/WFLY-13629 Project: WildFly Issue Type: Bug Components: Quickstarts Affects Versions: 20.0.0.Final Reporter: Norbert Kawiński Assignee: Eduardo Martins Problem: When running tests from Maven, the script finishes with "BUILD SUCCESS" but no tests are run. Cause: {color:#172b4d}"MemberRegistrationIT" class is not used by the {color}"Maven Surefire Plugin" which is responsible for running tests. Quoting its documentation: [https://maven.apache.org/surefire/maven-surefire-plugin/examples/junit-pl...] {color:#505f79}_The Maven Surefire Plugin will scan for test classes whose fully qualified names match the following patterns._{color} * {color:#505f79}_{{**/Test*.java}}_{color} * {color:#505f79}_{{**/*Test.java}}_{color} * {color:#505f79}_{{**/*Tests.java}}_{color} * {color:#505f79}{{_**/*TestCase.java_}}{color} {color:#172b4d}{{}}This plugin runs only classes with very specific naming convention. The "MemberRegistrationIT" class doesn't fit into this convention. {color} {color:#172b4d}Solution:{{}}{color} {color:#172b4d}Rename the "MemberRegistrationIT" class to something like "MemberRegistrationIntegrationTest".{color} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13628) Invalidation caches need to consider keys in the cache store when reassigning ownership

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-13628: ----------------------------------- Summary: Invalidation caches need to consider keys in the cache store when reassigning ownership Key: WFLY-13628 URL: https://issues.redhat.com/browse/WFLY-13628 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 20.0.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro On cache topology changes, the distributed web/SFSB manager iterates over keys in memory to determine primary ownership changes. This is not sufficient for invalidation caches - which will not necessary contain those keys in memory that require rescheduling. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13627) Distributed sessions stored in non-transactional invalidation-cache should schedule expirations locally

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-13627: ----------------------------------- Summary: Distributed sessions stored in non-transactional invalidation-cache should schedule expirations locally Key: WFLY-13627 URL: https://issues.redhat.com/browse/WFLY-13627 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 20.0.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro Currently, distributed web sessions (and SFSBs) are expired on the primary owner of the session. For non-transactional invalidation caches expiration should always be scheduled locally. This used to be the case, however, the logic for determining this has changed such that expirations happen on the owner of segment 0. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 10 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 June 2020