[
https://issues.apache.org/jira/browse/CAMEL-8502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15227260#comment-15227260
]
Quinn Stevenson commented on CAMEL-8502:
----------------------------------------
I'm starting on this one, but I'm not quite sure how you want the top-level
POMs split up.
Currently, there is a org.apache.camel/camel POM and a
org.apache.camel/came-parent POM, and configuration is split across the two.
I'm creating an org.apache.camel/camel-bom with all the library dependencies in
it (in dependencyManagement), but that's all.
I'm running into trouble with determining the parent for the BOM. Everything
else uses org.apache.camel/camel, but the BOM can't do that because of the
extra configuration in that project.
It seems the right thing to do is make the org.apache.camel/camel project
simply a placeholder for all the child modules. Does that sound correct?
> Camel BOM for Maven users
> -------------------------
>
> Key: CAMEL-8502
> URL: https://issues.apache.org/jira/browse/CAMEL-8502
> Project: Camel
> Issue Type: New Feature
> Components: build system
> Reporter: Claus Ibsen
> Fix For: Future
>
>
> We should consider introducing a real Maven BOM (bill of material) that Camel
> end users can import and use when working on camel maven projects. Then the
> BOM imports the version dependencies and whatnot that Camel uses.
> Today camel-parent can be sorta used for that, but it was for internal camel
> usage.
> Having a BOM is the proper way.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
