Hi All:

I'd like to build Apache Commons components with the build failing if there are 
Javadoc warnings. This idea would fail today for all components because we get 
this Javadoc warning:

[INFO] --- javadoc:3.10.1:javadoc (default-cli) @ commons-csv ---
[INFO] Configuration changed, re-generating javadoc.
[WARNING] Javadoc Warnings
[WARNING] warning: The code being documented uses packages in the unnamed 
module, but the packages defined in 
https://docs.oracle.com/en/java/javase/21/docs/api/ are in named modules.
[WARNING] 1 warning

For example, the above is from:

git clone https://gitbox.apache.org/repos/asf/commons-csv.git
cd commons-csv
mvn clean package javadoc:javadoc -DskipTests -Dcommons.javadoc.version=3.11.2

- The target byte code is Java 8, I never build with Java 8, always 17 or 21.
- The GitHub CI builds with all Java LTS versions plus the latest and the 
latest EA.
- The target JAR file includes JPMS module info generated by the Moditect 
plugin, works like a charm.

Googling doesn't help much, using -X to get debug output doesn't seem helpful 
to me, but it is interesting that -X does not enable "verbose" for the Javadoc 
command. 

Is this some more JPMS messiness that I somehow need to account for in my POM? 
If so, any clues as to how do it?

TY!
Gary

PS: My setup today:

Microsoft Windows [Version 10.0.19045.5131]
~
openjdk version "21.0.4" 2024-07-16 LTS
OpenJDK Runtime Environment Temurin-21.0.4+7 (build 21.0.4+7-LTS)
OpenJDK 64-Bit Server VM Temurin-21.0.4+7 (build 21.0.4+7-LTS, mixed mode, 
sharing)
~
Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937)
Maven home: C:\java\apache-maven-3.9.9
Java version: 21.0.4, vendor: Eclipse Adoptium, runtime: C:\Program 
Files\Eclipse Adoptium\jdk-21.0.4.7-hotspot
Default locale: en_US, platform encoding: UTF-8
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
~
Docker version 27.3.1, build ce12230


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to