[
https://jira.codehaus.org/browse/MSITE-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=359615#comment-359615
]
Michael Osipov edited comment on MSITE-326 at 12/24/14 8:08 AM:
----------------------------------------------------------------
This isn't the only spot for that. Several other components do not use platform
encoding when the input encoding is not set. You maybe remember
{{licenseEncoding}}. Why don't we create an umbrella ticket and gather all open
spots as several tickets underneath?
was (Author: michael-o):
This isn't the only spot for that. Several other components do not use platform
encoding when the input encoding is set. You maybe remember
{{licenseEncoding}}. Why don't we create an umbrella ticket and gather all open
spots as several tickets unterneath?
> 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)
