[ https://jira.codehaus.org/browse/MCHECKSTYLE-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=352450#comment-352450 ]
Herve Boutemy commented on MCHECKSTYLE-126: ------------------------------------------- see http://maven.apache.org/doxia/doxia-sitetools/doxia-site-renderer/ bq. When doxia-site-renderer is used by maven-site-plugin, the following template properties are defined: when using checkstyle:checkstyle, there is no m-site-p, so no outputEncoding parameter I suppose I'll have to update reporting-impl > Generated HTML page contains "charset=${outputEncoding}" > -------------------------------------------------------- > > Key: MCHECKSTYLE-126 > URL: https://jira.codehaus.org/browse/MCHECKSTYLE-126 > Project: Maven Checkstyle Plugin > Issue Type: Bug > Affects Versions: 2.4 > Environment: Maven 2.2.1 > JDK 1.6.0_17 > Windows XP Professional SP2 (German version) > Reporter: Stephan Vollmer > Priority: Minor > Fix For: 2.13 > > Attachments: checkstyle.html > > > Hi, > when I generate a Checkstyle report with the command {{mvn > checkstyle:checkstyle}}, the resulting HTML file > {{target/site/checkstyle.html}} contains the literal string > {{charset=$\{outputEncoding\}}}. Instead, the variable should be substituted > with the actual encoding, i. e. UTF-8. I attached the resulting HTML file to > this issue. > When the Checkstyle plugin is invoked during site generation (with {{mvn > site}}) the encoding is set correctly. > This issue is visible when the checkstyle report is created in german and the > german special characters aren't rendered correctly. > Here is the relevant HTML fragment: > {code:xml} > <html xmlns="http://www.w3.org/1999/xhtml"> > <head> > <meta http-equiv="Content-Type" content="text/html; > charset=${outputEncoding}" /> > <title>Checkstyle Ergebnisse</title> > {code} > Thanks! > Stephan -- This message was sent by Atlassian JIRA (v6.1.6#6162)