[CASSANDRA-14154] `ant javadoc` task broken due to UTF-8 characters in multiple source files

• Type: Bug
• Status: Resolved
• Priority: Low
• Resolution: Fixed
• Fix Version/s: 3.0.16, 3.11.2, 4.0-alpha1, 4.0
• Component/s: Build

Environment

Built on OpenSUSE Tumbleweed. I used the following java packages when building:

titan% rpm -qa | grep java
javapackages-local-4.7.0+git20170331.ef4057e7-1.5.x86_64
java-1_8_0-openjdk-devel-1.8.0.151-1.3.x86_64
python3-javapackages-4.7.0+git20170331.ef4057e7-1.5.x86_64
java-1_8_0-openjdk-headless-1.8.0.151-1.3.x86_64
timezone-java-2017c-1.3.noarch
java-1_8_0-openjdk-1.8.0.151-1.3.x86_64
libjavascriptcoregtk-1_0-0-2.4.11-7.6.x86_64
libjavascriptcoregtk-4_0-18-2.18.4-1.1.x86_64
javapackages-tools-4.7.0+git20170331.ef4057e7-1.5.x86_64

• Severity: Low
• Since Version: 3.11.1
• Assignee: Johannes Grassler
• Reporter: Johannes Grassler

Authors

Johannes Grassler

Reviewers

Jason Brown

• Created: 08/Jan/18 14:29
• Updated: 15/May/20 08:00
• Resolved: 10/Jan/18 13:18

Description

Several source files contain UTF-8 characters in String literals. When building the javadoc target with ant (ant javadoc), these will trip up javadoc, which defaults to ASCII encoding. See the build.log for what I did and the resulting output.

I created a patch that will fix the problem (javadoc-encoding.patch), which is attached.

I encountered this problem in 3.11.1, but I haven't checked whether other versions are affected as well.