8273935: (zipfs) Files.getFileAttributeView() throws UOE instead of returning null when view not supported

[jerboaa]

Clean backport. Problem exists in 17 GA as well.

---

Progress

• Change must not contain extraneous whitespace
• Commit message must refer to an issue

Issue

• JDK-8273935: (zipfs) Files.getFileAttributeView() throws UOE instead of returning null when view not supported

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk17u pull/109/head:pull/109
$ git checkout pull/109

Update a local copy of the PR:
$ git checkout pull/109
$ git pull https://git.openjdk.java.net/jdk17u pull/109/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 109

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.java.net/jdk17u/pull/109.diff

[bridgekeeper]

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

This backport pull request has now been updated with issue from the original commit.

[openjdk]

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

8273935: (zipfs) Files.getFileAttributeView() throws UOE instead of returning null when view not supported

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 1 new commit pushed to the master branch:

• 4e707bc: 8268894: forged ASTs can provoke an AIOOBE at com.sun.tools.javac.jvm.ClassWriter::writePosition

Please see this link for an up-to-date comparison between the source branch of this pull request and the master branch.
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.

[mlbridge]

Webrevs

• 00: Full (1418b13a)

[jerboaa]

/integrate

[openjdk]

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

• 91dd244: 8266239: Some duplicated javac command-line options have repeated effect
• c26cd97: 8274326: [macos] Ensure initialisation of sun/lwawt/macosx/CAccessibility in JavaComponentAccessibility.m
• a9981fb: 8274381: missing CAccessibility definitions in JNI code
• 20afdfd: 8273278: Support XSLT on GraalVM Native Image--deterministic bytecode generation in XSLT
• cdd4075: 8273135: java/awt/color/ICC_ColorSpace/MTTransformReplacedProfile.java crashes in liblcms.dylib with NULLSeek+0x7
• 2586eb0: 8274087: Windows DLL path not set correctly.
• d6d5a9a: 8271170: Add unit test for what jpackage app launcher puts in the environment
• a702838: 8270116: Expand ButtonGroupLayoutTraversalTest.java to run in all LaFs, including Aqua on macOS
• 84f6cb4: 8273498: compiler/c2/Test7179138_1.java timed out
• c4b3d62: 8273924: ArrayIndexOutOfBoundsException thrown in java.util.JapaneseImperialCalendar.add()
• ... and 18 more: https://git.openjdk.java.net/jdk17u/compare/d93500168cd120165fedb9609fdf2e10458976dd...master

Your commit was automatically rebased without conflicts.

[openjdk]

@jerboaa Pushed as commit de6899b.

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