-
Notifications
You must be signed in to change notification settings - Fork 663
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(deps): update org.apache.logging.log4j:* to v2.24.1 #2047
base: main
Are you sure you want to change the base?
Conversation
0818e1b
to
5a53112
Compare
⚠ Artifact update problemRenovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is. ♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
The artifact failure details are included below: File name: undefined
|
69c78e8
to
f514b6c
Compare
f514b6c
to
de4547b
Compare
de4547b
to
d05ff94
Compare
d05ff94
to
6802377
Compare
6802377
to
cd94764
Compare
9483105
to
609c35c
Compare
This upgrade was tricky. First, it did not compile unless upgrading biz.aQute.bnd to v7.0.0. After that, the build fails, complaining about class versions:
I cannot see that Log4j have officially announced that they require Java 17, although their release note page at https://logging.apache.org/log4j/2.x/release-notes.html says for the 2.22.1 release: "While maintaining compatibility with Java 8, the artifacts in this release where generated using JDK 17, unlike version 2.22.0 that used JDK 11.". @uschindler Can you decode what they mean by this and whether this is likely a bug in the 2.23.0 release or if we cannot upgrade since they require java17? PS: We should start thinking about JDK bump for Solr on main to at least 17. |
I see from apache/logging-log4j2#2232 and other discussions that log4j now tells users to include Log4j as |
Unfortunate that we cannot upgrade due to requirement for Java 17 in a minor release... So will have to stick with the one we have I guess... |
6fc848c
to
2664a2c
Compare
Similar to #1821 i.e. blocked on JDK 17+ -- if I find a third solrbot PR like it I'll create a JIRA and then close out these in favour of that. |
2664a2c
to
6fbb82c
Compare
|
b0f912f
to
3705cc6
Compare
3705cc6
to
9a459a8
Compare
9a459a8
to
707baf8
Compare
707baf8
to
cd545d9
Compare
cd545d9
to
fe877ca
Compare
fe877ca
to
a10b608
Compare
a10b608
to
ae7a8b1
Compare
This PR contains the following updates:
2.21.0
->2.24.1
2.21.0
->2.24.1
2.21.0
->2.24.1
2.21.0
->2.24.1
2.21.0
->2.24.1
2.21.0
->2.24.1
Configuration
📅 Schedule: Branch creation - "* * * * *" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR has been generated by Renovate Bot