[
https://issues.apache.org/jira/browse/CAMEL-22726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18040687#comment-18040687
]
Claus Ibsen commented on CAMEL-22726:
-------------------------------------
Kamelets are no longer hardcoded in jbang from Camel 4.17 onwards. Instead its
downloaded on demand and you can refer to a specific version via
--kamelet-version (like --camel-version)
[https://camel.apache.org/manual/camel-4x-upgrade-guide-4_17.html]
However when exporting and kamelets are in use, and no specific version has
been given via --kamelets-version then the pom.xml for CEQ can leave the
version blank if its somehow managed by CEQ. However I would think this is odd
as Kamelets are released indendept and they are essentially just a set of .yaml
files and not binary compiled to a specific version.
In the future I think its actually better for kamelets to be moved over to core
project and released together - that makes everything much easier. And also
makes kamelets more first-class. But this is a different discussion and we have
soo much on our plate already.
> Rely on version defined in Camel Quarkus bom for camel-kamelet dependency
> when exporting project with Camel JBang
> -----------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-22726
> URL: https://issues.apache.org/jira/browse/CAMEL-22726
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
> Affects Versions: 4.16.0
> Reporter: Aurélien Pupier
> Priority: Minor
>
> Currently, the camel-kamelet version is set directly in the pom.xml of the
> exported project to Camel Quarkus. This is not needed anymore as this version
> is now managed by the camel quarkus bom.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
