Backport: Fix Byte Buddy dependency scope for unit testing (#2755) #2766
Conversation
This file contains hidden or 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
Ananya2
requested review from
David-Engel,
divang,
machavan and
muskan124947
muskan124947
approved these changes
Sep 10, 2025
divang
approved these changes
Sep 10, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Overview
This PR backports the fix from #2755 into the release/13.2 branch.
Issue
One of the recently added testing dependencies (Byte Buddy 1.15.11) was left with the default compile scope instead of test. This resulted in the ~8.1 MB jar being included in runtime artifacts.
Resolution
Updated the POM to set the scope to test for the missed dependency.
Validation:
mvn dependency:treenow shows Byte Buddy only undertestscope