• Bug
  • Status: Closed
  • 1 Critical
  • Resolution: Fixed
  • hhuynh
  • Reporter: gkeim
  • August 07, 2008
  • 0
  • Watchers: 0
  • September 11, 2008
  • August 27, 2008


The SVT needs to be versioned against the Terracotta product it’s meant to work with. GCStats interface changes in 2.7, which is used by SVT.


Fiona OShea 2008-08-11

Setup meeting on how to fix and impact

Hung Huynh 2008-08-11

This project should be set up as a regular Forge project with release cycle matched with TC release like ehcache and everything else. It’s currently not.

Gary Keim 2008-08-11

I setup the project to look like the rest of the forge but I’m sure the Maven release plugin should have been used to create the branches. I’ll leave it to the Maven mavens to get that right. The other important piece is changing the Get-SVT page to support the different versions. And what about when the user installs the wrong version? The console will need to check for the SVT version it expects. What a pain.

Fiona OShea 2008-08-19

Setting up a meeting to discuss what to do in the short term for SVT

Fiona OShea 2008-08-26

wrap SVT and manage as a TIM (tim-svt) Update admin script to look for svt in modules directory add to tim-get script

Update the website page - to have instructions on running tim-get

Issues: windows scripts

Gary Keim 2008-08-27

Removed the need to have the scripts mess with classpath, now just determine the correct tim-svt archive and load it dynamically. Still need a 2.7-specific SVT-Get page.

Fiona OShea 2008-09-03

Now in Forge and available by tim-get