Hiding Javadoc unnecessary warnings by using quiet mode#1522
Hiding Javadoc unnecessary warnings by using quiet mode#1522
Conversation
|
Although I am not added as a reviewer, IMHO I think that removing this is kind of warning seems reasonable. |
|
in line of principle, I do not like to mute warning messages, even if, in all honesty, I don't think we would prioritize fixing those warnings any time soon compared to other more important tasks. |
|
Hi @arcuri82, I'm re-running the job as the build logs expired and I can't download it. Once it's done I will do a diff with a normal build to show you which warnings this hides (which according to my theory are only the warnings that look like this: "Warning: Generating /home/runner/work/EvoMaster/EvoMaster/client-java/controller-api/target/apidocs/org/evomaster/client/java/controller/api/dto/class-use/ActionDto.html..." while leaving the ones like this: "Warning: /home/runner/work/EvoMaster/EvoMaster/client-java/controller-api/src/main/java/org/evomaster/client/java/controller/api/ControllerConstants.java:15: warning: no comment |
|
Hi @arcuri82 here are 2 builds with and without Javadoc quiet mode: Scanned through them and the result is as I expected. AI summary: - The no-quiet build adds 1,355 Javadoc doclet progress lines, such as
Let me know if hiding this type of warnings is ok or there's a reason not to do it. kotlin-warnings-2-no-quiet-javadoc-warnings.txt |
Without quiet mode, Javadoc is very verbose and prints a [WARNING] line for each HTML file it generates. This goes against the initiative of reducing overall warnings as it will generate a new warning for each class introduced. Note that missing Javadoc still generates and prints warnings (check this build), I'm going to pursue another change for that which I will discuss with our not-so-benevolent dictator :D