public inbox for mauve-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Jeff Sturm <jsturm@one-point.com>
Cc: Michael Koch <konqueror@gmx.de>,
	GNU Classpath Project <classpath@gnu.org>,
	Mauve News Group <mauve-discuss@sources.redhat.com>
Subject: Re: Eclipse and Classpath
Date: Wed, 28 Apr 2004 20:02:00 -0000	[thread overview]
Message-ID: <877jvzhoef.fsf@fleche.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0404241127510.5951-100000@ops2.one-point.com>

Jeff> (What about Mauve?  Much of Eclipse's usefulness for us comes from
Jeff> interactively running the test suite so we get a very quick
Jeff> edit/compile/test/debug cycle.  But eclipse only knows about junit-style
Jeff> tests, not the gnu.testlet classes in Mauve.)

I think Graydon changed Mauve to use JUnit at one point, but it never
went in.  I think there was some confusion about some points I made.

It's time to revisit this (various folks pointed this out to me at the
recent RH meeting).  IMO anything that makes Mauve easier to hack is a
good thing.  My only real requirement is that we still be able to run
the gcj test suite; I don't think there is any substantial problem
here.

Tom

       reply	other threads:[~2004-04-28 20:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.44.0404241127510.5951-100000@ops2.one-point.com>
2004-04-28 20:02 ` Tom Tromey [this message]
2004-04-28 21:56   ` Thomas Zander
2004-04-30 23:22     ` Tom Tromey
     [not found] <OFD30D19BA.CBC8235A-ON85256E84.007C2292-85256E84.007C73EC@us.ibm.com>
2004-04-28 22:54 ` Archie Cobbs
2004-04-29  5:09   ` C. Brian Jones

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=877jvzhoef.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=classpath@gnu.org \
    --cc=jsturm@one-point.com \
    --cc=konqueror@gmx.de \
    --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).