Hello.
As you say, it's probably not a big problem. But it seems better
executing unit tests with the same or nearest dependency stack,
specially blueprint Camel tests that aim to validate our routes and
their context as well.
Indeed, having a new Spring version with a next Karaf release
Hi
That is not a problem. Camel is just a library so end user can use
different patch versions of JARs.
You can have Karaf team upgrade spring for their next releases.
On Thu, Apr 27, 2023 at 7:37 PM Ephemeris Lappis
wrote:
> Hello.
>
> We're upgrading Camel to 3.20.4. This version of Camel
Hello.
We're upgrading Camel to 3.20.4. This version of Camel seems to depend
on Spring 5.3.27.
As the application should run on Karaf 4.4.3 that provides spring
components with version 5.3.23.
Should we either force our project dependencies to use Spring 5.3.23,
or try to upgrade the Karaf
Hello.
In camel routes that work for a long time, we sometimes have some file
that is moved to the folder that is set on the "moveFailed" folder
parameter, but without any log. As the component seems to move the
file before the exchange is given to the route, our code can't log
anything...
We
Try with latest 3.20.4 release first.
Also using spring-main standalone is not so common.
We mainly use/support/focus on spring boot or quarkus based runtimes.
On Thu, Apr 27, 2023 at 11:03 AM Joël Guelluy
wrote:
> Hello,
>
> I'm in migration of a program Came 2.25 to 3.18.6, and there is
>
The Camel PMC is pleased to announce the release of Apache Camel 3.20.4 (LTS).
Apache Camel is an open source integration framework that empowers you
to quickly and easily integrate various systems consuming or producing
data.
This release is a new patch release with 29 fixes and improvements.
Hello,
I'm in migration of a program Came 2.25 to 3.18.6, and there is
something i can't fix.
It seems like camel-spring-main & addRoutesBuilder can't work
together... (i'm probably missing something...)
springcontext.xml
xmlns="http://camel.apache.org/schema/spring;>
MyMain.java (part)
