Skip to content

Support for unplanned logger calls#221

Open
SgtOmer wants to merge 5 commits intoapache:mainfrom
SgtOmer:sgtomer/support_unplanned_logger_methods
Open

Support for unplanned logger calls#221
SgtOmer wants to merge 5 commits intoapache:mainfrom
SgtOmer:sgtomer/support_unplanned_logger_methods

Conversation

@SgtOmer
Copy link
Copy Markdown

@SgtOmer SgtOmer commented Sep 1, 2025

#220 - implemented the fix suggested

@SgtOmer SgtOmer force-pushed the sgtomer/support_unplanned_logger_methods branch 3 times, most recently from 5075442 to 6870b83 Compare September 6, 2025 15:21
@SgtOmer SgtOmer force-pushed the sgtomer/support_unplanned_logger_methods branch from 6870b83 to e924f9b Compare September 6, 2025 15:24
@SgtOmer
Copy link
Copy Markdown
Author

SgtOmer commented Sep 6, 2025

Sorry for the mess with all the force pushes, had a problem with the signing and the git name

@ppkarwasz ppkarwasz self-requested a review September 7, 2025 14:32
Copy link
Copy Markdown
Contributor

@ppkarwasz ppkarwasz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @SgtOmer,

Sorry for the late review.

My initial idea was to fail, whenever there is a new method we didn't take into consideration, but you are probably right: if an unsupported method from the Log4j API is called, we can just pass it through.

@github-project-automation github-project-automation bot moved this from In review to Approved in Log4j pull request tracker Apr 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Development

Successfully merging this pull request may close these issues.

2 participants