[backport camel-4.18.x] CAMEL-23828: Honor explicit --quarkus-version during export

[JiriOndrusek]

fixes https://issues.apache.org/jira/browse/CAMEL-23828

When the user specifies --quarkus-version on the CLI, via application.properties, or via system property, the export command should use that exact version instead of resolving from the Quarkus Extension Registry. Previously the registry resolution was unconditional and would overwrite the user's version with the latest patch for that stream.

The fix removes the default value from the --quarkus-version option so the field starts as null. ExportQuarkus now only applies the build-time default and registry resolution when no explicit version was provided.

Description

Target

• I checked that the commit is targeting the correct branch (Camel 4 uses the main branch)

Tracking

• If this is a large change, bug fix, or code improvement, I checked there is a JIRA issue filed for the change (usually before you start working on it).

Apache Camel coding standards and style

• I checked that each commit in the pull request has a meaningful subject line and body.

• I have run mvn clean install -DskipTests locally from root folder and I have committed all auto-generated changes.

[davsclaus]

How does this work on the main branch? We cannot make special code on 4.18.x if its not similar/same as the main branch

[JiriOndrusek]

How does this work on the main branch? We cannot make special code on 4.18.x if its not similar/same as the main branch

In upstream, there was a big change https://issues.apache.org/jira/browse/CAMEL-23560 and part of it is QuarkusPlatformMixin, which provides the same functionality

camel/dsl/camel-jbang/camel-jbang-core/src/main/java/org/apache/camel/dsl/jbang/core/commands/QuarkusPlatformMixin.java

Line 70 in 8cb42d2

if (quarkusVersion != null) {

(I mentioned the upstream fix in the ticket for 4.18.x, but I should mention it in the PR as well)

[davsclaus]

Ah okay, then this is fine