internet access, you can just drop that xml in deploy
> >> for provisioning.
> >> As for the version numbering, the third digit(s), counted from left to
> >> right, represent bugfixes and must be binary compatible to the previous
> >> versions.
> >>
> >
I think that 5.3.x unit tests are backward compatible so will not be broken.
On 28/04/2023 12:51, Ephemeris Lappis wrote:
Hello again.
François, I agree : the range [5,6) should allow Camel to use the 5.x
version that is available. But as the current Karaf repository comes
with 5.3.23, Camel ro
s.
-Original Message-
From: Ephemeris Lappis
Sent: Friday, April 28, 2023 9:59 AM
To: u...@karaf.apache.org
Cc: users@camel.apache.org
Subject: Re: Karaf, Camel, and Spring
CAUTION: This email originated from outside of Gaston Schul. Do not click
links or open attachments unless you recogn
gt; -Original Message-
> From: Ephemeris Lappis
> Sent: Friday, April 28, 2023 9:59 AM
> To: u...@karaf.apache.org
> Cc: users@camel.apache.org
> Subject: Re: Karaf, Camel, and Spring
>
> CAUTION: This email originated from outside of Gaston Schul. Do not click
> li
Hello again.
François, I agree : the range [5,6) should allow Camel to use the 5.x
version that is available. But as the current Karaf repository comes
with 5.3.23, Camel routes in unit tests and at runtime do not use the
same Spring versions.
So, can we just ignore it, or do we have to adapt our
Hi,
The Camel features are using a range for the Spring version:
dependency='true'>mvn:org.apache.geronimo.specs/geronimo-jta_1.1_spec/1.1.1
spring
spring-tx
camel-core
mvn:org.apache.camel/camel-core-xml/3.20.4
mvn:org.apache.camel/camel-spring/3.20.4
mvn:org.apache.camel/came
phemeris Lappis
> Sent: Thursday, April 27, 2023 7:37 PM
> To: u...@karaf.apache.org; users@camel.apache.org
> Subject: Karaf, Camel, and Spring
>
> CAUTION: This email originated from outside of Gaston Schul. Do not click
> links or open attachments unless you recognize the sen
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 sho
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 s
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 repo
10 matches
Mail list logo
