[
https://jira.codehaus.org/browse/MSHARED-346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=352750#comment-352750
]
Herve Boutemy edited comment on MSHARED-346 at 9/14/14 3:59 PM:
----------------------------------------------------------------
wrong
or more precisely: in this comit, this is done exactly as done previously =
UTF-8
just fixing the fact that the encoding was not defined as property
see MSHARED-348 for the enhancement you expect
was (Author: hboutemy):
wrong
> missing properties usually set by m-site-p (outputEncoding, ...)
> ----------------------------------------------------------------
>
> Key: MSHARED-346
> URL: https://jira.codehaus.org/browse/MSHARED-346
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-reporting-impl
> Affects Versions: maven-reporting-impl-2.2
> Reporter: Herve Boutemy
> Assignee: Herve Boutemy
> Fix For: maven-reporting-impl-2.3
>
>
> 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 reports are invoked directly as goals, without m-site-p, these
> properties are not set
> this leads to wrong HTML like reported in MCHECKSTYLE-126 because
> outputEncoding is not defined, for example
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
