This issue is a reminder to discuss the usage of the ConfigururationContextBuilder.
While analyzing our service providers I recognized that the DefaultConfigurationContextBuilder is not treated like a service provider. Instead of accessing it via the usual SPI meachnism simply a new instance is created. Furthermore DefaultConfigurationContextBuilder is the only implementation of ConfigurationContextBuilder.
We should discuss:
- could be there more than one implementation of ConfigurationContextBuilder?
- If no, can we remove the ConfigurationContextBuilder interface from our API?