Yeah, the dependencies are converted in the plain related camel catalog
ones. Then, the runtime will take care to transform them into the ones of
the related runtime, Camel Quarkus in this case. If you have a look at the
deployed application, you can see that the pom has the camel-quarkus
related
Ok, but about the modeline
//camel-k: dependency=camel-quarkus-microprofile-metrics
Why it is transformed to the dependency:
- camel:microprofile-metrics
?
On Fri, Dec 17, 2021 at 12:24 PM Pasquale Congiusti
wrote:
>
> Hi Roberto,
> I think the modeline is meant for CLI only as a way to parse
Hi Roberto,
I think the modeline is meant for CLI only as a way to parse most of the
kamel run options and provide them for you. As stated in the example doc
[1];
$ kamel run Hello.java
Modeline options have been loaded from source files
Full command: kamel run Hello.java --dependency
The YAML below is a snippet of my Integration resource in k8s, got by:
kubectl get integration -o yaml
apiVersion: camel.apache.org/v1
kind: Integration
metadata:
creationTimestamp: "2021-12-15T11:22:48Z"
generation: 1
name: micro-profile-metrics2
namespace: default
resourceVersion:
