[ 
https://issues.apache.org/jira/browse/CAMEL-23353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen resolved CAMEL-23353.
---------------------------------
    Fix Version/s: 4.18.3
                       (was: 4.18.2)
       Resolution: Fixed

> 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.3, 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)

Reply via email to