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

Thanks for the reply.

I have already produced a version of the SimpleTestHarness that will
run on a 1.1.8 VM.  Then there are 39 1.1-tagged test classes that I
have identified as needing repair actually to run on a 1.1.8 VM.  I
have so far made repairs for 2 and have in mind doing a good number of
the 39.  But there may be some test classes that I will simply not
choose to utilize, those that make use of the AWT Robot class being
definite candidates for that list.  It might just be better to change
their tagging in my opinion.

When I am done, if there is interest in having this work committed,
I'll certainly be happy to make it available.

With regard to my question about history, I know about the -D option,
but my question was whether the current repository has revisions that
go back that far (4 years is an eternity in many development projects,
and many have to make compromises that "lose history" for various
reasons over such a long span).

Thanks again,
sts

On 30-Apr-2005 Tom Tromey wrote:
>>>>>> "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

  reply	other threads:[~2005-05-02 16:44 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
2005-05-02 16:44   ` Steven Schwarz [this message]
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.20050502094448.schwarz@solekai.com \
    --to=schwarz@solekai.com \
    --cc=mauve-discuss@sources.redhat.com \
    --cc=tromey@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).