Robert,
One final comment: while this thread has been in the context of javadoc,
the code in question is part of javac, and so the changes in behavior
apply to the use of @files with both javac and javadoc commands.
-- Jon
On 09/03/2019 11:43 AM, Robert Scholte wrote:
Jon,
this is exactly
Jon,
this is exactly the information I was looking for.
Based on this we can safely fix it in our plugin.
thanks,
Robert
On Tue, 03 Sep 2019 20:28:43 +0200, Jonathan Gibbons
wrote:
Robert,
I may have misunderstood your original question; I thought you were
talking about the encoding u
Alexis,
I think this issue is the one being discussed in the separate thread
with Robert Scholte, with the subject line: "No source files for
package" in a directory with accent characters
-- Jon
On 09/03/2019 10:44 AM, Jonathan Gibbons wrote:
Alexis,
There are no open issues in this are
Robert,
I may have misunderstood your original question; I thought you were
talking about the encoding used for the files generated by javadoc
(which is an area where we've had problems in the past) ... but it seems
like you may be referring to the file encoding used for any @-files used
on
Hi Jon,
It was not my analysis, I'm just the messenger.
The -docencoding is UTF-8 by default
The -charset uses the value of docencoding by default.
The issue seems to be related to the encoding of the @options argument we
pass to the javadoc tool.
Here's the thing we do:
/* default
Alexis,
There are no open issues in this area, and so there are currently no
plans to change anything.
If you are seeing issues, can you provide more details, including the
values of options like -docencoding, -charset, and the default charset
you are using, and what encoding you expected to
On 09/03/2019 10:06 AM, Robert Scholte wrote:
This is the title of an issue reported for the Maven plugin[1]
Based on the analysis some involved developers came to the conclusion
that the outputFileEncoding for Java 9, 10 and 11 was changed to
UTF-8, but since Java 12 it behaves again like
Is it planned that the current behavior with the default charset on Windows
will be changed in a future release?
The behavior has changed from Java 9 to Java 11, and since Java 12 to Java 14
it acts back like Java 8.
Thank you in advance.
Related issue on Maven Javadoc plugin:
https://issues.a
This is the title of an issue reported for the Maven plugin[1]
Based on the analysis some involved developers came to the conclusion that
the outputFileEncoding for Java 9, 10 and 11 was changed to UTF-8, but
since Java 12 it behaves again like Java 8.
Can this be confirmed with the related
