AVRO-4154: Make tools jar multi-release #3406
Merged
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
Some dependencies use multi-release jars. This change ensures they are included fully.
Contributor
Author
|
Rerunning docker tests (succeeded locally, pipeline failed due to network timeout) |
opwvhk
added a commit
that referenced
this pull request
Jun 13, 2025
opwvhk
added a commit
that referenced
this pull request
Jun 14, 2025
opwvhk
added a commit
to opwvhk/avro
that referenced
this pull request
Sep 5, 2025
Some dependencies use multi-release jars. This change ensures they are included fully.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What is the purpose of the change
AVRO-4154: Fix python tests running in Docker
Some dependencies use multi-release jars. This change ensures they are
included fully, by making the tools jar also a multi-release jar.
Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
If the change is good, the docker pipeline will succeed.
Documentation
yes/ no)docs / JavaDocs / not documented)