docs: make current javadoc build deterministic

The docs Javadoc script first installs reactor artifacts, then runs the explicit Maven Javadoc goal and copies the generated core API docs.

Running the install phase with Maven parallelism can race module-local annotation processor resolution: examples may try to resolve the current java-driver-mapper-processor snapshot before that module has been installed into the local Maven repository. Run the preliminary install serially so the docs Javadoc target is reproducible from a clean local repository or CI worker.

Also accept the current maven-javadoc-plugin output location, core/target/reports/apidocs, while keeping the previous core/target/site/apidocs path as a fallback. The explicit Javadoc goal passes but writes to reports/apidocs with the current plugin, so copying only site/apidocs makes the docs target fail after successful Javadoc generation.

Author: dkropachev

docs/_utils/javadoc.sh

@@ -2,7 +2,7 @@
 set -euo pipefail
 
 # Install dependencies
-mvn install -DskipTests -Dmaven.javadoc.skip=true -T 1C
+mvn install -DskipTests -Dmaven.javadoc.skip=true
 
 # Define output folder
 OUTPUT_DIR="docs/_build/dirhtml/api"
@@ -13,8 +13,16 @@ fi
 
 # Generate javadoc
 mvn javadoc:javadoc -T 1C
+JAVADOC_SOURCE_DIR="core/target/site/apidocs"
+if [[ ! -d "$JAVADOC_SOURCE_DIR" && -d "core/target/reports/apidocs" ]]; then
+    JAVADOC_SOURCE_DIR="core/target/reports/apidocs"
+fi
+if [[ ! -d "$JAVADOC_SOURCE_DIR" ]]; then
+    echo "Javadoc output directory was not generated" >&2
+    exit 1
+fi
 if [[ -d "$OUTPUT_DIR" ]]; then
     rm -r "$OUTPUT_DIR"
 fi
 mkdir -p "$OUTPUT_DIR"
-mv -f core/target/site/apidocs/* "$OUTPUT_DIR"
+mv -f "$JAVADOC_SOURCE_DIR"/* "$OUTPUT_DIR"