camel-k
camel-k copied to clipboard
chore(build): let bom managed by camel k runtime
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 https://github.com/apache/camel-k-runtime/pull/827
Release Note
chore(build): let bom managed by camel k runtime
fyi @lburgazzoli @astefanutti @ppalaga @jamesnetherton @oscerd
I think this is failing because we need the changes in https://github.com/apache/camel-k-runtime/pull/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.
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?
Root cause failures are:
org.graalvm.polyglot.PolyglotException: java.lang.IllegalStateException: Duplicate language id regex. First language [Language class com.oracle.truffle.regex.RegexLanguage, Loaded from file:/deployments/dependencies/lib/main/org.graalvm.regex.regex-22.1.0.jar]. Second language [Language class com.oracle.truffle.regex.RegexLanguage, Loaded from file:/deployments/dependencies/lib/main/org.graalvm.regex.regex-22.1.0.jar].
However it seems they are the same of the ones happening in the main branch. I suggest to merge and solve in the main branch.
ok, let's merge.