Maven
  1. Maven
  2. MNG-2216

Add default encodings section to POM

    Details

      Description

      Look at the attached example POM.

      Do you see many duplicate configuration properties ('UTF-8') in it? and the names of properties are very inconsistent.

      It would be great if:

      1) Add a global section which specifies default encodings:

      <defaultEncodings>
          <!-- Default: UTF-8 -->
          <inputEncoding>UTF-8</inputEncoding>
          <!-- Will be the same with inputEncoding if not specified. -->
          <outputEncoding>UTF-8</outputEncoding>
      </defaultEncodings>

      2) Make encoding properties in all plugins to be consistent and deprecate old properties. The default values could be:

      inputEncoding = ${pom.encoding.input}
      outputEncoding = ${pom.encoding.output}

      so users can override the default settings easily.

        Issue Links

          Activity

          Trustin Lee created issue -
          Carlos Sanchez made changes -
          Field Original Value New Value
          Link This issue is related to MNG-2254 [ MNG-2254 ]
          John Casey made changes -
          Fix Version/s 2.1 [ 11704 ]
          Jason van Zyl made changes -
          Fix Version/s 2.1 [ 11704 ]
          Fix Version/s 2.1.x [ 13142 ]
          Jason van Zyl made changes -
          Component/s POM [ 11339 ]
          Component/s POM::Encoding [ 12860 ]
          Jason van Zyl made changes -
          Fix Version/s 2.1.x [ 13142 ]
          Fix Version/s 2.0.8 [ 13139 ]
          Carlos Sanchez made changes -
          Link This issue is related to MNG-2932 [ MNG-2932 ]
          Hide
          Carlos Sanchez added a comment -

          if this involves a change to the pom schema has to be postponed to 2.1

          Show
          Carlos Sanchez added a comment - if this involves a change to the pom schema has to be postponed to 2.1
          Hide
          Brian E. Fox added a comment -

          Carlos is right, model changes need to be bumped to 2.1

          Show
          Brian E. Fox added a comment - Carlos is right, model changes need to be bumped to 2.1
          Brian Fox made changes -
          Fix Version/s 2.0.8 [ 13139 ]
          Fix Version/s 2.1 [ 13142 ]
          Hide
          Benjamin Bentmann added a comment -
          Show
          Benjamin Bentmann added a comment - There exists a related user proposal at http://docs.codehaus.org/display/MAVENUSER/POM+Element+for+Source+File+Encoding .
          Hervé Boutemy made changes -
          Link This issue relates to MCOMPILER-70 [ MCOMPILER-70 ]
          Hervé Boutemy made changes -
          Link This issue relates to MJAVADOC-182 [ MJAVADOC-182 ]
          Hervé Boutemy made changes -
          Link This issue relates to JXR-60 [ JXR-60 ]
          Hervé Boutemy made changes -
          Link This issue relates to MPMD-76 [ MPMD-76 ]
          Hervé Boutemy made changes -
          Link This issue relates to MRESOURCES-57 [ MRESOURCES-57 ]
          Hervé Boutemy made changes -
          Link This issue relates to PLX-371 [ PLX-371 ]
          Hervé Boutemy made changes -
          Link This issue relates to MCHANGES-71 [ MCHANGES-71 ]
          Hervé Boutemy made changes -
          Link This issue relates to MCHECKSTYLE-95 [ MCHECKSTYLE-95 ]
          Hervé Boutemy made changes -
          Link This issue relates to MINVOKER-30 [ MINVOKER-30 ]
          Hervé Boutemy made changes -
          Link This issue relates to MPLUGIN-100 [ MPLUGIN-100 ]
          Hervé Boutemy made changes -
          Link This issue relates to MPLUGIN-101 [ MPLUGIN-101 ]
          Hervé Boutemy made changes -
          Link This issue relates to MSITE-314 [ MSITE-314 ]
          Hervé Boutemy made changes -
          Link This issue relates to MODELLO-109 [ MODELLO-109 ]
          Hervé Boutemy made changes -
          Link This issue relates to MTAGLIST-27 [ MTAGLIST-27 ]
          Hervé Boutemy made changes -
          Link This issue relates to MJNCSS-31 [ MJNCSS-31 ]
          Hervé Boutemy made changes -
          Link This issue relates to MOJO-1138 [ MOJO-1138 ]
          Jason van Zyl made changes -
          Fix Version/s 3.x [ 13145 ]
          Fix Version/s 3.0 [ 13142 ]
          Benjamin Bentmann made changes -
          Link This issue relates to MNG-4149 [ MNG-4149 ]
          Jason van Zyl made changes -
          Fix Version/s 3.x [ 13145 ]
          Fix Version/s 3.1.alpha1 [ 16093 ]
          Brett Porter made changes -
          Fix Version/s 3.1.alpha1 [ 16093 ]
          Fix Version/s 3.1 [ 15565 ]
          stephenconnolly made changes -
          Fix Version/s 3.2 [ 15565 ]
          Fix Version/s Issues to be reviewed for 4.x [ 19871 ]
          Hervé Boutemy made changes -
          Description Look at the attached example POM.

          Do you see many duplicate configuration properties ('UTF-8') in it? and the names of properties are very inconsistent.

          It would be great if:

          1) Add a global section which specifies default encodings:

          <defaultEncodings>
              <!-- Default: UTF-8 -->
              <inputEncoding>UTF-8</inputEncoding>
              <!-- Will be the same with inputEncoding if not specified. -->
              <outputEncoding>UTF-8</outputEncoding>
          </defaultEncodings>

          2) Make encoding properties in all plugins to be consistent and deprecate old properties. The default values could be:

          inputEncoding = ${pom.encoding.input}
          outputEncoding = ${pom.encoding.output}

          so users can override the default settings easily.
          Look at the attached example POM.

          Do you see many duplicate configuration properties ('UTF-8') in it? and the names of properties are very inconsistent.

          It would be great if:

          1) Add a global section which specifies default encodings:

          {code:xml}<defaultEncodings>
              <!-- Default: UTF-8 -->
              <inputEncoding>UTF-8</inputEncoding>
              <!-- Will be the same with inputEncoding if not specified. -->
              <outputEncoding>UTF-8</outputEncoding>
          </defaultEncodings>{code}

          2) Make encoding properties in all plugins to be consistent and deprecate old properties. The default values could be:

          {noformat]inputEncoding = ${pom.encoding.input}
          outputEncoding = ${pom.encoding.output}{noformat]

          so users can override the default settings easily.
          Hervé Boutemy made changes -
          Description Look at the attached example POM.

          Do you see many duplicate configuration properties ('UTF-8') in it? and the names of properties are very inconsistent.

          It would be great if:

          1) Add a global section which specifies default encodings:

          {code:xml}<defaultEncodings>
              <!-- Default: UTF-8 -->
              <inputEncoding>UTF-8</inputEncoding>
              <!-- Will be the same with inputEncoding if not specified. -->
              <outputEncoding>UTF-8</outputEncoding>
          </defaultEncodings>{code}

          2) Make encoding properties in all plugins to be consistent and deprecate old properties. The default values could be:

          {noformat]inputEncoding = ${pom.encoding.input}
          outputEncoding = ${pom.encoding.output}{noformat]

          so users can override the default settings easily.
          Look at the attached example POM.

          Do you see many duplicate configuration properties ('UTF-8') in it? and the names of properties are very inconsistent.

          It would be great if:

          1) Add a global section which specifies default encodings:

          {code:xml}<defaultEncodings>
              <!-- Default: UTF-8 -->
              <inputEncoding>UTF-8</inputEncoding>
              <!-- Will be the same with inputEncoding if not specified. -->
              <outputEncoding>UTF-8</outputEncoding>
          </defaultEncodings>{code}

          2) Make encoding properties in all plugins to be consistent and deprecate old properties. The default values could be:

          {noformat}inputEncoding = $\{pom.encoding.input}
          outputEncoding = $\{pom.encoding.output}{noformat}

          so users can override the default settings easily.
          Hervé Boutemy made changes -
          Description Look at the attached example POM.

          Do you see many duplicate configuration properties ('UTF-8') in it? and the names of properties are very inconsistent.

          It would be great if:

          1) Add a global section which specifies default encodings:

          {code:xml}<defaultEncodings>
              <!-- Default: UTF-8 -->
              <inputEncoding>UTF-8</inputEncoding>
              <!-- Will be the same with inputEncoding if not specified. -->
              <outputEncoding>UTF-8</outputEncoding>
          </defaultEncodings>{code}

          2) Make encoding properties in all plugins to be consistent and deprecate old properties. The default values could be:

          {noformat}inputEncoding = $\{pom.encoding.input}
          outputEncoding = $\{pom.encoding.output}{noformat}

          so users can override the default settings easily.
          Look at the attached example POM.

          Do you see many duplicate configuration properties ('UTF-8') in it? and the names of properties are very inconsistent.

          It would be great if:

          1) Add a global section which specifies default encodings:

          {code:xml}<defaultEncodings>
              <!-- Default: UTF-8 -->
              <inputEncoding>UTF-8</inputEncoding>
              <!-- Will be the same with inputEncoding if not specified. -->
              <outputEncoding>UTF-8</outputEncoding>
          </defaultEncodings>{code}

          2) Make encoding properties in all plugins to be consistent and deprecate old properties. The default values could be:

          {noformat}inputEncoding = ${pom.encoding.input}
          outputEncoding = ${pom.encoding.output}{noformat}

          so users can override the default settings easily.
          Robert Scholte made changes -
          Component/s FDPFC [ 16560 ]
          Mark Thomas made changes -
          Project Import Sun Apr 05 08:49:45 UTC 2015 [ 1428223785911 ]
          Mark Thomas made changes -
          Link This issue relates to MCHANGES-71 [ MCHANGES-71 ]
          Mark Thomas made changes -
          Link This issue relates to MCHECKSTYLE-95 [ MCHECKSTYLE-95 ]
          Mark Thomas made changes -
          Link This issue relates to MCOMPILER-70 [ MCOMPILER-70 ]
          Mark Thomas made changes -
          Link This issue relates to MINVOKER-30 [ MINVOKER-30 ]
          Mark Thomas made changes -
          Link This issue relates to JXR-60 [ JXR-60 ]
          Mark Thomas made changes -
          Link This issue relates to MJAVADOC-182 [ MJAVADOC-182 ]
          Mark Thomas made changes -
          Link This issue relates to MPMD-76 [ MPMD-76 ]
          Mark Thomas made changes -
          Link This issue relates to MPLUGIN-100 [ MPLUGIN-100 ]
          Mark Thomas made changes -
          Link This issue relates to MPLUGIN-101 [ MPLUGIN-101 ]
          Mark Thomas made changes -
          Link This issue relates to MRESOURCES-57 [ MRESOURCES-57 ]
          Mark Thomas made changes -
          Link This issue relates to MSITE-314 [ MSITE-314 ]
          Mark Thomas made changes -
          Workflow jira [ 12712869 ] Default workflow, editable Closed status [ 12755663 ]
          Mark Thomas made changes -
          Project Import Sun Apr 05 21:45:26 UTC 2015 [ 1428270326204 ]
          Mark Thomas made changes -
          Link This issue relates to MCHANGES-71 [ MCHANGES-71 ]
          Mark Thomas made changes -
          Link This issue relates to MCHECKSTYLE-95 [ MCHECKSTYLE-95 ]
          Mark Thomas made changes -
          Link This issue relates to MCOMPILER-70 [ MCOMPILER-70 ]
          Mark Thomas made changes -
          Link This issue relates to MINVOKER-30 [ MINVOKER-30 ]
          Mark Thomas made changes -
          Link This issue relates to JXR-60 [ JXR-60 ]
          Mark Thomas made changes -
          Link This issue relates to MJAVADOC-182 [ MJAVADOC-182 ]
          Mark Thomas made changes -
          Link This issue relates to MPMD-76 [ MPMD-76 ]
          Mark Thomas made changes -
          Link This issue relates to MPLUGIN-100 [ MPLUGIN-100 ]
          Mark Thomas made changes -
          Link This issue relates to MPLUGIN-101 [ MPLUGIN-101 ]
          Mark Thomas made changes -
          Link This issue relates to MRESOURCES-57 [ MRESOURCES-57 ]
          Mark Thomas made changes -
          Link This issue relates to MSITE-314 [ MSITE-314 ]
          Mark Thomas made changes -
          Workflow jira [ 12952544 ] Default workflow, editable Closed status [ 12990415 ]

            People

            • Assignee:
              Unassigned
              Reporter:
              Trustin Lee
            • Votes:
              16 Vote for this issue
              Watchers:
              17 Start watching this issue

              Dates

              • Created:
                Updated:

                Development