> > >From Edouard G. Parmelan <[EMAIL PROTECTED]>, one of the Kaffe upstream > > >developers, > > a proposal to the Java policy: > > > > Each java-virtual-machine comes with a /etc/java-core-classes (using > > alternatives to manage it). This file contains the list of jars and > > directories with core classes. > > > > For Kaffe, here is an example: > > > > # Kaffe Core Classes > > /usr/share/kaffe/Klasses.jar > > /usr/share/kaffe/comm.jar > > /usr/share/kaffe/pjava.jar > > /usr/share/kaffe/servlet.jar > > /usr/share/kaffe/rmi.jar > > #/usr/share/kaffe/tools.jar > > #/usr/share/kaffe/microsoft.jar > > #/usr/share/kaffe/kjc.jar > > > > And may be, to help Jikes: > > > > # Debian policy for Java > > /usr/share/java/repository > > > > Advice?
It may be obvious, but there could be cases where one JVM uses different versions of a class library (or different class libraries). So just make sure to cater for versioned class libs. /usr/share/classpath0.00/rt.jar /usr/share/classpath -> symlinked to default / latest classpath ? /usr/share/classpath_with_sable_mods0.01/rt.jar John Leuner
