Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
OSMBean.getFreePhysicalMemorySize supression option #16039
Ideally the code gets updated. I think the best approach would be to expand the OSMBeanSupport class so that all methods of the dynamically determined OSMBean are exposed directly. And reflection is done behind this class.
But that is going to be a large and risky change; main goal of this PR is to apply fix this on 4.0 and then to backport it to 3.12 and 3.11. And I want to do that with the least amount of change (lowest risk)