Re: Camel 3.7.0 and Karaf 4.3.0

2020-12-28 Thread Jean-Baptiste Onofre 
Hi Oleg,

Do you have the error ?

For camel-jetty, I think it’s related to the jetty feature (it should be fixed 
with Karaf 4.3.1): jetty feature was removed to use pax-jetty, but Camel still 
reference jetty. For transition purpose, I added a jetty "meta" in coming Karaf 
4.3.1.

For camel-paxlogging, I’m suspecting the import range: camel-paxlogging 
reference paxlogging 1.11.2, with import range like [1,2). Whereas Karaf 4.3.x 
uses pax logging 2.x. So, at least camel-paxlogging should extend the range to 
[1,3) to work. I will create the Jira and do this change.

Regards
JB

> Le 28 déc. 2020 à 16:44, Oleg Cohen  a écrit :
> 
> Greetings,
> 
> Happy Holidays!
> 
> I have a question. I just migrated to Karaf 4.3.0 and Camel 3.7.0. It went 
> well, however, I had to remove two features that I previously had installed:
> 
> camel-jetty
> camel-paxlogging
> 
> There were a number of errors/dependency issues and I simply ended up 
> removing these two. 
> 
> I am wondering what those were for and what, if any, capabilities have I lost.
> 
> Would appreciate any insight!
> 
> Cheers,
> Oleg
> 
> 
> 
> -- 
> Oleg Cohen  |  Principal  |  A S S U R E B R I D G E
> Office: +1 617 564 0737 <>  |  Mobile: +1 617 455 7927 <>  |  Fax: +1 888 409 
> 6995 <>
> Email: oleg.co...@assurebridge.com   |  
> www.assurebridge.com

Camel 3.7.0 and Karaf 4.3.0

2020-12-28 Thread Oleg Cohen 
Greetings,

Happy Holidays!

I have a question. I just migrated to Karaf 4.3.0 and Camel 3.7.0. It went
well, however, I had to remove two features that I previously had installed:

*camel-jetty*
*camel-paxlogging*

There were a number of errors/dependency issues and I simply ended up
removing these two.

I am wondering what those were for and what, if any, capabilities have I
lost.

Would appreciate any insight!

Cheers,
Oleg



-- 
*Oleg Cohen  |  Principal  |  **A S S U R E B R I D G E*
*Office: +1 617 564 0737  |  Mobile: +1 617 455 7927  |  Fax: +1 888 409
6995*
*Email: oleg.co...@assurebridge.com   **|
 www.assurebridge.com *