What happened?
Looks like the microprofile-config integration is missing the META-INF/beans.xml marker file, which means that the configuration is not getting loaded as an alternative bean in Quarkus applications.
Is this intentional? or was this a miss?
Noticed this issue with 0.3.3 ... and looks like the main branch doesn't have it either.
For now, I am pushing my own bean that simply extends from MicroProfileConfigProvider
Relevant log output
Code of Conduct
What happened?
Looks like the microprofile-config integration is missing the
META-INF/beans.xmlmarker file, which means that the configuration is not getting loaded as an alternative bean in Quarkus applications.Is this intentional? or was this a miss?
Noticed this issue with
0.3.3... and looks like themainbranch doesn't have it either.For now, I am pushing my own bean that simply extends from
MicroProfileConfigProviderRelevant log output
Code of Conduct