[
https://jira.codehaus.org/browse/MSITE-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=359617#comment-359617
]
Herve Boutemy commented on MSITE-326:
-------------------------------------
problem with license was a real bug: nothing was taken into account
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
notice we're probably wasting time discussing this issue, since our warnings
for not setting {{project.build.sourceEncoding}} property has led everybody to
define the property
we should probably close this issue as "won't fix": time has shown nobody cares
because nobody is hit by this little discrepency between default Doxia source
and java source encodings
> 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)
