From: Tom Tromey <tromey@redhat.com>
To: Steven Schwarz <schwarz@solekai.com>
Cc: mauve-discuss@sources.redhat.com
Subject: Re: can Mauve help me test a PersonalJava implementation?
Date: Sat, 30 Apr 2005 23:28:00 -0000 [thread overview]
Message-ID: <m3sm17etis.fsf@localhost.localdomain> (raw)
In-Reply-To: <XFMail.20050428155232.schwarz@solekai.com>
>>>>> "Steven" == Steven Schwarz <schwarz@solekai.com> writes:
Steven> Of these, I only had success with JDK 1.4.2. All of the others failed
Steven> to compile the SimpleTestHarness, as well as some of the classes
Steven> involved in various individual tests.
The intent was always that this would work properly -- that you could
compile the 1.x subset of Mauve with a 1.x compiler and runtime, and
then try it.
However, this has obviously bit-rotted, probably because nobody really
uses anything < 1.4 any more.
Patches to fix this are welcome ... :-)
But of course we can't promise it won't break again unless this is
done with some regularity.
Steven> * With respect to this vendor's claim, it appears to be made in
Steven> marketing literature dated 2001. Is it possible to go back to the
Steven> sources that would have been current in 2001 in the current CVS
Steven> repository?
Sure, see the '-D' option to cvs.
Tom
next prev parent reply other threads:[~2005-04-30 23:28 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
2005-04-29 16:45 ` Thomas Zander
2005-04-30 23:28 ` Tom Tromey [this message]
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=m3sm17etis.fsf@localhost.localdomain \
--to=tromey@redhat.com \
--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).