[
https://issues.apache.org/jira/browse/CAMEL-9722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15199468#comment-15199468
]
ASF GitHub Bot commented on CAMEL-9722:
---------------------------------------
GitHub user tdiesler opened a pull request:
https://github.com/apache/camel/pull/908
[CAMEL-9722] Explicitly define cxf transitive dependencies
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tdiesler/camel CAMEL-9722
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/908.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #908
----
commit 375318d4fad79106b53b503829b4288ff51e8515
Author: Thomas Diesler <[email protected]>
Date: 2016-03-17T13:02:22Z
[CAMEL-9722] Explicitly define cxf transitive dependencies
----
> Explicitly define cxf transitive dependencies
> ---------------------------------------------
>
> Key: CAMEL-9722
> URL: https://issues.apache.org/jira/browse/CAMEL-9722
> Project: Camel
> Issue Type: Task
> Reporter: Thomas Diesler
> Fix For: 2.17.0
>
>
> According to [Importing
> Dependencies|https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Importing_Dependencies],
> it is possible to import the dependency management sections from multiple
> projects. The [wildfly-camel|https://github.com/wildfly-extras/wildfly-camel]
> project does this both with wildfly and camel dependencies.
> Generally we'd like to use the camel defined dependencies, it is however
> often the case that there is a version skew for a give project - cxf for
> example.
> To avoid an incorrect mix of cxf versions, camel should not only define its
> top-level cxf deps but also the transitive dependencies that it expects to be
> using
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
