Just to clarify guys, the EHCache stuff is sitting in a separate module, created its own module pom etc.
I have added a separate proposed fix at the same time for making your core cache generic, resolving issue jira 43, this though is separate from the ehcache module. For a temp solution in the ehcache module until issue 43 is resolved i have made a generic package in the ehcache module until such time the core cache becomes generic, and this can be managed/removed separately. Mike On 18 Feb 2012, at 08:39, Raffaele P. Guidi wrote: > ea is that of a separate module- similarly to what mir is > doing with JCS. But having ehcache a very large use base this could really > spread adoption.
