lburgazzoli commented on issue #592: URL: https://github.com/apache/camel-k-runtime/issues/592#issuecomment-767400153
> > I think we have two options here: > > > > 1. since `camel-k-master` and `camel-k-cron` have transitive dependencies on the related camel-quarkus components, we can ignore the camel-quarkus ones when when the catalog is computed (so camel-k-runtime ones have higher priority) > > 2. do not add schemes to camel-k-runtime artefact as they are used to provide capabilities > > > > @nicolaferraro @astefanutti what do you think ? > > I'm not sure they have transitive dependencies, actually iirc the CI was failing when the runtime version of the artifacts was chosen. > > Yeah, `camel-k-cron` does not seem to depend on `camel-quarkus-cron`. That is likely to be a leftover of the migration to quarkus as the runtime, it needs to be fixed in any case ---------------------------------------------------------------- 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
