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 4 Next »

Currently, the character encoding for source files needs to be configured individually for each and every plugin that processes source files.

Life would become easier if there was a dedicated POM element like ${} which could be used to specify the encoding once per entire project.

Affected Apache plugins:

  • maven-compiler-plugin
  • maven-javadoc-plugin
  • maven-resources-plugin
  • maven-plugin-plugin
  • maven-jxr-plugin
  • maven-pmd-plugin
  • maven-changes-plugin

Affected Mojo plugins:

  • taglist-maven-plugin

Please see [0] for the related thread from the mailing list, and [1] for some further descriptions.



  • No labels