This is the mail archive of the
mailing list for the Mauve project.
Re: Method of executing Mauve
- From: Tom Tromey <tromey at redhat dot com>
- To: Brian Jones <cbj at gnu dot org>
- Cc: Mark Wielaard <mark at klomp dot org>, GNU Classpath <classpath at gnu dot org>, Mauve News Group <mauve-discuss at sources dot redhat dot com>
- Date: 15 Nov 2002 09:04:58 -0700
- Subject: Re: Method of executing Mauve
- References: <email@example.com><1036694578.1177.118.camel@elsschot><firstname.lastname@example.org>
- Reply-to: tromey at redhat dot com
>>>>> "Brian" == Brian Jones <email@example.com> writes:
Brian> Fixed the URL. It should be simpler to configure/use Mauve. I
Brian> don't like having to export JAVA, JAVAC, before
Brian> configure/make... this choice should be defined at runtime
Brian> anyway instead of configure time.
I don't think these choices can be made at runtime. The problem is,
not every compiler may be able to compile the whole package and not
every runtime may have every class. For instance, when compiling and
running against classpath, you must omit javax.naming tests -- but
these work fine with gcj.
Brian> Btw, I think the current tag system is inadequate.
There was a long-ish discussion of Mauve test harness inadequacies
earlier this year. The real problem seems to be lack of time to
address them. I myself have neither time nor interest; the current
system works fine for my needs. Mostly that is because I never run
Mauve by hand, but instead let the libgcj test suite handle it for me.