[ 
https://issues.apache.org/jira/browse/CAMEL-15428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17180614#comment-17180614
 ] 

Marcin Grzejszczak commented on CAMEL-15428:
--------------------------------------------

Maybe I wasn't too clear. I am the maintainer of Spring Cloud Contract and I 
know how BOMs work :) The problem is that when I add the camel `dependencies` 
pom, it's breaking my dependencies. What I would like to have is just a 
definition of camel based projects. 
[https://mvnrepository.com/artifact/org.apache.camel.springboot/camel-spring-boot-dependencies/3.4.3]
 - you're enforcing versions of projects (e.g. com.fasterxml.jackson.dataformat 
» jackson-dataformat-yaml 2.10.4)

or

{{<dependency>}}
{{<groupId>httpunit</groupId>}}
{{<artifactId>httpunit</artifactId>}}
{{<version>1.7</version>}}
{{</dependency>}}
{{<dependency>}}
{{<groupId>io.apicurio</groupId>}}
{{<artifactId>apicurio-data-models</artifactId>}}
{{<version>1.0.16.Final</version>}}
{{</dependency>}}
{{<dependency>}}
{{<groupId>io.krakens</groupId>}}
{{<artifactId>java-grok</artifactId>}}
{{<version>0.1.9</version>}}
{{</dependency>}}
{{<dependency>}}
{{<groupId>io.methvin</groupId>}}
{{<artifactId>directory-watcher</artifactId>}}
{{<version>0.9.10</version>}}
{{</dependency>}}

>From my perspective I don't care about these versions nor do I want to 
>override my versions. What I want to have is the whole management section of 
>Camel specific projects. That's why I'd prefer to have a BOM and 
>`-dependencies` that reference the BOM.

 

> Create a proper camel BOM
> -------------------------
>
>                 Key: CAMEL-15428
>                 URL: https://issues.apache.org/jira/browse/CAMEL-15428
>             Project: Camel
>          Issue Type: New Feature
>            Reporter: Marcin Grzejszczak
>            Priority: Major
>
> Hi!
>  
> In Spring Cloud Contract I wanted to reference camel project versions without 
> providing versions for each of them. So I referenced the `camel-dependencies` 
> project in the dependencies management section.
> The problem is that also includes all the non project related library 
> versions (e.g. had a conflict with jackson-databind, Camel downgraded my 
> library).
> It would be great to have a `camel-bom` module that would include only camel 
> related projects without any other dependencies. Then `camel-dependencies` 
> would import `camel-bom` and all the necessary dependencies.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to