• Bug
  • Status: Closed
  • 2 Major
  • Resolution: Fixed
  • hsingh
  • Reporter: hhuynh
  • May 28, 2010
  • 0
  • Watchers: 1
  • January 17, 2013
  • June 23, 2010


We’re still using tim-ehcache-2.0 to run with ehcache-core-2.1.0

That doesn’t look right version and convention wise


Fiona OShea 2010-06-01

Is something messed up here?

Geert Bevin 2010-06-03

No, it’s not messed up, this is simply the name of the tim artifact. There’s no different for the implementation between the Ehcache TC support for 2.0 and 2.1. If we start tracking the exact version number of ehcache in the tim artifact name, then we constantly need to create new versions and releases also.

Tim Eck 2010-06-03

we’ve never really had a good answer to this issue. I agree that using tim-ehcache-2.0 with ehcache-core-2.1.x is confusing (even if it works fine).

This issue should probably be raised a little higher to have someone tell us what to do. If nothing else we can create tim-ehcache-2.1 which is empty and just depends on tim-ehcache-2.0. We do that in other places.

Geert Bevin 2010-06-04

Maybe we should renamed tim-ehcache-2.0 into tim-ehcache-2.x and create a new one in case a later 2.y becomes incompatible?

Tim Eck 2010-06-04

give this to Steve and PM :-)

Geert Bevin 2010-06-07

Need input on what to do next

Fiona OShea 2010-06-08

“Geert , please do your suggestion from 6/4 thanks

Himadri Singh 2010-06-24

Verified in rev 23847

now we have tim-ehcache-2.x for ehcache-2.x