This is the mail archive of the
mailing list for the Mauve project.
can Mauve help me test a PersonalJava implementation?
- From: Steven Schwarz <schwarz at solekai dot com>
- To: mauve-discuss at sources dot redhat dot com
- Date: Thu, 28 Apr 2005 15:52:32 -0700 (PDT)
- Subject: can Mauve help me test a PersonalJava implementation?
- Reply-to: Steven Schwarz <schwarz at solekai dot com>
I've been tasked with confirming the claim made by a PersonalJava VM
vendor that their implementation passes the Mauve suite.
(If you're not familiar with PersonalJava, you can just think of it
as, basically JDK 1.1.8, with some of the fine-grained security model
APIs from JDK 1.2 thrown in, and some of the expectations of the AWT
I've had a quick try at using Mauve to test various JDKs:
JDK 1.1.8 (from blackdown)
JDK 1.2.2 (from Sun)
JDK 1.3.1 (from Sun)
JDK 1.4.2 (from Sun)
Of these, I only had success with JDK 1.4.2. All of the others failed
to compile the SimpleTestHarness, as well as some of the classes
involved in various individual tests.
I was using
make KEYS=JDK1.1 check
in hopes of limiting the scope of Mauve to tests appropriate for the
1.1 level of JDK. Doing that I was surprised to see compile time
errors from any of the tests, but really surprised to see that the
basic harness was using features from JDK 1.4.
* Is anyone else out there using Mauve for testing such old JDKs as
1.1.8 (or even PersonalJava)? If so, could you share your strategy
* With respect to this vendor's claim, it appears to be made in
marketing literature dated 2001. Is it possible to go back to the
sources that would have been current in 2001 in the current CVS