versions

SIGAR uses a versioning scheme: common major.minor[.revision[.build]] The number is incremented when binary compatibility is broken between the .jar and the native minor libraries. This can happen if a new API function is added or a field is added to an existing one. The revision number is incremented for bug fixes or enhancements specific to the .jar or a specific native library. For example, where memory metrics were incorrect on Solaris machines with 8GB of RAM. Such as an issue change does not impact the interaction between and the native library. The number is sigar.jar build generated by the and is unlikely to be the same across all binaries.

Note: this was copied verbatim from the old Sigar documentation pdf and may be inaccurate.