[
https://issues.apache.org/jira/browse/CAMEL-23353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18076547#comment-18076547
]
Jiri Ondrusek commented on CAMEL-23353:
---------------------------------------
Hi [~davsclaus] I'm sorry for my previous PR, I missed the more obvious way of
achieving the same.
Here is the [PR|https://github.com/apache/camel/pull/22784] with the changes
you suggested. + I added a test into MavenDownloaderImplTest to cover scenario
with the repository from the system property.
> camel-jbang: Support configurable default Maven repositories and dynamic
> Quarkus platform version resolution from registry
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-23353
> URL: https://issues.apache.org/jira/browse/CAMEL-23353
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
> Reporter: Jiri Ondrusek
> Assignee: Jiri Ondrusek
> Priority: Major
> Fix For: 4.18.2, 4.21.0
>
>
> When using custom Camel distributions, two issues exist:
>
> 1. {*}Maven Repository Configuration{*}: Additional Maven repositories must
> be manually passed via --repos on every command. Lower-level Maven
> resolution in MavenDownloaderImpl doesn't respect higher-level repository
> configuration mechanisms, requiring repetitive manual configuration.
> 2. {*}Static Quarkus Platform Versions{*}: The export --runtime quarkus and
> run --runtime quarkus commands use build-time constant versions instead of
> querying the Quarkus platform registry. Only version list queries the
> registry. This means newer compatible platform versions available in the
> registry are not automatically used.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
