[ 
https://issues.apache.org/jira/browse/CAMEL-23824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18091198#comment-18091198
 ] 

Claus Ibsen commented on CAMEL-23824:
-------------------------------------

Note: this is more complex than a simple fix because camel-spring-boot has its 
own independent version that can differ from the camel-core version. The 
DependencyList code currently extracts the version from the 
camel-spring-boot-bom entry in dependencyManagement and uses it to fill in 
BOM-managed deps, but the resolution needs to correctly distinguish between:

- camelVersion (core)
- camelSpringBootVersion (may differ)
- springBootVersion (Spring Boot framework itself)

The generated pom.xml has {{CamelSpringBootVersion}} in the BOM entry which may 
not equal the Camel core version. The version resolution in DependencyList.java 
must account for this.

_Claude Code on behalf of Claus Ibsen_

> camel-jbang - dependency list should always include version for Spring Boot 
> and Quarkus runtimes
> ------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-23824
>                 URL: https://issues.apache.org/jira/browse/CAMEL-23824
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-jbang
>            Reporter: Claus Ibsen
>            Priority: Minor
>             Fix For: 4.21.0
>
>
> The {{camel dependency list}} command with {{--runtime=spring-boot}} or 
> {{--runtime=quarkus}} omits the artifact version from the GAV output for 
> BOM-managed dependencies (e.g. 
> {{org.apache.camel.springboot:camel-spring-boot-starter}} without version).
> The {{DependencyList}} code already has logic to resolve versions from the 
> BOM entries in the generated pom.xml (lines 184-188), but the version is not 
> showing up in practice.
> Tooling that consumes this command output needs full GAV coordinates 
> (groupId:artifactId:version) to fetch JARs. The version should always be 
> included regardless of runtime, since the BOM version is known at generation 
> time.
> The version resolution logic in {{DependencyList.java}} should be 
> investigated and fixed so that BOM-managed dependency versions are always 
> resolved and included in the output for all runtimes.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to