[
https://issues.apache.org/jira/browse/CAMEL-11965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16225212#comment-16225212
]
Claus Ibsen commented on CAMEL-11965:
-------------------------------------
Yeah they should be removed - if we did this for all 200 components to include
whatever they may have extra then the parent pom file is too big and
unmaintainable for us also. It has some old cruft today and would be a good
idea to clean it up in camel 3.
There is BOM in camel-bom you can import. Its a minimalistic for camel artifact.
> camel BOM (and camel-hl7) lack the optional dependency to hapi-structures-v251
> ------------------------------------------------------------------------------
>
> Key: CAMEL-11965
> URL: https://issues.apache.org/jira/browse/CAMEL-11965
> Project: Camel
> Issue Type: Task
> Components: build system
> Affects Versions: 2.20.0
> Reporter: Andrea Tarocchi
> Assignee: Andrea Cosentino
> Priority: Minor
>
> Camel BOM and camel-hl7 lack the optional dependency to
> {{hapi-structures-v251}} while }
> {{hapi-structures-v25}} and {{hapi-structures-v24}} are present.
> So if a maven project use dependency management like:
> {code:XML}
> <dependencyManagement>
> <dependencies>
> <dependency>
> <groupId>org.apache.camel</groupId>
> <artifactId>camel-parent</artifactId>
> <version>${camel.version}</version>
> <type>pom</type>
> <scope>import</scope>
> </dependency>
> </dependencies>
> </dependencyManagement>
> {code}
> is not able to do:
> {code:java}
> <dependency>
> <groupId>ca.uhn.hapi</groupId>
> <artifactId>hapi-structures-v251</artifactId>
> </dependency>
> {code}
> but need to specify the right version defeating the purpose of using a BOM.
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
