public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: Bryce McKinlay <bryce@waitaki.otago.ac.nz>
To: James Williams <james_williams@optusnet.com.au>
Cc: java@gcc.gnu.org
Subject: Re: Attention GCJ devel team
Date: Tue, 23 Apr 2002 22:42:00 -0000	[thread overview]
Message-ID: <3CC6422E.80808@waitaki.otago.ac.nz> (raw)
In-Reply-To: <001a01c1eb49$ab9652a0$cd901cd3@computer>

James Williams wrote:

>For myself I'm not convinced that generating the javadoc would violate any
>copyright for the following reasons.
>
>1.  deprecation is a part of the specification and deprecation is part of
>the javadoc, so how can the javadoc be excluded?
>

The @deprecated tags (and, perhaps, the @since version tags) are a 
special case. They may be used buy the compiler, so you could argue that 
they must be reproduced in order to properly implement the API. Thus, I 
think it is ok to include those.

>2.  In the license that I agreed to Sun granted me a license for the
>specification (which includes all of the javadocs) and nowhere within the
>license does it state that I don't have the freedom to recreate the javadoc.
>

The documentation is Sun's copyrighted work. We use that documentation 
to produce an implementation of the Java API. However, like any book, we 
cannot simply copy the contents and pass it off as our own.

regards

Bryce.


  reply	other threads:[~2002-04-24  5:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-23 22:29 James Williams
2002-04-23 22:42 ` Bryce McKinlay [this message]
     [not found] <001e01c1e797$c91c2f30$c47831d2@computer>
2002-04-21 22:22 ` Bryce McKinlay
2002-04-22  0:22   ` Nic Ferrier
2002-04-22  1:27     ` James Williams
2002-04-22 11:03     ` Raif S. Naffah
2002-04-23  7:25   ` Oskar Liljeblad
2002-04-23 18:04     ` Bryce McKinlay

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=3CC6422E.80808@waitaki.otago.ac.nz \
    --to=bryce@waitaki.otago.ac.nz \
    --cc=james_williams@optusnet.com.au \
    --cc=java@gcc.gnu.org \
    /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).