Skip to content

[Backport] [37.0.0] fix: package logging emitter resource and rename to avoid classpath issues#19371

Merged
cecemei merged 1 commit into37.0.0from
backport-2de75ab1d74c8ba6c9623654cb69f9cd71442007-to-37.0.0
Apr 24, 2026
Merged

[Backport] [37.0.0] fix: package logging emitter resource and rename to avoid classpath issues#19371
cecemei merged 1 commit into37.0.0from
backport-2de75ab1d74c8ba6c9623654cb69f9cd71442007-to-37.0.0

Conversation

@github-actions
Copy link
Copy Markdown

{
"backport_issue": "19363",
"message": "Backport for #19363"
}

…ssues (#19359)

The previous fix broadly added src/main/resources as a resource directory,
which inadvertently packaged log4j2.xml, log4j2.debug.xml, and the
services/javax.annotation.processing.Processor file into druid-processing.jar.

The packaged log4j2.xml (console-only) ends up on the classpath of dependent
modules like indexing-service and shadows processing's test log4j2.xml that
contains the RoutingAppender used to route task logs to per-task files. This
caused ThreadingTaskRunnerTest#test_streamTaskLogs_ofRunningTask_readsFromTaskLogFile
to fail because the per-task log file was never written.

Narrow the include to only loggingEmitterAllowedMetrics.json so behavior for
every other file in processing/src/main/resources matches pre-PR state.

Co-authored-by: Sarang Vadali <sarangvadali@salesforce.com>
(cherry picked from commit 2de75ab)
@cecemei cecemei mentioned this pull request Apr 23, 2026
10 tasks
@cecemei cecemei merged commit 13da69b into 37.0.0 Apr 24, 2026
58 of 59 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants