This repository has been archived by the owner on Apr 23, 2024. It is now read-only.
Adding new module with supporting graalvm appenders #62
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
…mitry Kubakhov <[email protected]> Signed-off-by: DmitryKubakhov <[email protected]>
DmitryKubahov
force-pushed
the
feature/graalvm_support
branch
from
1efa48b
to
93b22d7
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
GraalVM has several phases while building and running an image. During the build phase, the appender could not initialize any thread or file descriptor. With this information, we cannot use AsynAppender and FileAppender.
This PR contains 2 new appenders:
All initialization will be done only in the not build phase or in
doAppendmethod.This PR should fix this issue: https://jira.qos.ch/browse/LOGBACK-1550