[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [jakartaee-tck-dev] About copyright plugin potential fix
|
The header provides instructions for adding copyrights for
changes to existing files.
After the notice text, add the new copyright statement. Here are
the relevant instructions lifted from the header:
If applicable, add the following below the License
Header, with the fields enclosed by brackets [] replaced by your
own identifying information: "Portions Copyrighted [year] [name
of copyright owner]"
So,
- To existing files, below the header text, add: "Portions
copyrighted 2020, Contributors to the Eclipse Foundation."
- To new files that build from the previous version (I suspect
most if not all will copy the previous version), do the same.
- For anything completely new, use the project license. (EPL 2.0
+ GPLv2 w/CpE)
We can ask the Eclipse clearance team about this as well if what
I have written above doesn't seem to cover the concern. It seems
plausible that there might be some leeway in terms of who the "DO
NOT ALTER ..." statement is intended for. Originators (i.e.
contributors/committers) may be able to make be allowed to make
some changes (e.g. adding the current copyright year), while
recipients/end-users might not. The next step from here could be
to send a question to license@xxxxxxxxxxx.
-- Ed
On 5/4/2020 9:54 AM, Scott Marlow
wrote:
Hi Cesar,
Thanks for making the PR!
Kevin asked a question about the "DO NOT ALTER..."
copyright aspects that I don't know how to answer, other than
to possibly eliminate the DTDs + XSD files that have this (or
something else).
Some example file links:
Can someone explain the meaning of the "DO NOT ALTER"
copyright statement and how that aligns with the Eclipse
guidance to update the copyright date when modifying the
contents of the file?
Should we replace the existing XSDs with EE 9 schema
definitions? How about the DTDs?
Scott
Hi,
During the review of javax.jms to jakarta.jms PR
[1], Scott provided context about an issue with the
copyright plugin [2].
I opened the following fix proposal that will
prevent false positives by having a new -e flag to be
an opt-in feature:
_______________________________________________
jakartaee-tck-dev mailing list
jakartaee-tck-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev
_______________________________________________
jakartaee-tck-dev mailing list
jakartaee-tck-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev