Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (asf.osuosl.org: domain of eljotpl@gmail.com designates
 66.249.82.193 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=YlpvJDPkyAsmLvGDO2gU2DPgWkZqFO3kAg8Jm+L2Ri3CGGkQE9/SvpkpVv62d5EoVNr7P7VN9QzZ4pBWqsxWeo5TaibBuUipR80JNiai6uZMsPX9ke0NedyM3WPbs4jljH1tP+Y0i13P00q+scDbpIdvhPy2s4BUmRKPashNuCg=
Message-ID: <1b5bfeb50601021347h2514c3feg@mail.gmail.com>
Date: Mon, 2 Jan 2006 22:47:24 +0100
From: Jacek Laskowski <eljotpl@gmail.com>
To: dev@geronimo.apache.org
Subject: Re: How to proceed with patches to specs
In-Reply-To: <1b5bfeb50601021341t5b787b43t@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <1b5bfeb50512311717s5cdf0338i@mail.gmail.com>
	 <7A48B066-D852-4D4B-BBF0-4FE47C64DB89@yahoo.com>
	 <43B80232.1010509@toolazydogs.com>
	 <1b5bfeb50601020209h1dfc924fl@mail.gmail.com>
	 <43B965BB.60803@toolazydogs.com>
	 <1b5bfeb50601021341t5b787b43t@mail.gmail.com>

Sorry, the previous email went out too early. Trying again...

2006/1/2, Jacek Laskowski <eljotpl@gmail.com>:
> 2006/1/2, Alan D. Cabrera <list@toolazydogs.com>:
>
> >  That's the $64 question.  Jason knows the secret incantations needed t=
o be
> > performed to do this.  Jason?
>
> Hi,
>
> While awaiting Jason's response and trying to provide a test case for
> Jakob's recent patch, I found a test class - javax.mail.internet.
...InternetHeadersTest - that contained the following:

//
// This source code implements specifications defined by the Java
// Community Process. In order to remain compliant with the specification
// DO NOT add / change / or delete method signatures!
//

It made me think about the source code and its origins. As far as I
remember, we're not allowed to use JavaMail source code and merely
copy it over to our code. It's against the license, isn't it? What I
can't recall is the list of allowed materials we /are/ allowed to use
to build our own implementation. What is on the list? I guess it's
javadoc and the spec itself. Anything else? How could happen that the
above statement (This source code implements...) found its place in
/our/ code?

Cheers,
Jacek