[
https://issues.apache.org/jira/browse/MJAVADOC-614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16921653#comment-16921653
]
Robert Scholte commented on MJAVADOC-614:
-----------------------------------------
Change is confirmed on the
[javadoc-dev-list|https://mail.openjdk.java.net/pipermail/javadoc-dev/2019-September/001133.html]:
bq. It was not intentional to change to use UTF-8 for @-files in JDK 9, 10, 11:
it was the result of the default used by Files.newBuffereredReader when no
Charset argument was provided. The fix, in JDK-8214514, was to explicitly
specify Charset.defaultSet() as the second argument of Files.newBufferedReader.
> "No source files for package" in a directory with accent characters
> -------------------------------------------------------------------
>
> Key: MJAVADOC-614
> URL: https://issues.apache.org/jira/browse/MJAVADOC-614
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
> Affects Versions: 3.1.0, 3.1.1
> Environment: Operating System: Windows 7
> Java: OracleJDK12
> Maven: 3.6.1
> Reporter: Alexis Jehan
> Priority: Critical
> Attachments: options, options(3.0.1), packages, packages(3.0.1)
>
>
>
> Executing "mvn clean javadoc:javadoc" in the "D:\é\foo" produces the
> following error:
> {quote}[ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-javadoc-plugin:3.1.1:javadoc (default-cli) on
> project foo: An error has occurred in Javadoc report generation:
> [ERROR] Exit code: 2 - javadoc: error - No source files for package foo.bar
> [ERROR]
> [ERROR] Command line was: "C:\Program Files\Java\jdk-12\bin\javadoc.exe"
> @options @packages
> [ERROR]
> [ERROR] Refer to the generated Javadoc files in
> 'D:\é\foo\target\site\apidocs' dir.
> {quote}
> In a directory named "D:\e\foo", the same command does not produce any error.
> The bug does not affect Apache Maven Javadoc Plugin 3.0.1.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
