Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 17 Next »

Currently, the character encoding for reports output files needs to be configured individually for each and every plugin that creates new report types (i.e. don't write its content through Doxia but write directly its files to disk).

Life would become easier if there was a dedicated POM element like ${project.reporting.outputEncoding} which could be used to specify the encoding once per entire project. Every plugin could use it as default value, like it has been done with source files encoding:

Adding this element to the POM structure can only happen in Maven 2.1:

For Maven 2.0.x, the value can be defined as an equivalent property:

Thus plugins could immediately be modified to use ${project.reporting.outputEncoding} expression, whatever Maven version is used.

Default Value

Actually, default output encoding vary between plugins:

  • ISO-8859-1 for maven-site-plugin, maven-jxr-plugin and by extension every reporting plugin generating content with maven-site-plugin's template (that is the vast majority of reporting plugins),
  • UTF-8 for cobertura-maven-plugin,
  • platform encoding for maven-javadoc-plugin.

Unifying default value will lead to a change for plugins previously using another default value. This shouldn't cause much harm since reports are mainly read by humans through their web browser.

There are 2 options discussed for the unified default value.

Option 1: UTF-8

Proposed unified default value: UTF-8, which will ensure that default value is appropriate for characters in any language in the world. The change for plugins previously using another default value shouldn't cause much harm, since reports are mainly read by humans through their web browser.

A check has to be coded in every plugin with the default value:

This default value can be coded in POM model too for 2.1.x (default value of the encoding attribute) and in super-pom in Maven 2.0.x. But this change is only for clarity since without it, the previous check coded in every plugin will transform null value to the chosen default value.

Option 2: source encoding

Proposed unified default value: source encoding, .

A check has to be coded in every plugin with the default value:

Source encoding should be calculated as defined in Source File Encodingproposal, and added as a parameter in the plugin if necessary.

Plugins to Modify

The vast majority of reporting plugins don't need any change since they are using Doxia and maven-site-plugin's template: the encoding configuration will silently be inherited from maven-site-plugin. 

Affected Apache plugins:

  • maven-changelog-plugin
  • maven-javadoc-plugin: MJAVADOC-206, done in 2.5-SNAPSHOT
  • maven-jxr-plugin
  • maven-pmd-plugin: MPMD-83
  • maven-site-plugin: MSITE-340

Affected Codehaus plugins:

  • cobertura-maven-plugin

References

Please see [0] for the related thread from the mailing list and [1] for the corresponding feature request in JIRA.

[0] next step for encoding support: reporting output files

[1] MNG-3608

  • No labels