This is the mail archive of the
mailing list for the Mauve project.
Re: API Differences
- From: Brian Jones <cbj at gnu dot org>
- To: Daryl Lee <dlee at altaregos dot com>
- Cc: Mauve Discuss <mauve-discuss at sources dot redhat dot com>
- Date: 26 Dec 2002 20:45:34 -0500
- Subject: Re: API Differences
- References: <20021226202921.GA23724@tigger.localdomain>
Daryl Lee <firstname.lastname@example.org> writes:
> Having completed the java.io JDK 1.1 tests, I am now ready to move on to
> the 1.2 tests, but I need an efficient means of knowing the differences
> between the two versions of the APIs. Is there a tool I can use that will
> identify exactly what needs to be tested?
japicompat/japize can be used for this purpose. Take the 1.1 and 1.2
files from the japize website and run japicompat to compare them.
> An associated question has more to do with the mauve 'choose' script, which
> looks more and more like Greek everytime I try to figure out how it works.
> If I specify JDK1.2 in mauve-classpath, will it cause the selected JDK1.0 and
> JKD1.1 tests to be run as well as any JDK1.2 tests I create? (Please say
> yes!) A corollary question is, "What is the difference between the 'uses:'
> declaration in mauve tests and the standard Java 'import' statement?"
Yes, it will do what you think and select the previous version tests
as well. Uses is for the choose script... or other scripts, to know
that test foo in foo.java also uses bar in bar.java (must be in same
package currently). So it would be nice in some cases to avoid code
duplication of utility methods useful to a particular subset of tests.
Brian Jones <email@example.com>