8374355: Update copyright year to 2025 for demo in files where it was missed

[mrserb]

The copyright year in demo files updated in 2025 has been bumped to 2025.

The next command can be run (on top of this PR) to verify that each file had prior commits in 2025:

git diff HEAD~1 --name-only | while read f; do git log HEAD~1 --since="2025-01-01" --oneline -- "$f" | head -1 | grep -q . || echo "NOT IN 2025: $f"; done

---

Progress

• Change must be properly reviewed (1 review required, with at least 1 Reviewer)
• Change must not contain extraneous whitespace
• Commit message must refer to an issue

Issue

• JDK-8374355: Update copyright year to 2025 for demo in files where it was missed (Sub-task - P4)

Reviewers

• Alexey Ivanov (@aivanov-jdk - Reviewer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/28991/head:pull/28991
$ git checkout pull/28991

Update a local copy of the PR:
$ git checkout pull/28991
$ git pull https://git.openjdk.org/jdk.git pull/28991/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 28991

View PR using the GUI difftool:
$ git pr show -t 28991

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/28991.diff

Using Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back serb! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[openjdk]

@mrserb This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

8374355: Update copyright year to 2025 for demo in files where it was missed

Reviewed-by: aivanov

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been 16 new commits pushed to the master branch:

• c6246d5: 8374383: Update the copyright year to 2025 in the remaining files under test/ where it was missed
• 36d2c27: 8374327: Update copyright year to 2025 for files in java.base added/updated by commits in 2025
• 3fd7bde: 8374378: Update copyright year to 2025 for jdk.internal.vm.ci in files where it was missed
• ... and 13 more: https://git.openjdk.org/jdk/compare/534c33d0ef7daa0d0d5b56a1101b4c9d47a48049...master

As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

[openjdk]

@mrserb The following label will be automatically applied to this pull request:

• client

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command.

[mlbridge]

Webrevs

• 00: Full (82ad0738)

[mrserb]

Looking for volunteers to review this patch. It cannot be integrated in 2026.

[mrserb]

/integrate

[openjdk]

Going to push as commit 2447e07.
Since your change was applied there have been 18 commits pushed to the master branch:

• a1a75ab: 8373642: Test vmTestbase/nsk/monitoring/GarbageCollectorMXBean/CollectionCounters/CollectionCounters003/TestDescription.java failed
• 97f4f00: 8373917: test/hotspot/jtreg/vmTestbase/nsk/monitoring: -iterations setting misused in tests
• c6246d5: 8374383: Update the copyright year to 2025 in the remaining files under test/ where it was missed
• ... and 15 more: https://git.openjdk.org/jdk/compare/534c33d0ef7daa0d0d5b56a1101b4c9d47a48049...master

Your commit was automatically rebased without conflicts.

[openjdk]

@mrserb Pushed as commit 2447e07.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.