[MNG-3608] Reporting Encoding Configuration: ${project.reporting.outputEncoding}
- Dominant language
- Java
- Stars
- 5.3k
- Forks
- 3.1k
- Avg merge
- 20h 42m
- Merged PRs (30d)
- 297
Description
**[Hervé Boutemy](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=hboutemy)** opened **[MNG-3608](https://issues.apache.org/jira/browse/MNG-3608?redirect=false)** and commented
see [Reporting Encoding Configuration proposal](https://cwiki.apache.org/confluence/display/MAVENOLD/Reporting+Encoding+Configuration)
---
This issue is a sub-task of [MNG-2216](https://issues.apache.org/jira/browse/MNG-2216)
**Issue Links:**
- [MPMD-83](https://issues.apache.org/jira/browse/MPMD-83) Use proper file encoding for Non-HTML reports
- [MJAVADOC-206](https://issues.apache.org/jira/browse/MJAVADOC-206) use ${project.reporting.outputEncoding} as default value for "docencoding" and "charset" parameter and default to UTF-8
- [MSITE-340](https://issues.apache.org/jira/browse/MSITE-340) use ${project.reporting.outputEncoding} as default value for "outputEncoding" parameter and default to UTF-8
- [MSITE-326](https://issues.apache.org/jira/browse/MSITE-326) Make input source file encoding default to platform encoding
**Remote Links:**
- [Page
](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=65875544)
Contributor guide
Research direction
Start with the linked Reporting Encoding Configuration proposal and the MNG-2216 parent issue, then review the linked MPMD-83, MJAVADOC-206, MSITE-340, and MSITE-326 issues. Done means the proposed reporting encoding configuration is implemented consistently across the affected reporting integrations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100