Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • None
    • Commons Parent Pom
    • None

    Description

      The parent POM should define the following properties:

      <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
      <project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>

      Attachments

        Activity

          sebb Sebb added a comment -

          URL: http://svn.apache.org/viewvc?rev=815556&view=rev
          Log:
          COMMONSSITE-43 Define encoding as iso-8859-1

          sebb Sebb added a comment - URL: http://svn.apache.org/viewvc?rev=815556&view=rev Log: COMMONSSITE-43 Define encoding as iso-8859-1
          sebb Sebb added a comment -

          Just noticed that the pom already defines

          <commons.encoding>iso-8859-1</commons.encoding>

          so iso-8859-1 might be a better default for the other encodings.

          sebb Sebb added a comment - Just noticed that the pom already defines <commons.encoding>iso-8859-1</commons.encoding> so iso-8859-1 might be a better default for the other encodings.
          sebb Sebb added a comment -

          It can always be overridden by the component POM.

          We could also set the default to ISO-8859-1 - the point is that the encoding needs to be specified to avoid problem with the filters.

          sebb Sebb added a comment - It can always be overridden by the component POM. We could also set the default to ISO-8859-1 - the point is that the encoding needs to be specified to avoid problem with the filters.
          luc Luc Maisonobe added a comment -

          This was discussed in this thread: http://markmail.org/message/5uki2wynb5ffs4mw

          At that time, all people who have contributed to the discussion agreed. However, I don't know if anybody has checked whether some files did depend on the current encoding specification which is ISO-8859-1 (latin 1). Another point is if the javadoc and the source xref generated pages do support UTF-8. I remember encoding problems in maven-generated sites some time ago.

          luc Luc Maisonobe added a comment - This was discussed in this thread: http://markmail.org/message/5uki2wynb5ffs4mw At that time, all people who have contributed to the discussion agreed. However, I don't know if anybody has checked whether some files did depend on the current encoding specification which is ISO-8859-1 (latin 1). Another point is if the javadoc and the source xref generated pages do support UTF-8. I remember encoding problems in maven-generated sites some time ago.

          People

            Unassigned Unassigned
            sebb Sebb
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: