[
https://issues.apache.org/jira/browse/CAMEL-23828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiří Ondrušek updated CAMEL-23828:
----------------------------------
Environment: (was: This issue is already fixed on main by [PR
#23333|https://github.com/apache/camel/pull/23333], which eliminated the
built-in Quarkus platform version literal in favor of dynamic resolution from
the Quarkus Extension Registry. However, that change is too complex to backport
to camel-4.18.x, so this ticket
tracks a minimal, targeted fix for the camel-4.18.x branch.
When an explicit --quarkus-version is passed to camel export (or set via
application.properties / system property camel.jbang.quarkusVersion), the
specified version is silently overwritten by the Quarkus Extension Registry
resolution.
For example:
{code:java}
camel export --runtime=quarkus --gav=com.foo:acme:1.0-SNAPSHOT
--quarkus-version=3.27.0
--directory=test
{code}
Expected: the exported pom.xml contains
<quarkus.platform.version>3.27.0</quarkus.platform.version>.
Actual: the registry resolves the latest patch for the stream (e.g. 3.33.1.1)
and overwrites the user's value.
Root cause: The --quarkus-version option had a compile-time default (3.33.1.1),
so the field was never null. The registry resolution in ExportQuarkus was
unconditional — it ran regardless of whether the user had explicitly set the
version — and replaced whatever value was present.)
> camel export --quarkus-version is ignored — registry resolution overwrites
> the user-specified version
> -------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-23828
> URL: https://issues.apache.org/jira/browse/CAMEL-23828
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
> Affects Versions: 4.18.2
> Reporter: Jiří Ondrušek
> Assignee: Jiří Ondrušek
> Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
