Bump ver.slf4j from 1.7.36 to 2.0.0
Bumps ver.slf4j from 1.7.36 to 2.0.0.
Updates slf4j-api from 1.7.36 to 2.0.0
Commits
0614d46prepare release 2.0.0b1afcd0javadoc edits20cd3adstart work on 2.0.0-SNAPSHOTaeebb61prepare release 2.0.0-beta11068cd0javadoc changes4e4e56aadd CheckReturnValue annotation in org.slf4j.helpers0dcfa19check for return value in some oggingEventBuilder methodse7ca8d1start work on 2.0.0-beta1-SNAPSHOPT2314de9add setMessage and log method to the fluent API508a796set version to 2.0.0-beta0- Additional commits viewable in compare view
Updates slf4j-jdk14 from 1.7.36 to 2.0.0
Commits
0614d46prepare release 2.0.0b1afcd0javadoc edits20cd3adstart work on 2.0.0-SNAPSHOTaeebb61prepare release 2.0.0-beta11068cd0javadoc changes4e4e56aadd CheckReturnValue annotation in org.slf4j.helpers0dcfa19check for return value in some oggingEventBuilder methodse7ca8d1start work on 2.0.0-beta1-SNAPSHOPT2314de9add setMessage and log method to the fluent API508a796set version to 2.0.0-beta0- Additional commits viewable in compare view
Updates jcl-over-slf4j from 1.7.36 to 2.0.0
Commits
0614d46prepare release 2.0.0b1afcd0javadoc edits20cd3adstart work on 2.0.0-SNAPSHOTaeebb61prepare release 2.0.0-beta11068cd0javadoc changes4e4e56aadd CheckReturnValue annotation in org.slf4j.helpers0dcfa19check for return value in some oggingEventBuilder methodse7ca8d1start work on 2.0.0-beta1-SNAPSHOPT2314de9add setMessage and log method to the fluent API508a796set version to 2.0.0-beta0- Additional commits viewable in compare view
Updates jul-to-slf4j from 1.7.36 to 2.0.0
Commits
0614d46prepare release 2.0.0b1afcd0javadoc edits20cd3adstart work on 2.0.0-SNAPSHOTaeebb61prepare release 2.0.0-beta11068cd0javadoc changes4e4e56aadd CheckReturnValue annotation in org.slf4j.helpers0dcfa19check for return value in some oggingEventBuilder methodse7ca8d1start work on 2.0.0-beta1-SNAPSHOPT2314de9add setMessage and log method to the fluent API508a796set version to 2.0.0-beta0- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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 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)
Let's wait on this one.
If Jena uses 2.0.0, it may block downstream still using 1.7.x.
slf4j 2.0.0 setup works differently to 1.7 (2.0.0 uses service loaders, 1.7.x has it's own private mechanism.
1.8.x didn't get out of beta.
As there is no rush here, let's see how the rest of the world gets on with 2.0.0.
So the question for Jena upgrading is whether slf4j-api 2.0.0 if jena updates, is compatible with 1.7.x slf4j implementations (client apps using jena).
The answer is "no". It looks like a long-timescale change over unless adapters appear.
https://www.slf4j.org/faq.html#changesInVersion200
So I suggest we do not upgrade, wait to see what happens in the rest of the world, and close this PR.
Slight bump in the road: https://issues.apache.org/jira/browse/LOG4J2-3601
If that is not accepted, each inclusion of log4j-slf4j2-impl needs to be paired with an inclusion of log4j-core.
Superseded by #1568.