You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2026/02/10 08:16:00 UTC
[jira] [Resolved] (CAMEL-22969) Camel-jbang: add a parameter to specify QuarkusPlatform version when running/exporting from cmd
[ https://issues.apache.org/jira/browse/CAMEL-22969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-22969.
---------------------------------
Resolution: Information Provided
> Camel-jbang: add a parameter to specify QuarkusPlatform version when running/exporting from cmd
> ------------------------------------------------------------------------------------------------
>
> Key: CAMEL-22969
> URL: https://issues.apache.org/jira/browse/CAMEL-22969
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
> Affects Versions: 4.18.0
> Reporter: Jiri Ondrusek
> Priority: Major
>
> During prototyping of simple AI scenarios with recent camel-jbang cmd tool, I tried to run some of the routes in the quarkus runtime. But when I was using camel-jbang (version 4.17.0) the exported quarkus app contained Quarkus-platform (3.30.6 - which uses Camel 4.16.0).
> This is a consequence of releasing, when Camel is released before Quarkus platform. (so the Quarkus-platform contains usually version of Camel from the previous release)
> Unfortunately some of my apps did not work in Quarkus runtime because of that. The workaround for me - to run such app, was to export the app and to manually change the version of camel-quarkus/quarkus bom in the pom -> then app worked.
> I think that it would be nice and helpful to add a parameter like `quarkus-platform-version` and `camel-quarkus-platform-version` to the `export` and `run` commands (if quarkus runtime is used)
> Then the exported/executed app would use the proper Quarkus/Camel-quarkus and he prototyping would be much easier.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)