-
Enhancement
-
Resolution: Won't Fix
-
P4
-
None
-
8u25, 9
-
x86
-
linux
A DESCRIPTION OF THE REQUEST :
When generation a MANIFEST.MF file for a jar file, java.util.jar.Manifest and java.util.Attributes have hard coded "\n\r" line ends. They should use system line end style (System.getProperty("line.separator")) for consistency with the rest of files generated in the system.
JUSTIFICATION :
The JAR Manfiest spec ( https://docs.oracle.com/javase/7/docs/technotes/guides/jar/jar.html#JAR_Manifest ) states that you can use CR LF | LF | CR (not followed by LF) as new line characters but current implementation hard codes CR LF and you can't change behavior.
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
Generated MANIFEST.MF line ends consistent with the rest of files in the system.
ACTUAL -
Generated MANIFEST.MF line ends always with Windows line end style (CR LF).
When generation a MANIFEST.MF file for a jar file, java.util.jar.Manifest and java.util.Attributes have hard coded "\n\r" line ends. They should use system line end style (System.getProperty("line.separator")) for consistency with the rest of files generated in the system.
JUSTIFICATION :
The JAR Manfiest spec ( https://docs.oracle.com/javase/7/docs/technotes/guides/jar/jar.html#JAR_Manifest ) states that you can use CR LF | LF | CR (not followed by LF) as new line characters but current implementation hard codes CR LF and you can't change behavior.
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
Generated MANIFEST.MF line ends consistent with the rest of files in the system.
ACTUAL -
Generated MANIFEST.MF line ends always with Windows line end style (CR LF).