February 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13135) Upgrade WildFly Core 11.0.0.Beta9

by Jeff Mesnil (Jira)

Jeff Mesnil created WFLY-13135: ---------------------------------- Summary: Upgrade WildFly Core 11.0.0.Beta9 Key: WFLY-13135 URL: https://issues.redhat.com/browse/WFLY-13135 Project: WildFly Issue Type: Component Upgrade Components: Management Reporter: Jeff Mesnil Assignee: Jeff Mesnil Fix For: 19.0.0.Beta3, 20.0.0.Beta1 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-304) AutoClosable behaviour from MP Config spec is not implemented

by Marek Kopecky (Jira)

[ https://issues.redhat.com/browse/WFWIP-304?page=com.atlassian.jira.plugin... ] Marek Kopecky commented on WFWIP-304: ------------------------------------- bq. This issue already exists in the smallrye-config implementation we ship in EAP 7.3 AutoCloseable definition was added in MP Config 1.4, see https://github.com/eclipse/microprofile-config/commit/442525fd8aafc08c3c7... > AutoClosable behaviour from MP Config spec is not implemented > ------------------------------------------------------------- > > Key: WFWIP-304 > URL: https://issues.redhat.com/browse/WFWIP-304 > Project: WildFly WIP > Issue Type: Bug > Reporter: Marek Kopecky > Assignee: Jeff Mesnil > Priority: Blocker > > Current implementation MP Config 1.4 doesn t implement AutoCloseable behaviour on ConfigSource and Converter classes. Developers create [MP issue|https://github.com/eclipse/microprofile-config/issues/136], because these specification requirements seems confusing and unclear to them. [This issue|https://github.com/eclipse/microprofile-config/issues/136] is not approved as a bug from MP community. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4670) Upgrade JBoss MSC to 1.4.12.Final

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFCORE-4670?page=com.atlassian.jira.plug... ] Jeff Mesnil updated WFCORE-4670: -------------------------------- Fix Version/s: 11.0.0.Beta10 (was: 11.0.0.Beta9) > Upgrade JBoss MSC to 1.4.12.Final > --------------------------------- > > Key: WFCORE-4670 > URL: https://issues.redhat.com/browse/WFCORE-4670 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Server > Reporter: Katarina Hermanova > Assignee: Richard Opalka > Priority: Major > Fix For: 11.0.0.Beta10 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4484) Support SSH authentication for Git persistence

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFCORE-4484?page=com.atlassian.jira.plug... ] Jeff Mesnil updated WFCORE-4484: -------------------------------- Fix Version/s: 11.0.0.Beta10 (was: 11.0.0.Beta9) > Support SSH authentication for Git persistence > ---------------------------------------------- > > Key: WFCORE-4484 > URL: https://issues.redhat.com/browse/WFCORE-4484 > Project: WildFly Core > Issue Type: Feature Request > Components: Management, Security > Reporter: Farah Juma > Assignee: Ashley Abdel-Sayed > Priority: Major > Labels: EAP-CD19 > Fix For: 11.0.0.Beta10 > > > Currently Elytron only supports authentication for HTTP(s) URLS so there is no way to connect to a SSH git server to pull/push configuration history -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3376) Modules may create loggers on a deployments log context

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFCORE-3376?page=com.atlassian.jira.plug... ] Jeff Mesnil updated WFCORE-3376: -------------------------------- Fix Version/s: 11.0.0.Beta10 (was: 11.0.0.Beta9) > Modules may create loggers on a deployments log context > ------------------------------------------------------- > > Key: WFCORE-3376 > URL: https://issues.redhat.com/browse/WFCORE-3376 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Critical > Fix For: 11.0.0.Beta10 > > > Currently WildFly uses a {{ClassLoaderLogContextSelector}} to determine the log context to use when creating loggers. If a deployment has it's own log context, via logging-profile or per-deployment logging, and a dependency on a module, that module may create loggers on the deployments log context. This is due to the fact the the call stack is walked until it finds a log context associated with a class loader. > What is needed is a way to short-circuit once a non-logging API class loader is found and determine if there is an associated log context with the callers class loader. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-304) AutoClosable behaviour from MP Config spec is not implemented

by Jeff Mesnil (Jira)

