[
https://issues.apache.org/jira/browse/CAMEL-11247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16008159#comment-16008159
]
Nicola Ferraro commented on CAMEL-11247:
----------------------------------------
Yes, was just kidding. We are used to work with platforms that don't have
strict requirements on the libraries you can mix in (but this is another long
story :D).
I really appreciate your feedback and think that your proposal is valid. I just
wanted to point out that for us, working in the middle between spring-boot and
the end users, is not so easy to provide a fully working framework on top of
spring-boot, since we don't have control on the versions of the spring-boot
parent and the best we can do is trying to make it work with the default
configuration.
Also, reasoning like "if Camel x.y.z doesn't support Jackson z.y.x, then
disable Camel" is not possible. Camel has a core that will be always compatible
with spring-boot (we hope), plus 200+ modules that users can pick and use. We
will not try to put all 200+ camel starters in start.spring.io (although it
would be nice :D), but the rule should be "if module camel-aaa x.y.z is not
compatible with Jackson z.y.x, then disable camel-aaa".
Even if last paragraph was confusing we agree on something. Most of the camel
modules now work without the need to use "camel-spring-boot-dependencies", so
putting just current versions of our stuff in a "camel-bom" (as for
"camel-spring-boot-bom"...) is sufficient in most cases, providing a better
experience in the context of start.spring.io. We can manage the exceptions with
"camel-spring-boot-dependencies" or (better) in the camel starters.
"camel-bom" or "camel-spring-boot-bom", with or without parent... personally, I
care more about usability issues. Obviously you decide what to include into the
"platform".
> 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)
