Skip to main content

sphinx-java-autodoc

CI Documentation

Publish your Java library's guides and API reference in one searchable Sphinx site. Keep API contracts in Java sources and Javadoc; write guides that help your users choose an API and complete a task.

sphinx-java-autodoc reads Java sources and Javadoc comments with the JDK compiler APIs and renders them as native Sphinx content:

  • Generated, searchable pages for classes, interfaces, enums, records, annotation types and nested types.
  • Signatures, overloads, Javadoc links and inherited method documentation.
  • Class excerpts in handwritten guides, and links between projects through intersphinx.
  • Pages that refresh when sources change, with content-based extraction caching.

Extraction never executes application classes or annotation processors, and never downloads Java dependencies. See the Apache Commons Lang example for what the output looks like.

Requirements

Python 3.12+, Sphinx 9.1.x, and JDK 25 for extraction. Your library can keep targeting Java 17 or 21. See compatibility and limits for the tested versions.

Quick start

uv add "sphinx-java-autodoc @ git+https://github.com/r4sky0/sphinx-java-autodoc.git"

In docs/conf.py:

extensions = ["sphinx_java_autodoc"]
java_sources = ["../src/main/java"]
java_release = "17"
java_generate = "api"
java_visibility = "public"

Add api/index to the toctree in docs/index.rst, then build:

uv run sphinx-build -W --keep-going -n docs docs/_build/html

Publish your first API pages walks through these steps. Then continue with:

Development

From a clone of this repository:

uv sync --locked
uv run --locked pre-commit install
uv run --locked pre-commit run --all-files
uv run --locked pytest
uv run --locked --group showcase python showcase/build.py
uv run --locked sphinx-build -W --keep-going -n docs docs/_build/html

Development and releases are documented in CONTRIBUTING.md. CI covers lint, compiler warnings, integration tests, built distributions, dependency vulnerabilities, six HTML themes, the text builder, and Chromium browser interactions.

MIT licensed.

Metadata

Release files for sphinx-java-autodoc 0.2.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for sphinx-java-autodoc 0.2.0
File Size Uploaded
sphinx_java_autodoc-0.2.0.tar.gz 85.8 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for sphinx-java-autodoc 0.2.0
File Interpreter ABI Platform
sphinx_java_autodoc-0.2.0-py3-none-any.whl Python 3 none any Details

Total release size: 120.7 kB

Release files / sphinx_java_autodoc-0.2.0.tar.gz

Download URL sphinx_java_autodoc-0.2.0.tar.gz
Size 85.8 kB
Tags Source
SHA-256 checksum
How to use checksums
8073cee555af38aad74dd6b9cdd050eec41627a4792da7443720bd69c66bbdef
BLAKE2b-256 checksum
How to use checksums
c3349a7efe8fc88d7298a65044e0ec1e369b9f08edac061ce7426d3c7977355c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 12, 2026.

Transparency log

Release files / sphinx_java_autodoc-0.2.0-py3-none-any.whl

Download URL sphinx_java_autodoc-0.2.0-py3-none-any.whl
Size 34.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
2fd0cb2e9202316bc533d9ca63507520d4092846aefb7f32f16c017aa511dd60
BLAKE2b-256 checksum
How to use checksums
2f2e57be417b2065eff08d176231c06648ffa036fb35506b4dc5383be46b8c73
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 12, 2026.

Transparency log

Release history Release notifications | RSS feed

0.2.1

2 release files

This release

0.2.0 This release

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page