You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by GitBox <gi...@apache.org> on 2023/01/05 13:00:45 UTC

[GitHub] [logging-log4j2] ppkarwasz commented on pull request #1192: fix(sec): upgrade org.slf4j:slf4j-ext to 1.7.26

ppkarwasz commented on PR #1192:
URL: https://github.com/apache/logging-log4j2/pull/1192#issuecomment-1372186537

   @whiteChen233,
   
   As you can see from the comment:
   
   > Do not upgrade the SLF4J version. 1.7.26 broke backward compatibility. Users can update the version if they do not require support for SLF4J's `EventData`.
   
   we intentionally maintain backward compatibility with `slf4j-ext` version 1.7.25. It is up to the user to choose the version of `slf4j-ext` he wishes to use. If he uses `EventData`, `log4j-slf4j-impl` has support for it.
   
   Personally I would accept a PR that uses `sl4f-ext` 1.7.25 to compile the artifact, but bumps the version in the published POM. Basically we **need** 1.7.25 to compile the artifact, but we wish version 1.7.36 to appear as the **recommended** version of `slf4j-ext`. @vy, any idea which Maven plugin can do this?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@logging.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org