On Fri, Dec 10, 1999 at 07:46:50PM -0600, Aaron M. Renn wrote:
>
> Unfortunately, changes in Japhar 0.08 broke Classpath compatibility.
> You can't run them together right now. Hopefully that will be fixed
> in the next couple months. Right now the only Japhar I can swear
> works with the first classpath release is 0.07.
What should be done to let Japhar and Classpath work together again?
Note that I don't have Japhar or Classpath working at this moment.
I have both of the current CVS trees, but Classpath seems to depend
on Japhar to compile correctly and Japhar seems to need nspr which
I have not yet downloaded. I don't have a lot of experience (none
to be exactly :) with the build process or with the way Classpath
and Japhar should work together. But I do have some free time now
and I am willing to learn.
If there is any other way I could help please tell.
I saw that there is no java.applet, java.util.jar or java.util.zip yet,
which seem not to hard to write. There are a lot of java.awt classes missing,
which is probably a lot of work, but maybe I could begin writing some
simple classes that are missing (are all java 1.1 awt classes already done?)
Are you going to use the ninja rmi classes that kaffe is working on (under
lgpl I believe) or should they be adapted especially for Classpath?
And ofcourse there is no javax.swing yet but I would not know where to start
with that package since I have absolutely no experience with it.
If Classpath wants to deliver any of the "standard" java tools such as
appletviewer, jarsigner, javadoc, keytool, javap, native2ascii, serialver,
jar, maybe I could start writing those.
Cheers,
Mark
