[
https://issues.apache.org/jira/browse/CAMEL-9379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15033279#comment-15033279
]
Ioannis Canellos edited comment on CAMEL-9379 at 12/1/15 7:51 AM:
------------------------------------------------------------------
In general its a good idea to separate the parent pom from the bom. The one is
for internal use while the other is something that is meant to be handed over
to the user.
What we hand to the user doesn't need to contain transitives, but just the
camel artifacts.
Of course there are cases, where we want to somehow impose specific versions
for some of the transitives like tooling etc, to protect the user from running
into weird dependency conflicts. To satisfy this need it makes sense to provide
a secondary "bom with tooling".
I've seen this approach followed by projects like arquillian and it worked
really nice.
was (Author: iocanel):
In general its a good idea to separate the parent pom from the bom. The one is
for internal use while the other is something that is meant to be handed over
to the user.
What we hand to the user doesn't need to contain transitives, but just the
camel artifacts.
Of course there are cases, where we want to somehow impose specific versions
for some of the transitives like tooling etc, to protect the user from running
into weird dependency conflicts. To satisfy this need it makes sense to provide
a secondary "bom with tooling".
I've seen this approach followed by projects like arquilian and it worked
really nice.
> Camel BOM should not include tooling depdencies
> -----------------------------------------------
>
> Key: CAMEL-9379
> URL: https://issues.apache.org/jira/browse/CAMEL-9379
> Project: Camel
> Issue Type: Improvement
> Components: build system, tooling
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.17.0
>
>
> We have some tooling dependencies in the parent bom that causes pain for
> Camel end users that import the bom, and cause these depencies to influence
> them.
> We should move them to the tooling pom.xml so the Camel tooling dependencies
> are listed there, and thus separated from the parent bom.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
