camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Quinn Stevenson (JIRA)" <>
Subject [jira] [Commented] (CAMEL-8502) Camel BOM for Maven users
Date Tue, 05 Apr 2016 22:26:25 GMT


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

View raw message