[
https://jira.codehaus.org/browse/MSITE-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=359609#comment-359609
]
Herve Boutemy commented on MSITE-326:
-------------------------------------
implemented, no: see
http://maven.apache.org/plugins/maven-site-plugin/xref/org/apache/maven/plugins/site/AbstractSiteMojo.html#L117
{code:java}protected String getInputEncoding()
{
return ( inputEncoding == null ) ? ReaderFactory.ISO_8859_1 : inputEncoding;
}{code}
notice this is not well documented: we probably could improve [inputEncoding
parameter
documentation|http://maven.apache.org/plugins/maven-site-plugin/site-mojo.html#inputEncoding]
to tell what is used when no {{project.build.sourceEncoding}} is defined
but obsolete, probably since nobody asked for the feature: no setting
{{project.build.sourceEncoding}} cause WARNINGs that help people configure
it... :)
> Make file encoding default to platform encoding
> -----------------------------------------------
>
> Key: MSITE-326
> URL: https://jira.codehaus.org/browse/MSITE-326
> Project: Maven Site Plugin
> Issue Type: Wish
> Components: encoding
> Affects Versions: 2.0-beta-5, 2.0-beta-6
> Reporter: Herve Boutemy
>
> According to the [user poll about the default file
> encoding|http://www.nabble.com/-POLL--Default-Value-for-File-Encoding-td16958386.html],
> the inputEncoding should default to the platform default encoding instead of
> Latin-1. Since that would be a breaking change it is left to users to vote
> for this issue if they feelt it's worth to have it like that.
> If the change is made, we should have the plugin output a warning when using
> the platform encoding.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
