yihua opened a new issue, #20237: URL: https://github.com/apache/hudi/issues/20237
Every PR on this repo shows red "cannot find symbol" check annotations on files it never touched, for example on #19914 and #20215. They come from `maven-javadoc-plugin:jar (attach-javadocs)`, which the `validate-bundles` job runs through `-DdeployArtifacts=true`. The javadoc plugin only puts dependency artifacts on javadoc's classpath, not the module's own `target/classes`. Java sources that import Scala classes compiled in the same module therefore do not resolve: `hudi-spark-client` fails with 94 errors (`SparkAdapterSupport$`, `HoodieInternalRowUtils`, `HoodieSchemaConversionUtils`, ...) and `hudi-spark-common` with 1 (`DataSourceWriteOptions`). `failOnError=false` keeps the build green, so the published javadoc jars for those modules are incomplete and the errors only surface as annotations that bury real ones. Proposal: in the `deployArtifacts` profile, add the module's own jar to javadoc's classpath through `additionalDependencies` (system scope, `systemPath` pointing at the jar `jar:jar` builds earlier in the package phase), mirroring how cross-module Scala references already resolve through dependency jars. -- 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]
