October 2020 - jboss-jira - Jboss List Archives

[Red Hat JIRA] (WFCORE-5162) (7.3.z) WildFly Core - Require a minimum of Maven 3.6.0 and default to 3.6.3

by Ivo Studensky (Jira)

[ https://issues.redhat.com/browse/WFCORE-5162?page=com.atlassian.jira.plug... ] Ivo Studensky reassigned WFCORE-5162: ------------------------------------- Assignee: Ivo Studensky (was: James Perkins) > (7.3.z) WildFly Core - Require a minimum of Maven 3.6.0 and default to 3.6.3 > ---------------------------------------------------------------------------- > > Key: WFCORE-5162 > URL: https://issues.redhat.com/browse/WFCORE-5162 > Project: WildFly Core > Issue Type: Task > Components: Build System > Reporter: Ivo Studensky > Assignee: Ivo Studensky > Priority: Major > Fix For: 13.0.0.Beta1, 13.0.0.Final > > > The current minimum Maven version is 3.3.0 which is quite old at this point. A minimum of 3.6.0 should be required with {{mvnw}} defaulting to the latest, 3.6.3. > As part of this change we should remove the max heap from the {{.mvn/jvm.config}}. This config is picked up by maven as of 3.3.1 making it hard to override for environments like CI, http://maven.apache.org/configure.html#mvn-jvm-config-file. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (WFCORE-5162) (7.3.z) WildFly Core - Require a minimum of Maven 3.6.0 and default to 3.6.3

by Ivo Studensky (Jira)

Ivo Studensky created WFCORE-5162: ------------------------------------- Summary: (7.3.z) WildFly Core - Require a minimum of Maven 3.6.0 and default to 3.6.3 Key: WFCORE-5162 URL: https://issues.redhat.com/browse/WFCORE-5162 Project: WildFly Core Issue Type: Task Components: Build System Reporter: Ivo Studensky Assignee: James Perkins Fix For: 13.0.0.Beta1, 13.0.0.Final The current minimum Maven version is 3.3.0 which is quite old at this point. A minimum of 3.6.0 should be required with {{mvnw}} defaulting to the latest, 3.6.3. As part of this change we should remove the max heap from the {{.mvn/jvm.config}}. This config is picked up by maven as of 3.3.1 making it hard to override for environments like CI, http://maven.apache.org/configure.html#mvn-jvm-config-file. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-13971) (7.3.z) Require a minimum of Maven 3.6.0 and default to 3.6.3

by Ivo Studensky (Jira)

Ivo Studensky created WFLY-13971: ------------------------------------ Summary: (7.3.z) Require a minimum of Maven 3.6.0 and default to 3.6.3 Key: WFLY-13971 URL: https://issues.redhat.com/browse/WFLY-13971 Project: WildFly Issue Type: Task Components: Build System Reporter: Ivo Studensky Assignee: James Perkins Fix For: 21.0.0.Beta1, 21.0.0.Final The current minimum Maven version is 3.3.0 which is quite old at this point. A minimum of 3.6.0 should be required with {{mvnw}} defaulting to the latest, 3.6.3. As part of this change we should remove the max heap from the {{.mvn/jvm.config}}. This config is picked up by maven as of 3.3.1 making it hard to override for environments like CI, http://maven.apache.org/configure.html#mvn-jvm-config-file. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-13970) jpa ScannerTests.testGetBytesFromInputStream failed intermittently

by Scott Marlow (Jira)

[ https://issues.redhat.com/browse/WFLY-13970?page=com.atlassian.jira.plugi... ] Scott Marlow commented on WFLY-13970: ------------------------------------- Thanks for reporting this Cheng! I don't see any reason to keep the time comparison test which doesn't seem related to the JPA scanning. So, I removed the test comparison to address the failure. > jpa ScannerTests.testGetBytesFromInputStream failed intermittently > ------------------------------------------------------------------ > > Key: WFLY-13970 > URL: https://issues.redhat.com/browse/WFLY-13970 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 21.0.0.Final > Reporter: Cheng Fang > Assignee: Scott Marlow > Priority: Major > > When building WildFly, the test {{org.jboss.as.jpa.hibernate5.scan.ScannerTests#testGetBytesFromInputStream}} failed intermittently at line 147 when comparing the old perf time to the new one: > {code} > assertTrue(oldTime > newTime); > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-13519) Infinispan module attribute needs to support multiple values

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFLY-13519?page=com.atlassian.jira.plugi... ] Radoslav Husar updated WFLY-13519: ---------------------------------- Fix Version/s: 22.0.0.Beta1 > Infinispan module attribute needs to support multiple values > ------------------------------------------------------------ > > Key: WFLY-13519 > URL: https://issues.redhat.com/browse/WFLY-13519 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 20.0.0.Beta1 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Major > Fix For: 22.0.0.Beta1 > > > The cache-container and remote-cache-container resources in the Infinispan subsystem have a module attribute that is used to dynamically load externalizers used to configure marshalling for capabilities associated with these resources. > Additionally, this attribute is also used to load Infinispan modules (e.g query, multimap, hibernate, etc.). > Several users have had issues with configuring the marshalling of a custom cache because the module to which their cache container is associated does not know about their module. Users wanting to a specific Infinispan module has a similar issue. > Currently, the only way to load marshalling configuration from multiple modules is through the use of module dependencies (using services="import"). This causes lots of unnatural service dependencies, which complicates the ability to build fine grained galleon layers. > In order to support the use of multiple modules for a given cache-container, and also to support marshalling for multiple modules, we need to allow these resources to be associated with a list of modules, instead of a single module. > Thus, the "module" will need to be replaced by "modules", where the former becomes an alias for the latter, with some translation logic to convert multiple values to a single value. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-13965) Resource-level capability constraints are not enforced

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFLY-13965?page=com.atlassian.jira.plugi... ] Radoslav Husar updated WFLY-13965: ---------------------------------- Fix Version/s: 21.0.1.Final 22.0.0.Beta1 > Resource-level capability constraints are not enforced > ------------------------------------------------------ > > Key: WFLY-13965 > URL: https://issues.redhat.com/browse/WFLY-13965 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 21.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Critical > Fix For: 21.0.1.Final, 22.0.0.Beta1 > > > For example, a replicated-cache has a capability constraint on a JGroups transport. However, the following operation does not fail, even though a /subsystem=infinispan/cache-container=server/transport=jgroups resource was not defined: > {noformat} > [standalone@embedded /] /subsystem=infinispan/cache-container=server/replicated-cache=foo:add() > ResourceCapabilityReference.addCapabilityRequirements(/subsystem=infinispan/cache-container=server/replicated-cache=foo, null,[] > {"outcome" => "success"} > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-13939) Upgrade SmallRye Metrics to 2.4.4

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFLY-13939?page=com.atlassian.jira.plugi... ] Radoslav Husar updated WFLY-13939: ---------------------------------- Affects Version/s: 21.0.0.Final > Upgrade SmallRye Metrics to 2.4.4 > --------------------------------- > > Key: WFLY-13939 > URL: https://issues.redhat.com/browse/WFLY-13939 > Project: WildFly > Issue Type: Component Upgrade > Components: MP Metrics > Affects Versions: 21.0.0.Beta1, 21.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > Fix For: 22.0.0.Beta1 > > > Relases > https://github.com/smallrye/smallrye-metrics/releases/tag/2.4.4 > https://github.com/smallrye/smallrye-metrics/releases/tag/2.4.3 > Changelog > https://github.com/smallrye/smallrye-metrics/compare/2.4.3...2.4.4 > https://github.com/smallrye/smallrye-metrics/compare/2.4.2...2.4.3 > Notable changes > https://github.com/smallrye/smallrye-metrics/commit/b7c7313738e05cf48a2b5... potential NPE > https://github.com/smallrye/smallrye-metrics/commit/6c9a6f33eb9fed9952e5c... new API module -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-13936) Upgrade smallrye-fault-tolerance to 4.3.1

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFLY-13936?page=com.atlassian.jira.plugi... ] Radoslav Husar updated WFLY-13936: ---------------------------------- Affects Version/s: 21.0.0.Final > Upgrade smallrye-fault-tolerance to 4.3.1 > ----------------------------------------- > > Key: WFLY-13936 > URL: https://issues.redhat.com/browse/WFLY-13936 > Project: WildFly > Issue Type: Component Upgrade > Components: MP Fault Tolerance > Affects Versions: 21.0.0.Beta1, 21.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > Fix For: 22.0.0.Beta1 > > > Brings in new API module. > Release notes: > https://github.com/smallrye/smallrye-fault-tolerance/releases/tag/4.3.1 > Changes: > https://github.com/smallrye/smallrye-fault-tolerance/compare/4.3.0...4.3.1 > Notable changes: > Fixes: > https://github.com/smallrye/smallrye-fault-tolerance/commit/0e85a1ee4c689... > https://github.com/smallrye/smallrye-fault-tolerance/commit/28b2c26fc031a... > Improvements: > https://github.com/smallrye/smallrye-fault-tolerance/commit/af4ca42825c79... > https://github.com/smallrye/smallrye-fault-tolerance/commit/4b5081ba807ea... > "Breaking changes" > https://github.com/smallrye/smallrye-fault-tolerance/commit/e195d42b01f60... - this now requires a new module and new module dependency on 'smallrye-metrics-api' > Deprecations: > https://github.com/smallrye/smallrye-fault-tolerance/commit/b03f9d90d22b0... -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (JBLOGGING-145) Create an API to query information about the backing log manager

by James Perkins (Jira)

James Perkins created JBLOGGING-145: --------------------------------------- Summary: Create an API to query information about the backing log manager Key: JBLOGGING-145 URL: https://issues.redhat.com/browse/JBLOGGING-145 Project: JBoss Logging Issue Type: Feature Request Reporter: James Perkins Assignee: James Perkins Some useful items to query will be things like: * The Logger names * The loggers themselves * The handlers/appenders * The currently set level -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-13970) jpa ScannerTests.testGetBytesFromInputStream failed intermittently

by Cheng Fang (Jira)

Cheng Fang created WFLY-13970: --------------------------------- Summary: jpa ScannerTests.testGetBytesFromInputStream failed intermittently Key: WFLY-13970 URL: https://issues.redhat.com/browse/WFLY-13970 Project: WildFly Issue Type: Bug Components: JPA / Hibernate Reporter: Cheng Fang Assignee: Scott Marlow When building WildFly, the test {{org.jboss.as.jpa.hibernate5.scan.ScannerTests#testGetBytesFromInputStream}} failed intermittently at line 147 when comparing the old perf time to the new one: {code} assertTrue(oldTime > newTime); {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 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