"John Keiser" <[EMAIL PROTECTED]> writes:
> Right now we only support Japhar. But we want to support multiple VMs.
Yes.
> The simplest way to do this is to provide two JAR files: one, the
> VM-independent stuff (everything not in vm/reference), and two, the
> VM-dependent stuff. This makes it so that we can support multiple VMs
> without too much trouble.
Well, before providing a solution, perhaps backup and elucidate the
problem. Right now, supposing the --with-kaffe stuff worked (and we
had the kaffe dependent stuff coded) then to get Classpath to work
with Kaffe I would just reconfigure and recompile. (the native stuff
is different as well I guess...).
If you wanted to argue that you want to be able to compile Classpath
for every VM all at once, I could see that.
> However, I have to bring up an issue that could arise when we move to
> 1.2: the sealing of java.lang. Currently the VM interface involves
> package-private java.lang classes for security (making them public in
> another package could open up major holes if not dealt with properly). If
> there are two different JARs, I assume we'll have some sort of problem with
> sealing? Can someone who knows about sealing and such elucidate? Is there
> away around the problem, perhaps some way to reference a "trusted JAR file"?
If these are real issues, then I think we should just stick to keeping
them in the original jar/zip.
There is still the issue mentioned earlier about being able to specify
something like ./configure --with-package=java.beans to make just
java.beans and related classes/native stuff.
Brian
--
|-------------------------------|Software Engineer
|Brian Jones |[EMAIL PROTECTED]
|[EMAIL PROTECTED] |http://www.nortel.net
|http://www.classpath.org/ |------------------------------
