AW: sablevm[-classpath] maintenance (was Re: GregorianCalendar Problem)

Hi all,


Thanks for all the information about my GregorianCalendar problem!
Well, I am one of this non-academic users who is alienated by this, =
Classpath is currently on version 0.92, quite far away from 0.19...
I don't feel able to do some maintance work on the sablevm-classpath, =
sorry.
I guess, I will use JNI to read the system's time and date over a =
C-prog...


Cheers
Marco


-----Urspr=FCngliche Nachricht-----
Von: [email protected] =
[mailto:[email protected]] Im Auftrag von Chris Pickett
Gesendet: Montag, 16. Oktober 2006 01:12
An: Fernando Lozano
Cc: SableVM Users Mailing List
Betreff: sablevm[-classpath] maintenance (was Re: GregorianCalendar =
Problem)

Fernando Lozano wrote:
> Hi Chris,
>=20
>>> AFAIK this is a known classpath bug that was solved some time ago,=20
>>> 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=20
>> sablevm-classpath is 0.20, from Jan. 13, 2006.
>=20
> 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=20
> 0.19. :-(

$ svn log svn://svn.sablevm.org/sablevm/tags | head -n 4

------------------------------------------------------------------------
r3819 | egagnon | 2005-03-24 15:50:37 -0500 (Thu, 24 Mar 2005) | 2 lines

* Tagged sablevm-1.11.3.

$ svn log svn://svn.sablevm.org/sablevm-classpath/tags | head -n 4

------------------------------------------------------------------------
r3820 | egagnon | 2005-03-24 15:51:28 -0500 (Thu, 24 Mar 2005) | 2 lines

* Tagged sablevm-classpath-1.11.3.

However, the trunks of both sablevm and sablevm-classpath were updated =
much more recently and I think those suffering from bugs might want to =
at least try updating to a more recent version.  Whether or not this =
fixes the specific GregorianCalendar issue I don't know, that would =
require some digging in the Classpath repository or bugzilla.

svn://svn.sablevm.org/sablevm[-classpath]/trunk

>=20
>> I guess the question here is, do we care about keeping Classpath=20
>> compatability while waiting for Harmony?
>=20
> I vaguely remember reading on this list changes on the classpath / vm=20
> interface (for memory management and the like) make a little hard to=20
> import a new classpath, and some sablevm developers are pissed off=20
> because of this and don't want to work with classpath any more.

I don't think it's a question of being pissed off.  People just don't =
have either time for or interest in maintaining SableVM right now.  It's =
used a lot for research purposes (I can count about 10 research projects =
off the top of my head---Etienne's 5 plus another 5 at McGill, including =
my own) and in many cases that means Classpath fixes are irrelevant to =
us.

It may be the case that this alienates non-academic users, but if =
someone outside of UQAM or McGill wants to prepare an updated=20
SableVM+Classpath release I think the contribution would be quite
welcome.  In order to prepare such a release, Subversion write access to =
branches of both sablevm[-classpath] is available, as Etienne has =
mentioned.

Cheers,
Chris

_______________________________________________
SableVM-user mailing list
[email protected]
http://sablevm.org/lists/control/listinfo/sablevm-user