On Jul 3, 2013, at 6:01 PM, Jason Pell <ja...@pellcorp.com> wrote: > Sorry guys i never got back to this one. Would be easier i should think to > fix this for 3.0 and no longer support the old version at all thus no > reflection magic.
Well, I'd LIKE to still be able to run 2.7/2.6 with the newer versions of ehcache if at all possible. But yes, for 3.0, we could just go with the newest as a minimum. Dan > On Jul 4, 2013 7:04 AM, "Daniel Kulp" <dk...@apache.org> wrote: > >> Aki, >> >> This was on my todo list to look at, just never have managed to find the >> time. There is an issue logged about it: >> >> https://issues.apache.org/jira/browse/CXF-4577 >> >> If you have time, feel free to grab it and see what you can find out. >> >> Dan >> >> >> >> >> On Jul 3, 2013, at 4:58 PM, Aki Yoshida <elak...@gmail.com> wrote: >> >>> cxf's trunk and branches (2.7.x, 2.6.x, etc) all use ehcache 2.5.1 and >>> create the karaf feature with the corresponding smx's bundle version. But >>> the version range specified in the package imports is set as >> [2.5.0,3.0.0), >>> so we could use a newer version in runtime. >>> >>> As ehcache 2.5.1 is rather old (from 2012-01) and there are newer >> versions >>> such as 2.6.6 (2013-05) and 2.7.2 (2013-07) which is already an >>> osgi-bundle, I was wondering if we can use a newer version for trunk's >>> build. There are some disappeared classes and other changes, but the >> usage >>> in cxf seem to be compatible with these versions. I tried both 2.6.6 and >>> 2.7.2, and the build itself seems to run without problems. >>> >>> How do you think about upgrading ehcache to ehcache 2.7.2 for trunk so >> that >>> we can test cxf not just against old ehcache 2.5.1? >>> >>> As comparison, camel trunk uses ehcache 2.7.0, while 2.11.x uses 2.5.2. >>> >>> regards, aki >> >> -- >> Daniel Kulp >> dk...@apache.org - http://dankulp.com/blog >> Talend Community Coder - http://coders.talend.com >> >> -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