[ https://issues.redhat.com/browse/WFWIP-304?page=com.atlassian.jira.plugin... ] Jeff Mesnil commented on WFWIP-304: ----------------------------------- slight tangent but I don't think that's a WFWIP issue. This issue already exists in the smallrye-config implementation we ship in EAP 7.3. This should be tracked by a JBEAP issue, right? > AutoClosable behaviour from MP Config spec is not implemented > ------------------------------------------------------------- > > Key: WFWIP-304 > URL: https://issues.redhat.com/browse/WFWIP-304 > Project: WildFly WIP > Issue Type: Bug > Reporter: Marek Kopecky > Assignee: Jeff Mesnil > Priority: Blocker > > Current implementation MP Config 1.4 doesn t implement AutoCloseable behaviour on ConfigSource and Converter classes. Developers create [MP issue|https://github.com/eclipse/microprofile-config/issues/136], because these specification requirements seems confusing and unclear to them. [This issue|https://github.com/eclipse/microprofile-config/issues/136] is not approved as a bug from MP community. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13134) Clustering TS: Default to non-multicast discovery protocol

by Francesco Marchioni (Jira)

[ https://issues.redhat.com/browse/WFLY-13134?page=com.atlassian.jira.plugi... ] Francesco Marchioni deleted WFLY-13134: --------------------------------------- > Clustering TS: Default to non-multicast discovery protocol > ---------------------------------------------------------- > > Key: WFLY-13134 > URL: https://issues.redhat.com/browse/WFLY-13134 > Project: WildFly > Issue Type: Task > Reporter: Francesco Marchioni > Assignee: Radoslav Husar > Priority: Critical > > We have been slowly making progress on reducing reliance on multicast to run the clustering test suite by default given the complexity of system configuration (e.g. multicast on {{::1}} workarounds). The goal is to use a default non-multicast-based protocol by defaut. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13134) Clustering TS: Default to non-multicast discovery protocol

by Francesco Marchioni (Jira)

Francesco Marchioni created WFLY-13134: ------------------------------------------ Summary: Clustering TS: Default to non-multicast discovery protocol Key: WFLY-13134 URL: https://issues.redhat.com/browse/WFLY-13134 Project: WildFly Issue Type: Task Components: Clustering, Test Suite Affects Versions: 18.0.1.Final, 19.0.0.Beta1 Reporter: Francesco Marchioni Assignee: Radoslav Husar Fix For: 19.0.0.Beta2 We have been slowly making progress on reducing reliance on multicast to run the clustering test suite by default given the complexity of system configuration (e.g. multicast on {{::1}} workarounds). The goal is to use a default non-multicast-based protocol by defaut. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-304) AutoClosable behaviour from MP Config spec is not implemented

by Marek Kopecky (Jira)

[ https://issues.redhat.com/browse/WFWIP-304?page=com.atlassian.jira.plugin... ] Marek Kopecky commented on WFWIP-304: ------------------------------------- bq. What would happen if another endpoint is using this Config object? Would its configsources and converters be closed? It was just an example that demonstrate, that releaseConfig call is possible. It was not full customer use-case (where some synchronization would be necessary, etc.). {quote} However calling releaseConfig will lead to inconsistencies and unexpected behaviours. The ConfigProviderResolver interface is in the SPI package and is meant for integration, not for user code. The Config API/SPI is not properly split. We have to take that into consideration when something is technically doable but should not be recommended. {quote} releaseConfig and registerConfig methods are currently public in public org.eclipse.microprofile.config.api jboss module. I'm OK with clarification in future MP spec releases, but now we have 1.4 version. > AutoClosable behaviour from MP Config spec is not implemented > ------------------------------------------------------------- > > Key: WFWIP-304 > URL: https://issues.redhat.com/browse/WFWIP-304 > Project: WildFly WIP > Issue Type: Bug > Reporter: Marek Kopecky > Assignee: Jeff Mesnil > Priority: Blocker > > Current implementation MP Config 1.4 doesn t implement AutoCloseable behaviour on ConfigSource and Converter classes. Developers create [MP issue|https://github.com/eclipse/microprofile-config/issues/136], because these specification requirements seems confusing and unclear to them. [This issue|https://github.com/eclipse/microprofile-config/issues/136] is not approved as a bug from MP community. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4859) Layers for application and management core security realms

by Jeff Mesnil (Jira)

Jeff Mesnil created WFCORE-4859: ----------------------------------- Summary: Layers for application and management core security realms Key: WFCORE-4859 URL: https://issues.redhat.com/browse/WFCORE-4859 Project: WildFly Core Issue Type: Enhancement Components: Build System Reporter: Jean Francois Denise Assignee: Jean Francois Denise Fix For: 11.0.0.Beta9 Today core-security-realms contains both realms in the form of feature-groups. By introducing 2 layers for each realm, core-security-realms could then depend optionally on them. being optional, one could exclude security realms. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 2 months

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