This is the mail archive of the
mailing list for the Mauve project.
Re: Adding serialized version uid tests to mauve
- From: Brian Jones <cbj at gnu dot org>
- To: Dalibor Topic <robilad at yahoo dot com>
- Cc: Mauve Discussion Mailing List <mauve-discuss at sourceware dot cygnus dot com>
- Date: 18 Nov 2001 23:12:10 -0500
- Subject: Re: Adding serialized version uid tests to mauve
- References: <email@example.com>
Dalibor Topic <firstname.lastname@example.org> writes:
> I'm thinking about contributing serial version UID
> tests to mauve, which would test whether a class has
> the proper serial version uid. Is there any desire for
> such tests in mauve?
It is possible that Japize serves these needs. See
> Actually, is there some written "Contributing" and
> "Hacking Mauve" documentation available? I found the
> contributing section on the web page to be, well,
> blank, and the documentation in the CVS wasn't that
> helpful on the topic either.
The README has the necessary information, although I too find that
figuring out how to use it is not so obvious.
You must set variables before running configure. If you change them,
JAVA Name of Java interpreter to use
JAVAC Name of Java (to class) compiler to use
I use the following values for ORP & Classpath
JAVA=~/orp-1.0.8/mains/orp/Linux/dbg/orp -classpath /usr/local/classpath/share/classpath:.
(Umm, 1.0.8 doesn't work for me yet btw so don't expect much if you
Some classes in Mauve apparently have a method (non-constructor) of
the same name as the class and Jikes doesn't like those, the rest seem
Here's the hard part. The readme talks about using KEYS=... and here
is the only way I've tried that works.
make KEYS=classpath check
In the "mauve" directory I've placed a file called "mauve-classpath"
with entries like this. A version of this file is checked into
Classpath's CVS and gcj has a similar file in its CVS tree.
Brian Jones <email@example.com>