[
https://issues.apache.org/jira/browse/CAMEL-27343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on CAMEL-27343 started by Claus Ibsen.
-------------------------------------------
> camel-jbang - move the CVE audit (OSV.dev client, Camel advisories) to a
> small tooling module for reuse by a Maven plugin
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-27343
> URL: https://issues.apache.org/jira/browse/CAMEL-27343
> Project: Camel
> Issue Type: Task
> Components: camel-jbang, tooling
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Major
> Fix For: 4.24.0
>
>
> The CVE scan code ({{OsvClient}}, {{CveAudit}}, {{CveScan}}, {{CveFinding}},
> {{CvssScore}}, {{DependencyChains}}, ...) lives in camel-jbang-core
> ({{org.apache.camel.dsl.jbang.core.common.cve}}) and uses
> {{SecurityAdvisoryHelper}} and {{XmlHelper}} of camel-jbang-run.
> To reuse it from a Maven plugin goal (separate JIRA) without pulling in
> camel-jbang-core, move it to a small module under {{tooling/}} whose
> dependencies are only camel-catalog, camel-util-json and maven-artifact
> ({{ComparableVersion}}). camel-jbang-core, the TUI plugin and
> camel-maven-plugin then use it.
> * Keep the CLI and TUI behaviour unchanged (golden tests and the existing CVE
> tests move with the code).
> * The proxy helper (separate JIRA) and the offline OSV database (separate
> JIRA) go in this module too.
> * No change for users: internal refactoring.
> _Claude Code on behalf of Claus Ibsen (davsclaus)_
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)