pefernan opened a new issue, #1983: URL: https://github.com/apache/incubator-kie-issues/issues/1983
Since the previous upgrade (3.8 -> 3.15) Quarkus started deprecating the use of `@ConfigRoot` for the extensions configuration in favor of smallrye's `@ConfigMapping`. So far it's still supported for backguards compatibility by adding the `<arg>-AlegacyConfigRoot=true</arg>` in the quarkus mvn plugin configuration. After the last upgrade to `3.20` a new warning appeared during startup warning about this. Everything is still working as expected but it would be nice to change the affected configurations to use the new mechanism ``` The following config roots are using the legacy configuration classes infrastructure and should be adjusted to use an interface and @ConfigMapping. See https://quarkus.io/guides/writing-extensions#configuration for more information. Please report this issue to their respective owners. - org.kie.flyway.quarkus.KieFlywayQuarkusRuntimeConfig - org.kie.kogito.index.addon.config.DataIndexBuildConfig - org.kie.kogito.index.addon.config.DataIndexRuntimeConfig - org.kie.kogito.index.addon.config.DataIndexUIClientRuntimeConfig - org.kie.kogito.job.http.recipient.JobHttpRecipientRuntimeConfiguration - org.kie.kogito.job.sink.recipient.JobSinkRecipientRuntimeConfiguration - org.kie.kogito.quarkus.config.KogitoBuildTimeConfig - org.kie.kogito.quarkus.config.KogitoRuntimeConfig - org.kie.kogito.quarkus.workflow.deployment.config.KogitoWorkflowBuildTimeConfig ``` Reference: https://quarkus.io/guides/writing-extensions#configuration -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
