[
https://issues.apache.org/jira/browse/CAMEL-22100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17953397#comment-17953397
]
Claus Ibsen commented on CAMEL-22100:
-------------------------------------
Marco if this is not difficult to backport then you are welcome to send a PR
for 4.10.x branch
> camel-jbang - Transitive dependencies on plugins should use the parent
> artifact to manage versions
> --------------------------------------------------------------------------------------------------
>
> Key: CAMEL-22100
> URL: https://issues.apache.org/jira/browse/CAMEL-22100
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
> Affects Versions: 4.8.7, 4.9.0, 4.10.4, 4.11.0
> Reporter: Marco Carletti
> Assignee: Marco Carletti
> Priority: Major
> Fix For: 4.12.0
>
>
> When a plugin is added and executed, the MavenDependencyDownloader starts to
> resolve the transitive dependencies of the plugin itself, but is uses the
> Maven GAV of the plugin without taking account of the parent.
> Since all the Camel JBang plugin uses
> {code:xml}
> <groupId>org.apache.camel</groupId>
> <artifactId>camel-jbang-parent</artifactId>
> {code}
> as parent Maven module, it should rely on this module to manage the
> dependency versions
> Otherwise the downloaded dependencies are not the same used at runtime
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
