-
CSR
-
Resolution: Approved
-
P4
-
None
-
binary, behavioral
-
minimal
-
The functionality described in the JAR specification has not been implemented in Manifest.java. Therefore there should not be an issue with removing the wording from the JAR Specification.
-
Java API, Other
-
SE
Summary
Update the JAR specification to remove the statement on how an EOF is handled when it is the last character in the Manifest
Problem
The JAR specification defines Manifest EOF handling that has never been implemented in Manifest.java
Solution
Remove the following from the JAR specification as Manifest.java has never provided support for this:
- Before parsing:
- If the last character of the file is an EOF character (code 26), the EOF is treated as whitespace. Two newlines are appended (one for editors that don't put a newline at the end of the last line, and one so that the grammar doesn't have to special-case the last entry, which may not have a blank line after it).
Specification
The following will be removed from the JAR specification:
- Before parsing:
- If the last character of the file is an EOF character (code 26), the EOF is treated as whitespace. Two newlines are appended (one for editors that don't put a newline at the end of the last line, and one so that the grammar doesn't have to special-case the last entry, which may not have a blank line after it).
- csr of
-
JDK-8233721 Update JAR spec regarding when the last character is an EOF in a Manfiest
-
- Closed
-