Repository navigation
[ZEPPELIN-6725] Remove obsolete Py4J download properties from build g… - #5542
Merged
Merged
Conversation
tbonelee
requested changes
Oct 5, 2026
tbonelee
left a comment
tbonelee
left a comment
Contributor
There was a problem hiding this comment.
The pom.xml and JIRA links in the description point to local vscode-file:// paths. Since the description becomes the merge commit message, could you fix them?
Contributor
Author
I edited! 😀 |
tbonelee
approved these changes
Oct 5, 2026
Contributor
|
Merged into master |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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 this PR for?
This PR fixes the build documentation for Py4J so it matches the actual Maven configuration in the repository. It removes obsolete properties and URL examples that are not used by the current build, and keeps the documented
python.py4j.versionentry aligned with the real Maven dependency version used inpom.xml. No build behavior, dependency version, or runtime artifact changes are included.What type of PR is it?
Documentation
Todos
Update the build guide to remove unused Py4J download configuration entries
Clarify that python.py4j.version is the Maven dependency version
Align the documented default with
pom.xmlKeep bundled Py4J source ZIP behavior clearly separated from the Maven dependency
What is the Jira issue?
How should this be tested?
pypi.repo.urlorpython.py4j.repo.folderpython.py4j.versiondefault withpom.xmlScreenshots (if appropriate)
Questions:
Does the license files need to update? No
Is there breaking changes for older versions? No
Does this needs documentation? Yes, this PR updates the build documentation