Details
-
Type:
Improvement
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 2.0, 2.0.1, 2.0.2, 2.0.3
-
Fix Version/s: 3.2
-
Component/s: POM::Encoding
-
Labels:None
-
Complexity:Intermediate
-
Number of attachments :
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
- is related to
-
MNG-2932
Encoding chaos
-
- relates to
-
MNG-2254
the encoding parameter in xml declaration of POM is ignored
-
-
MNG-4149
Extend POM to support encoding parameter per (test) resource
-
-
MJNCSS-31
add an "encoding" parameter for source files and use ${project.build.sourceEncoding} as default value
-
-
MODELLO-109
add an "encoding" parameter and use ${project.build.sourceEncoding} as default value
-
-
MOJO-1138
add an "encoding" parameter for source files and use ${project.build.sourceEncoding} as default value
-
-
PLX-371
add an "encoding" parameter and use ${project.build.sourceEncoding} as default value
-
-
JXR-60
use ${project.build.sourceEncoding} as default value for "inputEncoding" parameter
-
-
MCHANGES-71
need add template encoding to announcement-generate
-
-
MCHECKSTYLE-95
Allow to configure file encoding for source files
-
-
MCOMPILER-70
use ${project.build.sourceEncoding} as default value for "encoding" parameter
-
-
MINVOKER-30
Allow to configure file encoding for verifications scripts
-
-
MJAVADOC-182
use ${project.build.sourceEncoding} as default value for "encoding" parameter
-
-
MPLUGIN-100
Allow customization of file encoding used for generated help goal
-
-
MPLUGIN-101
Allow customization of file encoding used for mojo extraction
-
-
MPMD-76
use ${project.build.sourceEncoding} as default value for "sourceEncoding" parameter
-
-
MSITE-314
use ${project.build.sourceEncoding} as default value for "inputEncoding" parameter
-
-
MRESOURCES-57
use ${project.build.sourceEncoding} as default value for "encoding" parameter
-
-
MTAGLIST-27
need a feature to set the encoding of source files.
-
| 1. | Reporting Encoding Configuration: ${project.reporting.outputEncoding} | |
|
Unassigned |