[
https://issues.apache.org/jira/browse/CAMEL-11247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16002939#comment-16002939
]
Nicola Ferraro commented on CAMEL-11247:
----------------------------------------
I've just tried with this configuration and it works:
https://github.com/spring-io/initializr/compare/master...nicolaferraro:camel-2.19.1
At least, there are no missing versions. Probably you've not linked the camel
dependency with the bom section, so the BOM was not added...
[~snicoll] we had some issues in the past because of some minor libraries that
were imported transitively by our modules, but were not present in the
spring-boot BOM. Something like: spring-boot had 'jetty-core', but not
'jetty-xy', so that Camel applications on spring-boot ended up having
jetty-core version 9.3 and jetty-xy version 9.2 (and same for other libraries).
But definitely, you're right about the scope of a BOM and I also think it's
sane in this context to provide our own modules only.
[~davsclaus], [~lb], each camel-spring-boot starter uses the
'camel-spring-boot-dependencies' bom, so their transitive dependencies should
be aligned with the spring-boot ones. I think we can create a minimal BOM for
spring-boot that contains only the starters and not the normal components (plus
catalog and other stuff), because normal components would take transitive
dependencies from camel-parent (and some of them are missing in the spring-boot
BOM). Thoughts?
> camel-spring-boot - Improve BOM to work better with start.spring.io
> -------------------------------------------------------------------
>
> Key: CAMEL-11247
> URL: https://issues.apache.org/jira/browse/CAMEL-11247
> Project: Camel
> Issue Type: Improvement
> Components: camel-spring-boot, camel-spring-boot-starters
> Reporter: Claus Ibsen
> Assignee: Nicola Ferraro
> Fix For: 2.20.0
>
>
> See this PR
> https://github.com/spring-io/initializr/pull/425#issuecomment-299801788
> I tried locally to set the initializer to use our current BOM for spring-boot
> starters, but the project it generates causes the mvn to not build.
> We should IMHO try to get this working so we can use a BOM in the
> start.spring.io wizard so people get a nicer project build out of the box.
> Which is also what the Spring guys is asking for.
> You can try the initializer locally, by following instructions at
> https://github.com/spring-io/initializr#running-the-app-locally
> Then you can thinker in the yml file to setup a Camel BOM
> https://github.com/spring-io/initializr/blob/master/initializr-service/src/main/resources/application.yml
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
