-
Notifications
You must be signed in to change notification settings - Fork 244
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Release build of v22.04.0 FAILED on "Execution attach-javadoc failed: NullPointerException" with maven option '-P source-javadoc' #5050
Comments
Is
exporting |
Thanks @jlowe exporting JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64 works for me. I got another failure as below after adding
.....
|
As javadoc of
so
Invoking Then mvn CLI: would failed with no jars
To fix: Add configuration |
To fix issue NVIDIA#5050 1, Add JAVA_HOME for maven opt `-P source-javadoc` 2, Change to use maven opt `-P release311` instead of `-P release301` 3, Add configuration `<detectOfflineLinks>` for maven-javadoc-plugin: Not detecting the links for all modules defined in the project: https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-no-fork-mojo.html#detectOfflineLinks To [ERROR] `The specified file '/home/jenkins/agent/workspace/jenkins-tim-rapids-release-11/dist/target/rapids-4-spark_2.12-22.04.0.jar' not exists` Signed-off-by: Tim Liu <timl@nvidia.com>
* Update for the public release To fix issue #5050 1, Add JAVA_HOME for maven opt `-P source-javadoc` 2, Change to use maven opt `-P release311` instead of `-P release301` 3, Add configuration `<detectOfflineLinks>` for maven-javadoc-plugin: Not detecting the links for all modules defined in the project: https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-no-fork-mojo.html#detectOfflineLinks To [ERROR] `The specified file '/home/jenkins/agent/workspace/jenkins-tim-rapids-release-11/dist/target/rapids-4-spark_2.12-22.04.0.jar' not exists` Signed-off-by: Tim Liu <timl@nvidia.com> * Update 'integration-tests/pom.xml' to keep links for all modules defined in the project Signed-off-by: Tim Liu <timl@nvidia.com>
Describe the bug
Release build of v22.04.0 FAILED with maven option '-P source-javadoc' as below
CLI:
BUILD ERRORS:
Steps/Code to reproduce bug
mvn clean package -pl '!tools' -P source-javadoc -Dcuda.version=cuda11 -Dbuildver=311 -DskipTests=false
Expected behavior
Build get PASS, and sources.jar/javadoc.jar can be generated along with spark-rapids artifacts
Environment details (please complete the following information)
Additional context
OSS requires sources.jar/javadoc.jar along with spark-rapids artifacts for the pubic release,
so we weed run maven with option
-P source-javadoc
to generate sources.jar/javadoc.jar files.The text was updated successfully, but these errors were encountered: