Bump org.jboss.logmanager:log4j2-jboss-logmanager from 1.1.2.Final to 2.0.1.Final #42559
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
dependabot
bot
added
the
area/dependencies
This comment has been minimized.
This comment has been minimized.
|
@jamezp what's the strategy here? Are all the adapters compatible with this new version? Should we update to it or not? (you can ignore CI for now, I think we ended up in the middle of a GitHub Action outage, I will rerun CI depending on what the plan is) |
|
Hi @gsmet. I'll update the release notes and the README. The 2.0.x versions only work with log4j 2.23+ because of apache/logging-log4j2#2249. The jboss-logging/log4j2-jboss-logmanager#82 was the change in the log4j2-jboss-logmanager. I decided since it was a major bump, that requiring a minimum of 2.23 seemed okay. |
Bumps [org.jboss.logmanager:log4j2-jboss-logmanager](https://github.com/jboss-logging/log4j2-jboss-logmanager) from 1.1.2.Final to 2.0.1.Final. - [Release notes](https://github.com/jboss-logging/log4j2-jboss-logmanager/releases) - [Commits](jboss-logging/log4j2-jboss-logmanager@1.1.2.Final...2.0.1.Final) --- updated-dependencies: - dependency-name: org.jboss.logmanager:log4j2-jboss-logmanager dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
gsmet
force-pushed
the
dependabot/maven/org.jboss.logmanager-log4j2-jboss-logmanager-2.0.1.Final
branch
from
e6a1d3b
to
5d02934
Compare
Status for workflow
|
dependabot
bot
deleted the
dependabot/maven/org.jboss.logmanager-log4j2-jboss-logmanager-2.0.1.Final
branch
Bumps org.jboss.logmanager:log4j2-jboss-logmanager from 1.1.2.Final to 2.0.1.Final.
Release notes
Sourced from org.jboss.logmanager:log4j2-jboss-logmanager's releases.
Commits
6e3b9c9Prepare for 2.0.1.Final release898b83dMerge pull request #95 from jamezp/issue942169187[94] Ensure the level is set in a privileged action if the security manager i...0c14d61Next is 2.0.1.Finala3787f9Prepare for 2.0.0.Final release131f6d8Fix the JavaDoc issue created by the module-info plugin. For whatever reason,...f357ab2Merge pull request #93 from jamezp/issue923ab9ca6[92] Allow the ThreadContextMDCMap to work with both the JBoss Log Manager 3....1a30abbMerge pull request #86 from jboss-logging/dependabot/maven/org.jboss.logmanag...c9cc876Merge pull request #91 from jboss-logging/dependabot/maven/org.junit-junit-bo...You can trigger a rebase of this PR by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)