[GEODE-10516] Java Documentation Modernization: Stable Aggregation, Legacy Tomcat Neutralization, and Compliance Readiness#7926
Open
JinwooHwang wants to merge 11 commits intoapache:developfrom
Open
Conversation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Java Documentation Modernization: Stable Aggregation, Legacy Tomcat Neutralization, and Compliance Readiness
Summary
This pull request restores and stabilizes the aggregate Javadoc build (
:geode-assembly:docs) under Gradle 7 by:javadocStubssource set containing minimal legacy Tomcat API placeholders.LifecycleSupport,SerializablePrincipal, etc.) without bundling obsolete Tomcat 6/7 artifacts.Result: The aggregate Javadoc builds cleanly, includes intended Geode modules, excludes unwanted external Tomcat API docs, and is positioned for later enforcement hardening.
Motivation
Previously the aggregate Javadoc failed due to unresolved Tomcat 6/7 symbols after refactoring. Pulling the Tomcat 6 distribution to recover those types was brittle and noisy. Excluding affected Geode sources reduced failures but degraded documentation coverage.
Goals addressed:
failOnError=false).-Xwerrorenforcement.Key Changes
Build (
geode-assembly/build.gradle)sourceSets { javadocStubs { ... } }.exclude 'org/apache/catalina/**'.options.addStringOption('Xwerror','-quiet').Stub Classes (with ASF headers)
Located under:
geode-assembly/src/javadocStubs/java/org.apache.catalina.util.LifecycleSupportorg.apache.catalina.ha.session.SerializablePrincipalorg.apache.catalina.LifecycleListenerorg.apache.catalina.Realmorg.apache.catalina.realm.GenericPrincipalThey intentionally contain only the signatures required for symbol resolution.
Javadoc Assembly
javadocOnlydependency projects.Rationale
org.apache.catalina.*-XwerrorVerification
Performed:
:geode-assembly:docs.For all changes:
Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?
Has your PR been rebased against the latest commit within the target branch (typically
develop)?Is your initial contribution a single, squashed commit?
Does
gradlew buildrun cleanly?Have you written or updated unit tests to verify your changes?
If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?