From: Greg Orlowski <greg.orlowski@gmail.com>
To: mauve-discuss@sources.redhat.com
Subject: legal question about writing mauve test cases
Date: Sun, 13 Nov 2005 03:32:00 -0000 [thread overview]
Message-ID: <4c60c7920511121932k195c6515mad4a7f281dc189f2@mail.gmail.com> (raw)
Hi,
Is it legal to use the reflection api's w/ sun's jdks to generate
lists of method signatures and then compare them to gnu-classpath's
method signatures as a reference-point from which to develop test
cases for mauve?
Does using the reflection capabilities of java with sun's libraries
constitute reading source code (legally)?
I've been doing some of this anyway just to be able to compare
gnu-classpath & sun's implementation. If it's legal, I'd like to take
some diffs of output from running reflection methods as a reference
for some test cases.
I'd like to contribute to classpath, but I'll be using sun's tools
extensively at my job, and I'm worried that I'll be tainted by doing
so.
thanks for any information you can give me on this!
-Greg
next reply other threads:[~2005-11-13 3:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-13 3:32 Greg Orlowski [this message]
2005-11-13 13:19 ` Dalibor Topic
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=4c60c7920511121932k195c6515mad4a7f281dc189f2@mail.gmail.com \
--to=greg.orlowski@gmail.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).