You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2026/06/24 13:04:00 UTC
[jira] [Closed] (CAMEL-23824) camel-jbang - dependency list should always include version for Spring Boot and Quarkus runtimes
[ https://issues.apache.org/jira/browse/CAMEL-23824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen closed CAMEL-23824.
-------------------------------
Resolution: Fixed
Not a bug - version resolution works correctly.
> 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)