This is an automated email from the ASF dual-hosted git repository.
tbonelee pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/zeppelin.git
The following commit(s) were added to refs/heads/master by this push:
new a6b101ebf1 [ZEPPELIN-6725] Remove obsolete Py4J download properties
from build g…
a6b101ebf1 is described below
commit a6b101ebf1bf630a92677babd5fb8b232d7aeb4b
Author: YooJung Huh <[email protected]>
AuthorDate: Mon Oct 5 22:17:34 2026 +0900
[ZEPPELIN-6725] Remove obsolete Py4J download properties from build g…
### 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.version` entry aligned with the real Maven dependency version used
in `pom.xml`. No build behavior, dependency version, or runtime artifact
changes are included.
### What type of PR is it?
Documentation
### Todos
* [x] Update the build guide to remove unused Py4J download configuration
entries
* [x] Clarify that python.py4j.version is the Maven dependency version
* [x] Align the documented default with `pom.xml`
* [x] Keep bundled Py4J source ZIP behavior clearly separated from the
Maven dependency
### What is the Jira issue?
* https://issues.apache.org/jira/browse/ZEPPELIN-6725
* PR title includes: [ZEPPELIN-6725]
### How should this be tested?
* Confirm that no repository references remain for `pypi.repo.url` or
`python.py4j.repo.folder`
* Compare the documented `python.py4j.version` default with `pom.xml`
* Review the “Optional configurations” section to confirm it no longer
describes non-existent Py4J download properties
### Screenshots (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
Closes #5542 from gjenfwo/ZEPPELIN-6725.
Signed-off-by: ChanHo Lee <[email protected]>
---
docs/setup/basics/how_to_build.md | 7 ++-----
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/docs/setup/basics/how_to_build.md
b/docs/setup/basics/how_to_build.md
index 8109852084..ea40a59987 100644
--- a/docs/setup/basics/how_to_build.md
+++ b/docs/setup/basics/how_to_build.md
@@ -165,14 +165,11 @@ Py4J package
```bash
python.py4j.version # default 0.10.7
-pypi.repo.url # default https://files.pythonhosted.org
-python.py4j.repo.folder # default
/packages/dd/03/d83f659f045d819fc7550dd472b3831fe8c8fa7204c6428270a46a4a5ab9/
```
-final URL location for Py4J package will be produced as following:
-
-`${pypi.repo.url}${python.py4j.repo.folder}py4j-${python.py4j.version}.zip`
+`python.py4j.version` is the Maven dependency version used for
`net.sf.py4j:py4j` in the Python build.
+The bundled Python-side Py4J source ZIP used at runtime is a separate artifact
from the Maven dependency and is not controlled by this property.
Frontend Maven Plugin configurations
