-
Notifications
You must be signed in to change notification settings - Fork 350
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(build): let bom managed by camel k runtime #3317
Conversation
I think this is failing because we need the changes in apache/camel-k-runtime#827 to be available. @oscerd which would be the best strategy to use a new change in the camel k runtime? putting this on hold until the camel k runtime is released? Thanks. |
Yes, for the moment. |
Moving as a draft to avoid any unintentional merge. It will need to be merged during next 1.10 release cycle, as soon as camel k runtime version is officially released as well. |
@squakez can we rebase this and make it ready for review? |
6ec9acf
to
988924e
Compare
Root cause failures are:
However it seems they are the same of the ones happening in the |
ok, let's merge. |
With this PR, we remove the dependency from the platform. We'll let the runtime to manage them accordingly. It will also require some change on Camel K Runtime apache/camel-k-runtime#827
Release Note