lsergio commented on issue #5755: URL: https://github.com/apache/camel-k/issues/5755#issuecomment-2276530887
Trying to understand the code, I guess this is related to how [this method ](https://github.com/apache/camel-k/blob/f3748c80826848c567c6fdc4c545aabcc5b1049b/pkg/apis/camel/v1/build_types_support.go#L281) is implemented. BuilderDependencies() will load the dependencies from the builder task in each build. Taking one of my builds as an example, I see the list: ``` dependencies: - camel:quartz - mvn:org.apache.camel.k:camel-k-cron - mvn:org.apache.camel.k:camel-k-runtime - mvn:org.apache.camel.quarkus:camel-quarkus-yaml-dsl ``` These strings do not include the jar version. If two builds use the same Camel components, but with different camel-k-runtimes, HasMachingBuild will work as if the dependencies are the same, but they are not. This might lead to a wrong image reuse. I will try and confirm this and open a separate ticket. -- 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]
