[jira] [Comment Edited] (CAMEL-15428) Create a proper camel BOM

["Stephane Nicoll (Jira)" <ji...@apache.org>]

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

Stephane Nicoll edited comment on CAMEL-15428 at 8/19/20, 3:26 PM:
-------------------------------------------------------------------

{{camel-spring-boot-dependencies}} is the problem. It not only provides dependency management for Camel but also for a bunch of 3rd party libraries. 

If two boms provide dependency management for the same thing, you get a warning in Maven. Spring Boot does this because it relates to "platform dependency management" rather than providing a bom for Spring Boot artitacts. I don't have an opinion if Camel is considered as a development platform but I think it would be worthwhile to have bom in the strict sense of the term.

I would welcome a {{camel-spring-boot-bom}} on start.spring.io that only defines Camel artifacts actually.


was (Author: snicoll):
{{camel-spring-boot-dependencies}} is the problem. It not only provides dependency management for Camel but also for a bunch of 3rd party libraries. 

If two boms provide dependency management for the same thing, you get a warning in Maven. Spring Boot does this because this is relates to "platform dependency management" rather than providing a bom for Spring Boot artitacts.

I would welcome a {{camel-spring-boot-bom}} on start.spring.io that only defines Camel artifacts actually.

> 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)