From: Steven Schwarz <schwarz@solekai.com>
To: mauve-discuss@sources.redhat.com
Subject: can Mauve help me test a PersonalJava implementation?
Date: Thu, 28 Apr 2005 22:52:00 -0000 [thread overview]
Message-ID: <XFMail.20050428155232.schwarz@solekai.com> (raw)
Hi,
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
implementation relaxed.)
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.
Questions:
* 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
and experiences?
* 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
repository?
Thanks,
sts
next reply other threads:[~2005-04-28 22:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-28 22:52 Steven Schwarz [this message]
2005-04-29 9:36 ` Thomas Zander
2005-04-29 15:17 ` Steven Schwarz
2005-04-29 15:31 ` Dalibor Topic
2005-04-29 15:33 ` Archie Cobbs
2005-04-29 16:39 ` Steven Schwarz
2005-04-29 16:46 ` Steven Schwarz
2005-05-09 16:19 ` Tom Tromey
2005-04-29 16:45 ` Thomas Zander
2005-04-30 23:28 ` Tom Tromey
2005-05-02 16:44 ` Steven Schwarz
2005-05-02 17:03 ` Thomas Zander
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=XFMail.20050428155232.schwarz@solekai.com \
--to=schwarz@solekai.com \
--cc=mauve-discuss@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).