Re: GregorianCalendar Problem

Hi Chris,

>> AFAIK this is a known classpath bug that was solved some time ago,
>> but SableVM is not updated to
>> current classpath releases and as they joined Apache Harmony it's
>> unlikely they will ever update.
>
> That appears to be true, the last version of Classpath imported into
> sablevm-classpath is 0.20, from Jan. 13, 2006.

Has this resulted in a new SableVM release? As far as I know SableVM
1.13 is from December 2005 and so included either Classpath 0.18 or
0.19. :-(

> I guess the question here is, do we care about keeping Classpath
> compatability while waiting for Harmony?

I vaguely remember reading on this list changes on the classpath / vm
interface (for memory management and the like) make a little hard to
import a new classpath, and some sablevm developers are pissed off
because of this and don't want to work with classpath any more.


[]s, Fernando Lozano