Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Received-SPF: pass (athena.apache.org: domain of alexei.fedotov@gmail.com
 designates 66.249.92.173 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=WSX0UYkI3BIGqTyz031NsQ3hY7MR3aut5yPKJ6lKZaeNSr+ge23t/nzL1hIi8NjD6BYOuqjo076tDncTOkbIYyOCwQt7ibhLrDgBfkVNsuxmCUvTegetRe6gMeVrtyR/xVBG00Xxrw6bBfPPjLmoiwFZiD+6obGlGTmOmbwjuW0=
Message-ID: <c30d70960710240538h11df4079medcc0b5d85cdbe0c@mail.gmail.com>
Date: Wed, 24 Oct 2007 16:38:03 +0400
From: "Alexei Fedotov" <alexei.fedotov@gmail.com>
To: dev@harmony.apache.org
Subject: Re: [OT] new tools for Harmony
In-Reply-To: <471F0C6B.90300@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <471EBF57.9020600@gmail.com> <471ECE53.7010803@gmail.com>
	 <471ED9A6.4050703@gmail.com> <471F0C6B.90300@gmail.com>

Hello,
I don't fully understand IP issues around javacc:

   * The tool was initially developed by Sreeni while working for Sun.
   * Then Sreeni left the company and created Metamata, which worked
as caretaker for the tool and had a different license [2] than now.

May be we should not be paranoid about it, but it worth to be mentioned.
[1] http://www.cs.purdue.edu/homes/hosking/352/javaccdocs/usage.html


On 10/24/07, Tim Ellison <t.p.ellison@gmail.com> wrote:
> Regis wrote:
> > Tim Ellison wrote:
> >> Regis wrote:
> >>> JavaCC is BSD licensed, it convert grammar file to java file, and
> >>> according to it's FAQ[2], the java files produced by javacc
> >>> can be used in any way.
> >>>
> >>> And javacc created java files with first line like this:
> >>> "/* Generated By:JavaCC: Do not edit this line. FilterParser.java */"
> >>>
> >>> Is it acceptable?
> >>
> >> Yep.  Please ensure that you also contribute the grammar files that you
> >> write as input to javacc.  Both the grammar files and the resulting java
> >> files should have the ASF standard block comments at the top and be
> >> checked into SVN.  It's probably a good idea to also keep the 'Do not
> >> edit' instruction just so people know.
> >>
> > So we must move the 'Do not edit' instruction below the ASF standard block
> > comments.
>
> It is not strictly necessary for the ASF comment to be the very first
> thing in the file, but given that it is first by convention I would say
> you should move the instruction below if it does not require a great effort.
>
> > And I think we should add a additional 'README' file, give some
> > instruments about
> > how to use the grammar files and generated source files.
>
> Yes, instructions to make the process reproducible are important.
>
> Thanks,
> Tim
>


-- 
With best regards,
Alexei,
ESSD, Intel