chore: TRG 7.00 - update copyright header

[borisrizov-zf]

Description

Comply with TRG 7.00 and update all copyright headers to point to current year.

Command used:

find . -type f -exec sed -i -E 's/(.*)Copyright \(c\) 2021,2023 Contributors to the Eclipse Foundation/\1Copyright \(c\) 2021,2024 Contributors to the Eclipse Foundation/g' {} \;

Pre-review checks

Please ensure to do as many of the following checks as possible, before asking for committer review:

• DEPENDENCIES are up-to-date. Dash license tool. Committers can open IP issues for restricted libs.
• Copyright and license header are present on all affected files

[sonarcloud]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[carslen]

Kudos for attempting to meet TRGs, but do not update the Copyright header just because of the year change. The year (range) in the copyright header should be changed in case of changes to the file.
The Eclipse Handbook recommendation: "The year is expressed as a single year or a range spanning the year of the very initial assertion and that of the most recent change."

Depending on the IDE you're using, some IDE's have great features to support you to keep your copyright header up to date (e.g. JetBrains Copyright feature available for most Jetbrains IDEs). Other IDEs or Editors like VS Code may provide similar features/Plugins/Extensions (e.g. VS Code Extensions).

Please do not merge this PR, but update the copyright header when code is changed/extended.

[borisrizov-zf]

@carslen Ok, no problem, but we should maybe update the TRG text as it led me to believe that this is necessary.

[carslen]

Feel free to create a draft with an updated TRG. I guess you're pointing to this section of the TRG:

Keep the following updated for each pull request to the default branch (main)

• Legal Documentation: TRG 7.01
• License and copyright header: TRG 7.02
  • must be present in every file if possible
  • update the year in the copyright section at the beginning of each new year

From my point of view this isn't misleading. The TRG describes recurring activities you have to take care of, when creating a new PR because of changes to the code, docs, etc. As no changes have been made to the code, no update of the copyright headers is required.