Skip to content

Update dependency org.jboss.logging:jboss-logging to v3.5.0.Final - autoclosed

Ghost User requested to merge renovate/jboss.logging.version into master

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 age adoption passing confidence

Release Notes

jboss-logging/jboss-logging

v3.5.0.Final

Compare Source

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

Compare Source

Release Notes

Bug

  • [JBLOGGING-158] - Upgrade jboss logging log4j dependency versions to 2.17.0 and above

Task

Component Upgrade

v3.4.2.Final

Compare Source

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

Compare Source

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

Compare Source

v3.3.3.Final

Compare Source

Release Notes - JBoss Logging - Version 3.3.3.Final

Enhancement

  • [JBLOGGING-141] - At Logger.getMessageLogger, safeguard the doPrivileged call by a SecurityManager check

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever MR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this MR and you won't be reminded about this update again.


  • If you want to rebase/retry this MR, click this checkbox.

This MR has been generated by Renovate Bot.

Edited by Ghost User

Merge request reports