From: Daryl Lee <dlee@altaregos.com>
To: Mauve Discuss <mauve-discuss@sources.redhat.com>
Subject: Re: API Differences
Date: Fri, 27 Dec 2002 05:28:00 -0000 [thread overview]
Message-ID: <20021227132812.GB5559@tigger.localdomain> (raw)
In-Reply-To: <20021227123744.53173.qmail@web10010.mail.yahoo.com>
That will make a great resource when I'm ready to move from 1.2 to 1.3 and
higher, but right now they don't seem to include the 1.1-1.2 differences.
On Fri, Dec 27, 2002 at 04:37:44AM -0800, Dalibor Topic wrote:
>
> --- Brian Jones <cbj@gnu.org> wrote:
> > 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.
>
> Or you could use http://javadiff.sourceforge.net/
> which is written to specifically go after changes in
> API docs. japitools are great to see what has changed
> on the binary compatibility side, but jdiff looks like
> a great way to see how specified semantics have
> changed/been clarified.
>
> best regards,
>
> dalibor topic
>
> __________________________________________________
> Do you Yahoo!?
> Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
> http://mailplus.yahoo.com
>
--
Daryl Lee
Open the present--it's a gift.
next prev parent reply other threads:[~2002-12-27 13:28 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
2002-12-27 4:37 ` Dalibor Topic
2002-12-27 5:28 ` Daryl Lee [this message]
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=20021227132812.GB5559@tigger.localdomain \
--to=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).