Update dependency org.jboss.logging:jboss-logging to v3.5.0.Final
This MR contains the following updates:
Package | Change | Age | Adoption | Passing | Confidence |
---|---|---|---|---|---|
org.jboss.logging:jboss-logging (source) |
3.3.2.Final -> 3.5.0.Final
|
Release Notes
jboss-logging/jboss-logging
v3.5.0.Final
Release Notes
Feature Request
- [JBLOGGING-133] - Support specification of existing logging provider other than by system property.
Bug
- [JBLOGGING-147] - The log4j2 provider should not use object messages for messages with no parameters
Task
- [JBLOGGING-146] - Add tests for the various backend log managers
Enhancement
- [JBLOGGING-97] - Object value passed to JBossLogManagerProvider.putMdc(String, Object) should be returned from getMdc(final String)
- [JBLOGGING-162] - Require Java 11 as a minimum for the runtime
v3.4.3.Final
Release Notes
Bug
- [JBLOGGING-158] - Upgrade jboss logging log4j dependency versions to 2.17.0 and above
Task
- [JBLOGGING-157] - Add testing for Java 17
Component Upgrade
- [JBLOGGING-150] - Upgrade jboss-parent to 39
- [JBLOGGING-151] - Upgrade logback to 1.2.8
- [JBLOGGING-152] - Upgrade log4j to 1.2.17
- [JBLOGGING-153] - Upgrade log4j 2 to 2.16.0
- [JBLOGGING-154] - Upgrade JBoss Log Manager to 2.1.18.Final
- [JBLOGGING-155] - Upgrade JUnit to 5.8.2
- [JBLOGGING-156] - Upgrade slf4j to 1.7.32
v3.4.2.Final
: JBoss Logging 3.4.2.Final
Release Notes - JBoss Logging - Version 3.4.2.Final
Feature Request
- [ JBLOGGING-144 ] Upgrade jboss-parent to version 36 as 34 has unbounded range in all profiles
Bug
- [ JBLOGGING-147 ] The log4j2 provider should not use object messages for messages with no parameters
Task
- [ JBLOGGING-146 ] Add tests for the various backend log managers
- [ JBLOGGING-149 ] Use a hard-coded name for the debug logger name
v3.4.1.Final
: JBoss Logging 3.4.1.Final
Release Notes - JBoss Logging - Version 3.4.1.Final
Enhancement
- [JBLOGGING-140] - Avoid ClassCastException in Slf4jLoggerProvider
- [JBLOGGING-141] - At Logger.getMessageLogger, safeguard the doPrivileged call by a SecurityManager check
v3.4.0.Final
v3.3.3.Final
: JBoss Logging 3.3.3.Final
Release Notes - JBoss Logging - Version 3.3.3.Final
Enhancement
- [JBLOGGING-141] - At Logger.getMessageLogger, safeguard the doPrivileged call by a SecurityManager check
Configuration
-
If you want to rebase/retry this MR, check this box
This MR has been generated by Renovate Bot.
Edited by Ghost User