ugh, hit reply instead of reply-all first time and also made a lame
misunderstanding regarding ehcache versions :-/ Anyway, just've committed
the update to ehcache 2.8.3; I'll file a JIRA for this so it can be tracked
when generating the next release notes..

br,
juan pablo


On Tue, Jul 8, 2014 at 12:00 AM, Ichiro Furusato <ichiro.furus...@gmail.com>
wrote:

> Hi Juan Pablo,
>
> If you look in the repositories for the ehcore-core.jar you'll find the
> latest is indeed 2.6.9, but
> that's only because that version is the end of the line for that jar, not
> the EHCache project.
> Newer distributions of the EHCache project will no longer release an
> ehcache-core.jar, only
> a consolidated one.
>
> The API and the bundling of the jars has also changed from 2.6.x to 2.8.x,
> in that you won't
> find removeAllCaches() in the 2.6.x trunk, but by 2.8.x this was the
> replacement for removeAll(),
> which was then deprecated.
>
> At some point I believe we'll want to move to 2.8.x since that's about a
> year newer.
>
> Cheers,
>
> Ichiro
>
>
>
> On Tue, Jul 8, 2014 at 6:16 AM, Juan Pablo Santos Rodríguez <
> juanpablo.san...@gmail.com> wrote:
>
>> Hi Ichiro,
>>
>> AIUI, ehcache is the full framework ([#1] listing all modules), whereas
>> ehcache-core is just the module we're using. It was last updated on april
>> this year (2.6.9), so I've updated to it, and while at it, also performed
>> some other easy dependencies upgrades. And yes, it was about 10-minutes
>> work :-D
>>
>> Regarding CacheManager.getInstance().removeAllCaches(), didn't find it
>> :-?, so ended up using CacheManager.getInstance().removalAll() instead,
>> which should be ok. Did found a couple of
>> CacheManager.getInstance().clearAll() on unit tests though, and changed
>> them to use removalAll(), as CacheManager.getInstance().clearAll() isn't
>> thread safe. Also, I recall reading on ML not so long ago somebody
>> reporting some intermitent test failures, so maybe this helps a little bit
>> with them..
>>
>>
>> br,
>> juan pablo
>>
>> [#1]:
>> https://oss.sonatype.org/content/repositories/sourceforge-releases/net/sf/ehcache/
>>
>>
>> On Fri, Jul 4, 2014 at 1:47 PM, Ichiro Furusato <
>> ichiro.furus...@gmail.com> wrote:
>>
>>> Hi Juan Pablo,
>>>
>>> The upgrade to EHCache seems pretty painless. The current trunk is on
>>> version
>>> 2.6.6,from May 2013. So it's not terribly old but my understanding is a)
>>> the API
>>> has changed a bit, and b) EHCache is no longer distributed as an
>>> ehcache-core
>>> module in contemporary versions.
>>>
>>> This may not be a high priority so feel free to ignore this message...
>>>
>>> I've updated my local version (JSPWiki 2.10.2-SNAPSHOT) to the latest
>>> version
>>> 2.8.3 by modifying the two POMs as shown below. All tests pass and I've
>>> seen
>>> no difference in my own tests.
>>>
>>> In ./pom.xml:
>>>
>>>       <dependency>
>>>         <groupId>net.sf.ehcache</groupId>
>>>         <artifactId>ehcache</artifactId>
>>>         <version>2.8.3</version>
>>>       </dependency>
>>>
>>> In ./jspwiki-war/pom.xml:
>>>
>>>     <dependency>
>>>       <groupId>net.sf.ehcache</groupId>
>>>       <artifactId>ehcache</artifactId>
>>>     </dependency>
>>>
>>> We ran across this when upgrading EHCache for a different application and
>>> found some API differences that required an upgrade, so I thought to see
>>> about
>>> JSPWiki at the same time.
>>>
>>> Note that any use of
>>>
>>>     CacheManager.getInstance().removeAll();
>>>
>>> has been deprecated, replaced with:
>>>
>>>     CacheManager.getInstance().removeAllCaches();
>>>
>>> All told, about 10 minutes work (not counting this email)...
>>>
>>> Cheers,
>>>
>>> Ichiro
>>>
>>
>>
>

Reply via email to