[
https://issues.apache.org/jira/browse/CAMEL-25270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Federico Mariani updated CAMEL-25270:
-------------------------------------
Description:
Camel JBang accepts Camel dependency shorthand such as {{--dep=camel:foo}} and
{{\--dep=camel-foo}}. The command-line dependency downloader currently resolves
these at the running Camel version, while automatic component loading uses the
coordinates in the Camel catalog. This can make the two paths request different
versions of the same artifact.
Expected behavior:
* When a Camel shorthand artifact has a catalog model, use that model's group
ID, artifact ID, and version.
* When the artifact is absent from the catalog, retain the running Camel
version as the fallback.
* Preserve the version in an explicit Maven coordinate.
* Use the resolved coordinates consistently for the classpath check and
download.
Add a focused regression test for cataloged components and other artifacts, an
uncataloged artifact, and an explicit Maven coordinate. Document the shorthand
resolution rule.
was:
Camel JBang accepts Camel dependency shorthand such as {{--dep=camel:foo}} and
{{--dep=camel-foo}}. The command-line dependency downloader currently resolves
these at the running Camel version, while automatic component loading uses the
coordinates in the Camel catalog. This can make the two paths request different
versions of the same artifact.
Expected behavior:
* When a Camel shorthand artifact has a catalog model, use that model's group
ID, artifact ID, and version.
* When the artifact is absent from the catalog, retain the running Camel
version as the fallback.
* Preserve the version in an explicit Maven coordinate.
* Use the resolved coordinates consistently for the classpath check and
download.
Add a focused regression test for cataloged components and other artifacts, an
uncataloged artifact, and an explicit Maven coordinate. Document the shorthand
resolution rule.
> camel-jbang - Resolve Camel shorthand dependencies using catalog coordinates
> ----------------------------------------------------------------------------
>
> Key: CAMEL-25270
> URL: https://issues.apache.org/jira/browse/CAMEL-25270
> Project: Camel
> Issue Type: Improvement
> Reporter: Federico Mariani
> Assignee: Federico Mariani
> Priority: Major
>
> Camel JBang accepts Camel dependency shorthand such as {{--dep=camel:foo}}
> and {{\--dep=camel-foo}}. The command-line dependency downloader currently
> resolves these at the running Camel version, while automatic component
> loading uses the coordinates in the Camel catalog. This can make the two
> paths request different versions of the same artifact.
> Expected behavior:
> * When a Camel shorthand artifact has a catalog model, use that model's group
> ID, artifact ID, and version.
> * When the artifact is absent from the catalog, retain the running Camel
> version as the fallback.
> * Preserve the version in an explicit Maven coordinate.
> * Use the resolved coordinates consistently for the classpath check and
> download.
> Add a focused regression test for cataloged components and other artifacts,
> an uncataloged artifact, and an explicit Maven coordinate. Document the
> shorthand resolution rule.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
