Thank you David for the CDI integration proposal! It looks good to me as it moves the dependency from CDI to Injection. By the way, for anyone who was not on the call, the context is that we try to make Config not to depend on CDI so that CDI can use Config. MP Config has a tighter integration with CDI. With that design, there will be circular dependency between Config and CDI if CDI wants to use Config. Also with this design, there will be a migration path from MP Config to Jakarta Config, which is very important to the end users. I think with this approach, most scenarios can be satisfied, so CDI injection can come in a later release if needed.
Joakim,
Jakarta Config has different use cases from MP Config. If some features in MP Config works well to satisfy the use cases of Jakarta Config. It is a great plus to take MP Config based on the experience and feedback. There is no need to reinvent the wheels. However, if the feedback for some MP Config needs to improve, Jakarta Config can rework the design to improve the situation. Hope this helps!
Thanks
Emily