public inbox for mauve-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Steven Schwarz <schwarz@solekai.com>
Cc: Archie Cobbs <archie@dellroad.org>,
	classpath@gnu.org, mauve-discuss@sources.redhat.com
Subject: Re: can Mauve help me test a PersonalJava implementation?
Date: Mon, 09 May 2005 16:19:00 -0000	[thread overview]
Message-ID: <m3oebke5mv.fsf@localhost.localdomain> (raw)
In-Reply-To: <XFMail.20050429094200.schwarz@solekai.com>

Steven> Ok.  I used -target 1.1 and that worked to produce class files that
Steven> are acceptable to a JDK 1.1.8 VM.  Now the problem is that
Steven> SimpleTestHarness won't run on a JDK 1.1.8 VM:
Steven>         java.lang.NoClassDefFoundError: java/lang/Comparable

Yeah, -target N is not that useful if you are using classes that
didn't appear in that release.  (This is something we could teach the
free systems to warn about :-)

Steven> If I go to the labor of crafting a replacement for SimpleTestHarness
Steven> that confines itself to 1.1 APIs, will I also find that there are
Steven> individual tests for which the subject of the test is a 1.1 API (and
Steven> therefore the test earns the JDK1.1 tag) but the way the test is
Steven> written drags in 1.2 - 1.5 APIs for the test verification?

Probably.  Those are bugs, though.

Steven> I come back to my original question: are people out there really using
Steven> the current Mauve with PersonalJava (or JDK 1.1) implementations?

Not that I know of.

Tom

  reply	other threads:[~2005-05-09 16:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-28 22:52 Steven Schwarz
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 [this message]
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=m3oebke5mv.fsf@localhost.localdomain \
    --to=tromey@redhat.com \
    --cc=archie@dellroad.org \
    --cc=classpath@gnu.org \
    --cc=mauve-discuss@sources.redhat.com \
    --cc=schwarz@solekai.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).