From: Brian Jones <cbj@gnu.org>
To: Daryl Lee <dlee@altaregos.com>
Cc: Mauve Discuss <mauve-discuss@sources.redhat.com>
Subject: Re: API Differences
Date: Thu, 26 Dec 2002 17:45:00 -0000 [thread overview]
Message-ID: <m3d6nock01.fsf@lyta.haphazard.org> (raw)
In-Reply-To: <20021226202921.GA23724@tigger.localdomain>
Daryl Lee <dlee@altaregos.com> 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
--
Brian Jones <cbj@gnu.org>
next prev parent reply other threads:[~2002-12-27 1:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-26 12:29 Daryl Lee
2002-12-26 17:45 ` Brian Jones [this message]
2002-12-27 4:37 ` Dalibor Topic
2002-12-27 5:28 ` Daryl Lee
2002-12-27 7:06 ` Daryl Lee
2002-12-27 16:50 ` 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=m3d6nock01.fsf@lyta.haphazard.org \
--to=cbj@gnu.org \
--cc=dlee@altaregos.com \
--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).