[
https://issues.apache.org/jira/browse/CAMEL-27351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on CAMEL-27351 started by Claus Ibsen.
-------------------------------------------
> camel-jbang - dependency view shows outdated, overridden and conflicting
> dependencies, and camel dependency outdated
> --------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-27351
> URL: https://issues.apache.org/jira/browse/CAMEL-27351
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Major
> Fix For: 4.24.0
>
>
> The dependency view of camel-jbang (the Maven Dependencies screen) lists the
> declared dependencies with their version and, on demand, the transitive ones
> with the dependency that brings them in. It does not tell whether a
> dependency is old, overrides the version Camel manages, or is loaded twice.
> This ticket makes it the place to look at that, with the same data available
> as a CLI command.
> *Camel JARs move together*
> * The camel-* JARs are one row (or a header): "Camel 4.18.1 (LTS, EOL ...),
> newer: 4.18.3 on this line, 4.24.0 latest", from camel-releases.json of the
> catalog. No "newer" per camel-* JAR, as they cannot be upgraded one by one.
> It links to the upgrade view (CAMEL-27352).
> *Compared with what Camel ships*
> * A CAMEL column: the version the camel-parent POM of the Camel release in
> use pins for that library (for example kafka-version, snakeyaml-version).
> * A status per row: managed (same as Camel), override (the project pins
> another version than Camel's, such as snakeyaml 1.33 against Camel's 2.x in
> the security/cve-audit example of camel-jbang-examples), older / newer (for
> libraries Camel does not manage).
> *Newer versions, on demand*
> * NEWER: the latest patch of the same major.minor line. LATEST: the latest
> release, marked when it is a new major version. Loaded with a key (as
> transitives are), from maven-metadata.xml via
> MavenDownloader.resolveAvailableVersions, cached; nothing is fetched until
> asked.
> *Conflicts*
> * The same artifact loaded in two versions (the example ends up with
> snakeyaml 1.33 and 2.x), and a declared version different from the one
> actually loaded (from the jvm action, which now includes the application
> classpath of camel run).
> *CVEs*
> * A CVE count per row and the version that fixes all of them, from the CVE
> audit (CAMEL-27328 / CAMEL-27340), with a link between the two views.
> *AI*
> * Shift+F8: which dependencies to upgrade and whether it is safe, with the
> override, conflict and CVE rows in the prompt.
> *CLI*
> * camel dependency outdated (or an option of camel dependency list) with the
> same columns, --json, and the CLI exit codes (1 when something is outdated,
> with a --fail-on style option), sharing the code with the screen as camel
> dependency audit does.
> Related: CAMEL-27352, CAMEL-27328, CAMEL-27340.
> _Claude Code on behalf of Claus Ibsen_
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)