|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
i didnt say they werent well-formed XML files. i said that they are not well-formed text files.
POSIX is a widely-accepted standard. here are the relevant POSIX definitions:
3.397 Text File
A file that contains characters organized into zero or more lines. The lines do not contain NUL characters and none can exceed {LINE_MAX} bytes in length, including the <newline> character.
3.206 Line
A sequence of zero or more non-<newline> characters plus a terminating <newline> character.
http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html
{the config.xml files do not meet this definition. they are <file>s containing a sequence of zero or more <line>s followed by one or more non-<newline> characters.}however, it is much more practically important to note that many standard, popular, extremely widely-deployed tools rely on this definition {vim, cat, and read being just a few examples}. there are no tools that i ever heard of that require special lines NOT to end in the newline character.