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 5 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, some plugins use ISO-8859-1 as default output encoding (maven-site-plugin, maven-jxr-plugin), others UTF-8 (cobertura-maven-plugin), or even platform encoding (maven-javadoc-plugin).

Proposed unified default value: UTF-8, which must be supported by every JVM (see java.nio.Charset) and will work for characters in any language in the world.

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.

Plugins to Modify

Affected Apache plugins:

  • maven-site-plugin: MSITE-224
  • maven-javadoc-plugin
  • maven-jxr-plugin

Affected Codehaus plugins:

  • cobertura-maven-plugin
  • No labels