The GitHub Actions job "Java CI" on commons-xml.git/fix/javadoc-ci-split has succeeded. Run started by GitHub user ppkarwasz (triggered by ppkarwasz).
Head commit for run: c285755ad2de172f11d8b51e5e5d69896b1329ed / Piotr P. Karwasz <[email protected]> ci: run Javadoc in a dedicated job instead of every matrix build Every non-GraalVM matrix entry runs bare `mvn`, which falls through to pom.xml's <defaultGoal> and so generates Javadoc eleven times, on seven JDK majors across two operating systems. commons-parent sets failOnWarnings=true, so a single warning from any one of those JDKs fails an otherwise good build. That is what is currently red on every open PR and on main. The three JDK 8 jobs (temurin 8, semeru 8, zulu 8.0.201) fail with: javadoc: warning - Error fetching URL: https://jakarta.ee/specifications/platform/8/apidocs/ An error has occurred in Javadoc report generation: Project contains Javadoc Warnings The link comes from commons-parent; JDK 8's javadoc can no longer fetch it, JDK 9+ can. Nothing in any branch causes it: a dependabot version bump fails identically, and main went red with no relevant code change. Give the build job an explicit goal list that omits javadoc:javadoc, and add one `javadoc` job on temurin 25 that runs it. Javadoc output varies by JDK, so pinning the check to a single modern JDK keeps that variance from failing unrelated builds, and drops eleven redundant Javadoc runs from the matrix. Windows to match the matrix's primary OS. The GraalVM row keeps its own maven-args override. pom.xml's <defaultGoal> deliberately keeps javadoc:javadoc, so a bare local `mvn` still checks it as README.md and CONTRIBUTING.md instruct; only CI overrides the list. The two need to stay in sync. Assisted-By: Claude Opus 5 (1M context) <[email protected]> Report URL: https://github.com/apache/commons-xml/actions/runs/32381509277 With regards, GitHub Actions via GitBox
