Hi Gert,
it sounds good to me. It makes sense to override in config.properties in
ServiceMix and remove it later.
+1
Regards
JB
On 04/30/2013 01:55 PM, Gert Vanthienen wrote:
Hi JB,
So this would be to pick up the fix for
https://issues.apache.org/jira/browse/KARAF-2273, right? Personally,
I would prefer cherry-picking the config property into the ServiceMix
codebase and get this release out of the door, I think.
We can always remove that property again once we upgrade to Karaf
2.3.2 in the next release of ServiceMix.
Regards,
Gert Vanthienen
On Tue, Apr 30, 2013 at 1:21 PM, Jean-Baptiste Onofré <[email protected]> wrote:
Hi Gert,
it makes sense. If possible, I would:
- with Karaf 2.3.2
- or override the etc/config.properties to set blueprint.sync=true
Regards
JB
On 04/30/2013 11:51 AM, Gert Vanthienen wrote:
L.S.,
Over the past few weeks, we fixed a major issue for 4.5.1 with
endorsed Java libraries, cfr.
https://issues.apache.org/jira/browse/SMX4-1423
I would like to do another 4.5.x release just to get this fix out:
this seems like pretty core functionality that's broken now.
There's also a new release for CXF available, but unfortunately
there's no matching Camel release yet (cfr.
https://issues.apache.org/jira/browse/KARAF-971) but I guess we can
always do another release once a matching Camel 2.10.x is available.
Wdyt?
Gert Vanthienen
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com
