6517125: FontStrike.getGlyphVectorOutline() not used

[gredler]

This method is not used and can be deleted from the entire FontStrike class hierarchy. There was some discussion in 2007 about re-enabling if there were performance benefits, but 20 years have passed and no performance issues have emerged. In fact, the macOS OpenJDK never implemented this method.

---

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-6517125: FontStrike.getGlyphVectorOutline() not used (Enhancement - P4)

Reviewers

• Phil Race (@prrace - Reviewer)
• Sergey Bylokhov (@mrserb - Reviewer)

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 28856

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

Using diff file

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

Using Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back dgredler! 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]

@gredler 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:

6517125: FontStrike.getGlyphVectorOutline() not used

Reviewed-by: prr, serb

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 146 new commits pushed to the master branch:

• 73a8629: 8374310: Update copyright year to 2025 for client-libs in files where it was missed
• 98b7792: 8372801: tools/sincechecker/modules/java.base/JavaBaseCheckSince.java fails with JDK 27
• 6ade348: 8374177: Update @SInCE of HotSpotAOTCacheMXBean after JDK-8373607
• ... and 143 more: https://git.openjdk.org/jdk/compare/d854a04231a437a6af36ae65780961f40f336343...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]

@gredler 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 (2fea151a)

[gredler]

/integrate

[openjdk]

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

• 3e6170c: 8374354: Update copyright year to 2025 for jdk.javadoc in files where it was missed
• 534c33d: 8374323: Update copyright year to 2025 for the build system in files where it was missed
• 73a8629: 8374310: Update copyright year to 2025 for client-libs in files where it was missed
• ... and 145 more: https://git.openjdk.org/jdk/compare/d854a04231a437a6af36ae65780961f40f336343...master

Your commit was automatically rebased without conflicts.

[openjdk]

@gredler Pushed as commit e65ace1.

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