chore(dependencies): remove unnecessary dependency on log4j-core #1087
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
and make dependencies on log4j-api explicit.
#1069 introduced the dependency on org.apache.logging.log4j.log4j-core in kork-artifacts, but it's not necessary. At least, after removing it, and verifying the dependency is gone from
the code still builds fine. As well
turns up classes present in log4j-api, but nothing in log4j-core.
As well uses of the
@Log4j2
annotation depend on log4j-api (see https://projectlombok.org/api/lombok/extern/log4j/Log4j2)This all makes the comment in spinnaker-dependencies.gradle true again:
While we're at it, get log4j-bom up to date.