Hi all looking at our API I asked me, if it would not be easier for users having direct access to a *ConfigurationBuilder *instead of the current way of creating a *ConfigurationContextBuilder *and calling another method for creating a *Configuration *based on the created *ConfigurationContext*.
Summarizing I propose: 1. Deprecate *ConfigurationProvider#getConfigurationContextBuilder()* 2. Deprecate *ConfigurationProvider#getConfiguration(ConfigurationContext)* 3. Define *ConfigurationBuilder *basically with similar API as the former ConfigurationContextBuilder, but for building a *Configuration *instance directly. 4. Add *ConfigurationProvider#createConfigurationBuilder()*. 5. Adapt the SPIs as needed. Though not the reason for my request, it would align us with the design used in MP as well... WDYT? J Anatole Sidenote: @Oliver test coverage and mutation testing is awesome. I wrote quite some additional tests for the OSGI part before moving it from the sandbox to the extensions repo ;-) -- *Anatole Tresch* PPMC Member Apache Tamaya JCP Star Spec Lead *Switzerland, Europe Zurich, GMT+1* *maketechsimple.wordpress.com <http://maketechsimple.wordpress.com/> * *Twitter: @atsticks, @tamayaconf* *Speaking at:* [image: JSD_Speaker_2017][image: J-Con 2017 logo][image: JVM Con]
