You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2017/10/12 09:23:00 UTC

[jira] [Resolved] (CAMEL-8502) Camel BOM for Maven users

     [ https://issues.apache.org/jira/browse/CAMEL-8502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-8502.
--------------------------------
       Resolution: Fixed
         Assignee: Nicola Ferraro
    Fix Version/s:     (was: Future)
                   2.20.0

There is a camel-bom artifact now, that lists just all the camel artifacts.

> 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
>            Assignee: Nicola Ferraro
>             Fix For: 2.20.0
>
>
> 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.4.14#64029)