Le 14/03/2025 à 17:04, Jacques Le Roux a écrit :
Hi,
At https://issues.apache.org/jira/browse/OFBIZ-9148
I have recently made an effort to reduce the number of Javadoc remaining
warnings.
Now the 100 *visible* warnings are all of a kind that need manual interventions. Here is the list
<https://issues.apache.org/jira/secure/attachment/13075415/13075415_javadoc-100-warnings.txt>
I think that errors are placed ahead. So we would have no errors.
It seems that unlike Ant and Maven
https://stackoverflow.com/questions/32642447/increase-the-maximum-number-of-javadoc-warnings-when-compiling-with-ant
https://stackoverflow.com/questions/51582609/increase-the-number-of-reported-javadoc-errors-and-warning-when-building-with-ma
Gradle does not handle the |Xmaxwarns Javadoc option:
|https://docs.gradle.org/current/dsl/org.gradle.api.tasks.javadoc.Javadoc.html
It's well explained there
https://stackoverflow.com/questions/76264497/set-xmaxerros-and-xmaxwarns-in-gradle-to-display-all-errorprone-messages
The solution proposed is to no avail/OOTB.plugins.withType<JavaPlugin> /seems
to be Kotlin specific syntax.
It works with /plugins.withType(JavaPlugin)/
But I still get only 100 warning/s :// We have for sure more! Removing one or
more of those ahead you get still 100.
Conclusion: because the remaining warnings need manual interventions, we have
still an unknown number of remaining warnings.
Jacques
Hi,
At OFBIZ-9148 I have attached the javadoc-12168-warnings.txt file that shows
all the Javadoc warnings and count of their types.
It confirms that no errors remains.
It's a lot of tedious work to have this clean one day...
HTH
Jacques
