Open turing85 opened 6 months ago
So I started migrating things. commons
, and the spring
look good (there was not really anything to migrate in common-test
).
The other two modules, however (blueprint
and cdi
) give me trouble. For one, there is an unresolved property fest.assert.version
. For another, camel-cdi
has been removed. Alternatives are camel-spring
and camel-quarkus
. I tried migrating camel-cdi
to camel-quarkus
, with limited success. I think that if we want to go down this route, we'd need to rewrite the tests for camel-quarkus
"in the quarkus way", i.e. with junit5
and @QuarkusTest
.
I'd like to have some opinons and pointers, however, before I start this part of the migration. The progress can be seen in my fork (github.com
).
Camel
4.0.0
has been released on 2023-08-14. As of now, this is the current LTS. The next LTS (4.4.0
) is expected to be released in Jan/Feb 2024.The new release broght some changes. The most notably change is the switch from
javax
tojakarta
. But internal APIs of camel changed as well. The most notable changes are listed in the official migration guide (camel.apache.org
).It is desirable to support Camel in version
4.0.0
.