We may add a note also in the on the camel documentation in the github repo about this.
-- Andrea Cosentino ---------------------------------- Apache Camel PMC Chair Apache Karaf Committer Apache Servicemix PMC Member Email: [email protected] Twitter: @oscerd2 Github: oscerd On Monday, December 3, 2018, 3:49:17 PM GMT+1, Jean-Baptiste Onofré <[email protected]> wrote: OK, I found the issue, it's related to property placeholder: https://issues.apache.org/jira/browse/CAMEL-12570 So, it affects users when using property placeholder in the camel blueprint route. To work, users have to use at least Camel 2.21.2. If an user still uses Camel 2.20.1, it won't work. That's why I think it's better to: 1. stay with blueprint-core 1.9.x on Karaf 4.2.x 2. do a a new blueprint-core 1.9.1 release including the interceptor fix we need for jpa Thoughts ? Regards JB On 03/12/2018 15:43, Jean-Baptiste Onofré wrote: > I just tested camel-blueprint 2.20.1 with blueprint-core 1.10.0 and it > seems to work: I deployed a simple camel route written using blueprint > and it starts and works fine. > > Does someone remember the issue we had with the blueprint-core upgrade > with camel-blueprint ? Maybe it was with previous Camel version. > > Regards > JB > > On 03/12/2018 15:26, Jean-Baptiste Onofré wrote: >> Hi guys, >> >> A pull request has been merged on master (so for Karaf 4.2.2), but I >> think it's not correct: >> >> https://github.com/apache/karaf/commit/62e832c7009b5b8beafd219ff7b6b66051205682 >> >> This is an upgrade to blueprint-core 1.10.0. We already have a Jira >> about that: >> >> https://issues.apache.org/jira/browse/KARAF-5942 >> >> We can't update to blueprint 1.10.0 on Karaf 4.2.x without breaking the >> Camel Blueprint support, which I think it's really bad. >> >> So, I think it would be better to revert this update and target >> blueprint 1.10.0 to Karaf 4.3.x. >> >> Thoughts ? >> >> Regards >> JB >> > -- Jean-Baptiste Onofré [email protected] http://blog.nanthrax.net Talend - http://www.talend.com
