Warning about Run time configuration when using quarkus-reactive-db2-client #49292
Description
Describe the bug
Note: This issue is more for tracking + it should be fixed before LTS in my POV.
The fix seems be part of the #48973 and it's planned for 3.28.
Expected behavior
Using the quarkus-reactive-db2-client in my project, I would not expect warning that Run time configuration should not be consumed in Build Steps.
Actual behavior
When starting Quarkus:
2025-07-30 21:02:07,054 WARN [io.qua.deployment] (main) Run time configuration should not be consumed in Build Steps, use RuntimeValue<io.quarkus.datasource.runtime.DataSourcesRuntimeConfig>
in a @Recorder constructor instead at io.quarkus.datasource.runtime.DataSourcesRuntimeConfig dataSourcesRuntimeConfig of io.quarkus.deployment.builditem.ServiceStartBuildItem
io.quarkus.reactive.db2.client.deployment.ReactiveDB2ClientProcessor.build(io.quarkus.deployment.annotations.BuildProducer,io.quarkus.deployment.annotations.BuildProducer,io.quarkus.deployment.annotations.BuildProducer,io.quarkus.reactive.db2.client.runtime.DB2PoolRecorder,io.quarkus.vertx.deployment.VertxBuildItem,io.quarkus.vertx.core.deployment.EventLoopCountBuildItem,io.quarkus.deployment.builditem.ShutdownContextBuildItem,io.quarkus.deployment.annotations.BuildProducer,io.quarkus.deployment.annotations.BuildProducer,io.quarkus.datasource.runtime.DataSourcesBuildTimeConfig,io.quarkus.datasource.runtime.DataSourcesRuntimeConfig,io.quarkus.reactive.datasource.runtime.DataSourcesReactiveBuildTimeConfig,io.quarkus.reactive.datasource.runtime.DataSourcesReactiveRuntimeConfig,io.quarkus.reactive.db2.client.runtime.DataSourcesReactiveDB2Config,java.util.List,io.quarkus.deployment.pkg.builditem.CurateOutcomeBuildItem)
of class io.quarkus.reactive.db2.client.deployment.ReactiveDB2ClientProcessor
How to Reproduce?
No response
Output of uname -a or ver
No response
Output of java -version
No response
Quarkus version or git rev
main, 3.25.0
Build tool (ie. output of mvnw --version or gradlew --version)
No response
Additional information
No response