Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move ConversantMedia disruptor blocking queue to new module #2914

Merged
merged 1 commit into from
Sep 6, 2024

Conversation

ppkarwasz
Copy link
Contributor

This PR moves the DisruptorBlockingQueue plugin to a new log4j-conversant module.

This change is necessary to remove an optional dependency from log4j-core.

@ppkarwasz ppkarwasz self-assigned this Sep 3, 2024
@ppkarwasz ppkarwasz requested a review from vy September 3, 2024 10:47
Copy link
Member

@vy vy left a comment

Choose a reason for hiding this comment

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

LGTM.

@vy vy added performance Issues or PRs that affect performance, throughput, latency, etc. appenders Affects one or more Appender plugins async Affects asynchronous loggers or appenders and removed performance Issues or PRs that affect performance, throughput, latency, etc. labels Sep 4, 2024
Moves `DisruptorBlockingQueue` to a separate module.

Includes peer review (cf. #2914).
@ppkarwasz ppkarwasz force-pushed the feature/main/move-conversant branch from d76181e to f25c5e4 Compare September 6, 2024 11:38
@ppkarwasz ppkarwasz merged commit f25c5e4 into main Sep 6, 2024
3 of 8 checks passed
@ppkarwasz ppkarwasz deleted the feature/main/move-conversant branch September 6, 2024 11:38
ppkarwasz added a commit that referenced this pull request Sep 12, 2024
Moves `DisruptorBlockingQueue` to a separate module.

Includes peer review (cf. #2914).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
appenders Affects one or more Appender plugins async Affects asynchronous loggers or appenders
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants