Paul,
The last time someone asked this type of question on a forum it
was about auto-generated methods. E.g., JDT's ability to generate
hashCode, equals, and toString() methods from the field
declarations of the existing class...
Perhaps the statement about generated code could or should be
stronger. E.g., an EPL2 licensed generator produces results with
the same license and copyright as the input. I.e., perhaps EPL2
should dictate that a generator does not inject licenses,
copyrights, or alter intellectual property status when it
transforms input into output. In other words, if someone wants to
author a generator that violates this principle, they can't
license it under the EPL2. Just a thought.
Regards,
Ed
On 21.04.2017 18:14, Berg, Paul W
wrote:
I would be highly in favor of this. Stating that
the output of a code generator licensed under the EPL2 is
specifically not covered by the EPL2 unless otherwise stated in
the generated code would be very welcome.
_______________________________________________
epl-discuss mailing list
epl-discuss@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/epl-discuss