| Re: [ee4j-pmc] License guidance for auto-generated files |
_______________________________________________Auto-generated files (at least in Germany) do not fulfil any criteria needed to be copyrighted at all, as machines cannot hold copyright. Hence (at least in Germany) it must be "2".
-Markus
From: ee4j-pmc-bounces@xxxxxxxxxxx [mailto:ee4j-pmc-bounces@xxxxxxxxxxx] On Behalf Of Ivar Grimstad
Sent: Freitag, 14. Dezember 2018 17:18
To: EE4J PMC Discussions
Subject: Re: [ee4j-pmc] License guidance for auto-generated files
I would say "1" sounds like the reasonable answer, but there may be some rules that I am not aware of...
Ivar
On Fri, Dec 14, 2018 at 12:02 PM Mark Thomas <markt@xxxxxxxxxx> wrote:
Hi,
The Jakarta EL Reference Implementation has a JavaCC grammar for EL that
is licensed under the standard license:
EPL-2.0 OR GPL-2.0 WITH Classpath-exception-2.0
This grammar is then used as an input to JavaCC which generates a Java
parser for EL that consists of a handful of Java files.
A question has arisen as to what license header should be applied to the
generated files.
Is it:
1. The standard license?
2. No license (because they are auto-generated)?
3. Something else?
I'm expecting the answer to either be "1" or "1 or 2 but we recommend 1".
Currently, "1" is being used.
Thanks,
Mark
_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/ee4j-pmc
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/ee4j-pmc