Did some more work ( still attached to https://issues.apache.org/jira/browse/JCS-118 - side note: i didnt recheck defaults tests here so maybe seomthing is broken regarding the configuration I changed a bit as mentionned in a comment )
The question at this point is how to go ahead? My main issue is while we don't have a fully working patch how can we share changes. Not sure patches are the best solution. [sandbox] could be since we are more to have perms. wdyt? Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2014-04-22 9:41 GMT+02:00 Jean-Louis MONTEIRO <jeano...@gmail.com>: > +1, that'd be awesome. > I don't think it's a big word/rework. Crossing fingers, it's just a matter > of some interfaces and an SPI to implement. > > JLouis > > > 2014-04-21 20:39 GMT+02:00 Thomas Vandahl <t...@apache.org>: > >> On 21.04.14 19:06, Romain Manni-Bucau wrote: >> > saw it, I can rephrase the question this way: will tomee be able to >> > rely on jcs or should we directly use ehcache as do cxf already for >> > other needs. >> > >> > I'd like to see an apache product in the box but not sure we'll find >> > enough time to make it real short term >> > >> >> Me too. I think it should be not too hard and the 2.0 release is >> certainly a good milestone to work on this. At the moment, however, I >> maintain this project pretty much alone and I have no idea what JCache >> means and how it is related to the current architecture of JCS. >> I'm willing to help as much as I can. >> >> Bye, Thomas. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org >> >> > > > -- > Jean-Louis --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
