Link the published Java SDK API reference from the Java SDK docs#69433
Merged
jason810496 merged 2 commits intoJul 6, 2026
Conversation
The interface-based API section pointed readers at the published JavaDoc without a link, with a TODO left from AIP-108 waiting for the docs site location to exist. The Javadoc publishing pipeline now targets https://airflow.apache.org/docs/java-sdk/stable/, so the placeholder can become a real link, matching how other SDK references are linked.
jason810496
added
kind:documentation
AIP-108: java-sdk
uranusjr
approved these changes
Jul 6, 2026
uranusjr
reviewed
Jul 6, 2026
The site on airflow.apache.org is an HTML rendering of the API, not an actual Javadoc rendering; Javadoc is bundled with the released artifacts instead. The term also fails the docs spell check.
Contributor
Backport successfully created: v3-3-testNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
|
github-actions Bot
pushed a commit
to aws-mwaa/upstream-to-airflow
that referenced
this pull request
Jul 6, 2026
…DK docs (apache#69433) * Link the published Java SDK API reference from the Java SDK docs The interface-based API section pointed readers at the published JavaDoc without a link, with a TODO left from AIP-108 waiting for the docs site location to exist. The Javadoc publishing pipeline now targets https://airflow.apache.org/docs/java-sdk/stable/, so the placeholder can become a real link, matching how other SDK references are linked. * Stop calling the published Java SDK API reference Javadoc The site on airflow.apache.org is an HTML rendering of the API, not an actual Javadoc rendering; Javadoc is bundled with the released artifacts instead. The term also fails the docs spell check. (cherry picked from commit 66798f9) Co-authored-by: Jason(Zhe-You) Liu <68415893+jason810496@users.noreply.github.com>
henry3260
pushed a commit
that referenced
this pull request
Jul 6, 2026
…DK docs (#69433) (#69448) * Link the published Java SDK API reference from the Java SDK docs The interface-based API section pointed readers at the published JavaDoc without a link, with a TODO left from AIP-108 waiting for the docs site location to exist. The Javadoc publishing pipeline now targets https://airflow.apache.org/docs/java-sdk/stable/, so the placeholder can become a real link, matching how other SDK references are linked. * Stop calling the published Java SDK API reference Javadoc The site on airflow.apache.org is an HTML rendering of the API, not an actual Javadoc rendering; Javadoc is bundled with the released artifacts instead. The term also fails the docs spell check. (cherry picked from commit 66798f9) Co-authored-by: Jason(Zhe-You) Liu <68415893+jason810496@users.noreply.github.com>
vatsrahul1001
pushed a commit
that referenced
this pull request
Jul 7, 2026
…DK docs (#69433) (#69448) * Link the published Java SDK API reference from the Java SDK docs The interface-based API section pointed readers at the published JavaDoc without a link, with a TODO left from AIP-108 waiting for the docs site location to exist. The Javadoc publishing pipeline now targets https://airflow.apache.org/docs/java-sdk/stable/, so the placeholder can become a real link, matching how other SDK references are linked. * Stop calling the published Java SDK API reference Javadoc The site on airflow.apache.org is an HTML rendering of the API, not an actual Javadoc rendering; Javadoc is bundled with the released artifacts instead. The term also fails the docs spell check. (cherry picked from commit 66798f9) Co-authored-by: Jason(Zhe-You) Liu <68415893+jason810496@users.noreply.github.com>
vatsrahul1001
pushed a commit
that referenced
this pull request
Jul 9, 2026
…DK docs (#69433) (#69448) * Link the published Java SDK API reference from the Java SDK docs The interface-based API section pointed readers at the published JavaDoc without a link, with a TODO left from AIP-108 waiting for the docs site location to exist. The Javadoc publishing pipeline now targets https://airflow.apache.org/docs/java-sdk/stable/, so the placeholder can become a real link, matching how other SDK references are linked. * Stop calling the published Java SDK API reference Javadoc The site on airflow.apache.org is an HTML rendering of the API, not an actual Javadoc rendering; Javadoc is bundled with the released artifacts instead. The term also fails the docs spell check. (cherry picked from commit 66798f9) Co-authored-by: Jason(Zhe-You) Liu <68415893+jason810496@users.noreply.github.com>
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
2 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.
Why
The Java SDK guide left an AIP-108 TODO in place of a Javadoc link. The docs pipeline now targets https://airflow.apache.org/docs/java-sdk/stable/, so the placeholder can become a real link.
What
API referencesection tolanguage-sdks/java.rst, mirroring the Go SDK one from Link pkg.go.dev API reference from the Go SDK docs #69429.Java SDK API Referencelink.Was generative AI tooling used to co-author this PR?