-
Bug
-
Resolution: Fixed
-
P4
-
25
-
b14
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8366335 | 21.0.10-oracle | Abhishek N | P4 | Resolved | Fixed | master |
| JDK-8366336 | 17.0.18-oracle | Abhishek N | P4 | Resolved | Fixed | master |
The Jar testing of UTF8 Manifest in ValueUtf8Voding produces misleading output and possible UTF8DataFormatExceptions.
The diagnostic output is not relevant to the test success or failure.
The test writes the manifest to a ByteArrayOutputStream and then naively attempts to create a single string from the byte array.
However, the manifest uses a 70 column format with continuation lines.
The continuation format may break the multi-character utf8 sequence across lines, causing either a UTF8DataFormatException or the insertion of replacement characters '\ufffd'.
Frequently, the output contains mostly replacement characters due to this mis-interpretation and is useless.
The diagnostic output is not relevant to the test success or failure.
The test writes the manifest to a ByteArrayOutputStream and then naively attempts to create a single string from the byte array.
However, the manifest uses a 70 column format with continuation lines.
The continuation format may break the multi-character utf8 sequence across lines, causing either a UTF8DataFormatException or the insertion of replacement characters '\ufffd'.
Frequently, the output contains mostly replacement characters due to this mis-interpretation and is useless.
- backported by
-
JDK-8366335 Jar Manifest test ValueUtf8Coding produces misleading diagnostic output
-
- Resolved
-
-
-
- Resolved
-
- links to
-
Commit(master)
openjdk/jdk/ffa63409
-
Review(master)
openjdk/jdk/23971