nicolaferraro opened a new issue #2170: URL: https://github.com/apache/camel-k/issues/2170
Let's take a hello world integration. There are some commands that theoretically should do the same thing, but they don't: - `kamel run hello.yaml -d camel:jackson`: adds `org.apache.camel:camel-jackson` - `kamel run hello.yaml -d camel-quarkus:jackson`: **error** in the CLI, but works as next one if set manually in the integration - `kamel run hello.yaml -d camel-quarkus-jackson`: adds `org.apache.camel.quarkus:camel-quarkus-jackson` and transitively `org.apache.camel:camel-jackson` I think that we should treat `camel:` and `camel-quarkus:` as synonyms, as there's no reason why one would like to add the camel component without the quarkus extension, given that we only have quarkus as runtime. People can still use `mvn:` if they want to use a specific lib. We can keep both for compatibility, but with the same meaning. This problem is also evident in Kamelets, where we need to use [camel-quarkus:](https://github.com/apache/camel-kamelets/blob/0851143b8feece2000bd2aca93bf36b650043e34/aws-sqs-fifo-sink.kamelet.yaml#L55) and mark the Kamelet as [requiring Quarkus](https://github.com/apache/camel-kamelets/blob/0851143b8feece2000bd2aca93bf36b650043e34/aws-sqs-fifo-sink.kamelet.yaml#L10) just because dependency formats are distinct. cc @astefanutti , @lburgazzoli wdyt? -- 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
