MODINVUP-91: ERROR StatusLogger Log4j2: Add log4j-core to classpath #101
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…classpath. ``` java -jar target/mod-inventory-update-fat.jar ERROR StatusLogger Log4j2 could not find a logging implementation. Please add log4j-core to the classpath. Using SimpleLogger to log to the console... ``` I can reproduce this bug locally and with the latest master branch container folioci/mod-inventory-update:3.2.2-SNAPSHOT.115. The cause is vert-x3/vertx-dependencies#179 and it can be fixed by moving log4j-bom before vertx-stack-depchain in `<dependencyManagement>` as explained in https://github.com/folio-org/raml-module-builder/blob/v35.1.2/doc/upgrading.md#version-351
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I can reproduce this bug locally and with the latest master branch container folioci/mod-inventory-update:3.2.2-SNAPSHOT.115.
The cause is vert-x3/vertx-dependencies#179 and it can be fixed by moving log4j-bom before vertx-stack-depchain in
<dependencyManagement>as explained in https://github.com/folio-org/raml-module-builder/blob/v35.1.2/doc/upgrading.md#version-351