Subham-KRLX opened a new pull request, #2514: URL: https://github.com/apache/sedona/pull/2514
Did you read the Contributor Guide? Yes, I have read the [Contributor Rules](https://sedona.apache.org/latest/community/rule/) and [Contributor Development Guide](https://sedona.apache.org/latest/community/develop/) No, I haven't read it. Is this PR related to a ticket? Yes, and the PR name follows the format [GH-1893] Fix JavaDoc package-list error in docs build workflow. Closes #1893 No: this is a documentation update. The PR name follows the format [DOCS] my subject this is a CI update. The PR name follows the format [CI] my subject What changes were proposed in this PR? This PR fixes the JavaDoc build error reported in issue #1893, where the build failed with Error fetching link: .../common/target/target/apidocs/package-list. The issue was caused by the spark/common module trying to link to the common module's JavaDoc, but the common module's JavaDoc was not being copied to the documentation directory in the GitHub Actions workflow. This patch updates the .github/workflows/docs.yml file to explicitly copy the common module's generated JavaDoc to docs/api/javadoc/common/. This ensures the package-list file exists at the expected location for linking. How was this patch tested? Verified the workflow syntax and path logic. Ran mvn -q clean install -DskipTests locally to ensure the build process works. The CI build for this PR will serve as the final verification. Did this PR include necessary documentation updates? Yes, I am adding a new API. I am using the [current SNAPSHOT version number](https://github.com/apache/sedona/blob/99239524f17389fc4ae9548ea88756f8ea538bb9/pom.xml#L29) in vX.Y.Z format. Yes, I have updated the documentation. No, this PR does not affect any public API so no need to change the documentation. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
