[
https://jira.codehaus.org/browse/MSITE-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=359656#comment-359656
]
Michael Osipov commented on MSITE-326:
--------------------------------------
bq. default encoding for Doxia source content is taken into account: for
compatibility reason, its defautl value is just not the same as for java source
code
Don't we have the liberty to make stuff predictable? If someone sets input
encoding, I'd presume it would apply to all input in the project, not just Java
files.
At long last, I would simply move this to a *TASK* and move it to 3.5.
> 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)
