Peter Palaga created CAMEL-23560:
------------------------------------
Summary: Eliminate the usage of a built time Quarkus Platform
version literal; use dynamic resolution from Quarkus Extension registry
Key: CAMEL-23560
URL: https://issues.apache.org/jira/browse/CAMEL-23560
Project: Camel
Issue Type: Improvement
Reporter: Peter Palaga
Quarkus Platform version literal, set at Camel built time, is currently used
primarily as a default value for various Camel CLI commands, such as camel run
and camel export.
That Quarkus Platform version can never be up to date at Camel built time,
because the proper Quarkus Platform version, in which the given Camel version
gets distributed is only known after Camel Quarkus and Quarkus Platform get
released.
Making Camel dependent of Quarkus Platform creates a dependency cycle.
The problem can be solved by eliminating the runtime Quarkus version literal in
Camel and resolving the compatible Quarkus Platform version at Camel CLI
runtime using Quarkus Extension registry, esp. its
[https://registry.quarkus.io/client/extensions/all] endpoint.
A PR follows.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
