Reverting behavior change from 2.8.0
We discovered that too many consumers depend on the old behavior of avoiding throwing exceptions from configuration reading calls. Adapting code paths that put these calls in the middle of critical request-servicing code is too onerous.
This version DOES fix the old bug that caused properties with defaults (from the Property.orElse() method) to fail for this "invalid setting" case. They will now return the default value.
We are also retaining the noisy logging of parsing errors, to assist users with detection and fixing.
Full Changelog: v2.8.1...v2.8.2