ppalaga opened a new issue #2225: URL: https://github.com/apache/camel-quarkus/issues/2225
Our `ContainerResourceLifecycleManager` implementations often reference container versions. We have no process/tool in place that would ensure that the versions stay up to date, esp. that the version of the given container is close enough to the version of the respective library. One possible solution that comes to my mind is to maintain the versions in the top pom.xml either using the same property as the respective library or using a separate property, but placing it along with the lib version prop, so that any discrepancy gets noticed when the lib is upgraded. Any other ideas? ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
