ConfigJSR
ConfigJSR copied to clipboard
#55 ConfigProviderResolver lazy initialization
The ConfigProviderResolver
should not initialize on just being imported for a variety of reasons.
The major reasons is makes initialization less predictable and bootstrapping more complicated. Performance is also a reason.
Instead it should be initialized on access just like logging frameworks and many other Java frameworks.