Hi

I started the migration from spring boot 1 to 2 in a new branch
boot2ga as the older branch boot2 was out of date. Then I have copied
over the good parts and got the project to build and the
camel-spring-boot is now using SB2.

To support both Spring Boot 1.x and 2.x at the same time is too
complex, and therefore we are migrating to SB2 and dropping SB1
support in the upcoming Camel 2.22.0 release.


The branch is at (will push in a little while):

https://github.com/apache/camel/tree/boot2ga


Outstanding work
=============


1)
There were some newer unit tests and a few minor new changes to some
of the actuator stuff that was done on master branch that was not
migrated to the older boot2 branch. So we need to check upon this and
then add those again. Its not as easy as the actuator api has changed
alot from SB1 to SB2.

2)
Migrate the itests/camel-itest-spring-boot from SB1 to SB2. I think we
had to do some changes here as well. Those has not yet been migrated.

3)
Jackson was upgraded from 2.8 to 2.9 as SB2 uses this newer version.
This may affect the camel-swagger component.

4)
Look at upgrading other dependencies that SB2 supports/uses. For
example metrics. And there is also the camel-lucene / camel-solr
components that can be upgraded to newer versions.

5)
Run all of the unit tests.

6)
Check the examples that uses spring-boot and check that they work and
if there is something to update/modify.

7)
Update to Karaf 4.2.0 when its GA as we have upgraded to Spring
Framework 5 by default now.

8)
Look at the camel-archetype-spring-boot if it need migration as well.

9)
Migrate the application.properties / yaml to the new SB2 naming. They
changed the prefix and some keys to new names. We need to do this in
our examples / camel-spring-boot unit tests etc. See the SB2 migration
guide: 
https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-2.0-Migration-Guide

10)
Maybe there is some new feature etc in SB2 we can leverage. I noticed
there is some InfoContributor you can do in actuator to provide some
info details. Maybe we can do a CamelContextInfoContributor that can
give you the camel version etc.






-- 
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Reply via email to