KAFKA-18752: Fix the warning of no-operation caused by slf4j in building kafka#19501
KAFKA-18752: Fix the warning of no-operation caused by slf4j in building kafka#19501frankvicky wants to merge 57 commits intoapache:trunkfrom
Conversation
…ing kafka JIRA: KAFKA-18752 In KAFKA-18466 we remove the slf4j impl from runtime scope to fix the compatible issue (see apache#17373 (comment)). However, that also causes a side effect that in running some tasks slf4k can't find any provider as they are included to "release-only" We could fix this by adding releasOnly to class path
github-actions
bot
added
triage
|
Build output: |
m1a2st
left a comment
m1a2st
left a comment
There was a problem hiding this comment.
There is an typo in your description 'slf4k' should be 'slf4j'
|
This PR is being marked as stale since it has not had any activity in 90 days. If you If you are having difficulty finding a reviewer, please reach out on the [mailing list](https://kafka.apache.org/contact). If this PR is no longer valid or desired, please feel free to close it. If no activity occurs in the next 30 days, it will be automatically closed. |
|
This PR has been closed since it has not had any activity in 120 days. If you feel like this |
2 participants
JIRA: KAFKA-18752 In KAFKA-18466, we remove the slf4j impl from runtime
scope to fix the compatibility issue (see
#17373 (comment)).
However, that also causes a side effect: when running some tasks, slf4j
can't find any provider as they are included in "release-only". We could
fix this by adding releaseOnly to the class path.
This patch leverages the task collection API to enable specific tasks to
access
releaseOnlydependencies.