Open apjanke opened 2 years ago
To run just this step, do mvn javadoc:javadoc
.
$ mvn javadoc:javadoc
[INFO] Scanning for projects...
[INFO]
[INFO] -------------------< net.janklab.shmorg.log4j:log4j >-------------------
[INFO] Building Janklab-Munged Apache Log4j 1.2.15-janklab.1-preview
[INFO] --------------------------------[ jar ]---------------------------------
[INFO]
[INFO] >>> maven-javadoc-plugin:2.10.4:javadoc (default-cli) > generate-sources @ log4j >>>
[INFO]
[INFO] <<< maven-javadoc-plugin:2.10.4:javadoc (default-cli) < generate-sources @ log4j <<<
[INFO]
[INFO]
[INFO] --- maven-javadoc-plugin:2.10.4:javadoc (default-cli) @ log4j ---
[INFO]
4 warnings
[WARNING] Javadoc Warnings
[WARNING] javadoc: warning - No source files for package reference
[WARNING] javadoc: warning - No source files for package syntax
[WARNING] javadoc: warning - No source files for package reference
[WARNING] javadoc: warning - No source files for package syntax
[INFO] ------------------------------------------------------------------------
The command mvn -X javadoc:javadoc
will produce debugging output, but it doesn't have diagnostics directly next to those WARNING messages. Gotta scan the whole output, I guess.
In my log4j 1.2.15's
mvn2 site
build:That seems like an actual issue. Fix it up.
I don't know what package it's referring to there.