Daniel Widdis

Hey @yeohbraddy it looks like just running `./gradlew javadoc` is pretty fast and does the missing doc check, while we can leave the full validation to the end of the...

Hey @yeohbraddy I'm not sure there is any automated testing as you're actually testing the automation! - you should be able to validate the javadoc check yourself just by checking...

> Yes, the [release nightlies](https://gradle.org/release-nightly/) Updating my wrapper to use a nightly build sounds great, except... This `release-nightly` link currently is showing `6.9.3-20221007060817+0000` as the latest, but my build is...

> Also remember that you do not necessarily need to ... I made a brief attempt to follow your link and understand what you said, but the practical matter is...

Looks like Sonatype and the CI is giving you some stuff to work with, so I'll hold off on further review. But can you rebase onto master and make sure...

How about the contents of `/sys/devices/system/cpu/cpuN/cpufreq/scaling_cur_freq` or `/sys/devices/system/cpu/cpuN/cpufreq/cpuinfo_cur_freq`? (Replace N with core #.) is there a similar `ocpu` entry on the syspath? How about `/proc/cpuinfo`? Looks like there are instructions...

Also `lshw -class processor`

It should have seen the `capacity:` line in the `lshw` command. Of course, that requires elevated permissions.

Actually, the `lshw` is in the max frequency. Bottom line: The javadocs note that this method is an "attempt", and the information is not always available or requires installation of...

Looks like `show platform cpu` just gives the nominal speed of the CPU, same as OSHI's "Vendor frequency".