[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[eclipse.org-architecture-council] [Bug 249959] [discussion] How to treat copyright headers for checked-in generated sources?
|
https://bugs.eclipse.org/bugs/show_bug.cgi?id=249959
Product/Component: Community / Architecture Council
Ed Merks <Ed.Merks@xxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |Ed.Merks@xxxxxxxxx,
| |janet.campbell@xxxxxxxxxxx
--- Comment #2 from Ed Merks <Ed.Merks@xxxxxxxxx> 2008-10-07 10:27:55 -0400 ---
Martin,
I definitely don't agree with these statements. We should get Janet's advice.
My position with EMF's generator (which addresses this specific shortcoming of
JAXB) has always been that the copyright that applies to the input to the
generator is the same copyright that applies to the output, much like the
copyright on the .class file is the same as the copyright of the source .java
file. I.e., the incoming intellectual property's copyright is preserved as it
passes through the transformation process from input to output.
Moreover, a generator does *not* inject copyrightable material nor intellectual
property. So while the templates of the generator are copyrighted and do
represent intellectual properly, their application to produce a final generated
result does not inject that copyright or intellectual copyright into the final
result. Just as the byte code generated by a compiler, no matter how smart,
doesn't affect the copyright.
The bottom line is that what's produced by EMF's generator is purely the
property of the original user. I'm not sure what JAXB's position is on this...
Note that EMF's generator is a merging generator, so changes to the schema can
be applied to produce an incremental delta in the generated files. I.e, it
will not overwrite all the files with new results and will not change the
package header comment, in existing files.
--
Configure bugmail: https://bugs.eclipse.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
