Jenkins should create xml 1.1 output in order to support control characters that are illegal in xml 1.0

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      The current implementation of XmlFile.java emits an XML 1.0 header, which breaks things like Move/Copy/Promote if the user has included any characters that are illegal in XML 1.0 (such as Control-XX, etc) in their jobs.
      XStream, which is used for serialization/deserialization, deals with XML fragments, and doesn't have an issue reading/writing this non well-formed XML. Changing XmlFile.java so that it creates xml 1.1  here will allow jenkins config files to support these special characters. This also requires updating the underlying XML Pull Parser being used by XStream to something that support XML v1.1

        1. image-2018-08-30-17-20-59-194.png
          image-2018-08-30-17-20-59-194.png
          30 kB

            Assignee:
            mike cirioli
            Reporter:
            mike cirioli
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: