[
https://issues.apache.org/jira/browse/MJAVADOC-165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17957541#comment-17957541
]
Olivier Lamy commented on MJAVADOC-165:
---------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-javadoc-plugin#1013|https://github.com/apache/maven-javadoc-plugin/issues/1013].
> Provide specific default value for "encoding" parameter
> -------------------------------------------------------
>
> Key: MJAVADOC-165
> URL: https://issues.apache.org/jira/browse/MJAVADOC-165
> Project: Maven Javadoc Plugin (Moved to GitHub Issues)
> Issue Type: Improvement
> Affects Versions: 2.3
> Reporter: Benjamin Bentmann
> Assignee: Siveton Vincent
> Priority: Minor
> Fix For: 2.4
>
> Attachments: source-encoding.patch
>
>
> As stated in the [javadoc
> doc|http://java.sun.com/javase/6/docs/technotes/tools/windows/javadoc.html#encoding],
> the parameter "encoding" defaults to the platform's default encoding if not
> specified. This might be a convenient feature when running javadoc directly
> from the console prompt (less typing) but I consider this harmful for an
> automated build. The platform's default encoding might easily differ between
> machines/developers, causing unreliable build output.
> Please see the related issue MCOMPILER-63 for further explanations.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
