ConfigJSR icon indicating copy to clipboard operation
ConfigJSR copied to clipboard
verified publisher icon eclipse

#55 ConfigProviderResolver lazy initialization

Open agentgt opened this issue 6 years ago • 1 comments

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.

agentgt avatar May 14 '19 16:05 agentgt

Oh the ECA failed because I did the commit using github directly and it must have put the wrong email in.... It is such a trivial change.... I don't have anymore time to waste trying to get the ECA check happy. Sorry.

agentgt avatar May 14 '19 16:05 agentgt