[CASSANDRA-17712] Remove javadocs step from CI and release process

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 3.0.28, 3.11.14, 4.0.6, 4.1-beta1, 4.1
• Component/s: CI
• Bug Category: Degradation - Resource Management
• Severity: Normal
• Complexity: Low Hanging Fruit
• Discovered By: User Report
• Platform: All
• Since Version: NA

Source Control Link

https://github.com/apache/cassandra/commit/9e32c44455f5df1749b66cc66c5a3c18929b7bd2

Test and Documentation Plan

run CI

• Assignee: Brandon Williams
• Reporter: Berenguer Blasi

Authors

Brandon Williams

Reviewers

Berenguer Blasi

• Created: 23/Jun/22 05:16
• Updated: 05/Oct/22 22:22
• Resolved: 18/Aug/22 11:01

Description

Currently the javadocs step is both:

• Taking up jenkins cycles and generating a large output in CI when building artifacts
• Failing randomly on javadoc issues such as AlterTableStatement.java:135: error: text not allowed in element

Apidocs are not being bundled, uploaded or used anywhere. Hence it would be best to remove javadocs generation on every CI. Mainly removing javadoc from artifacts and mvn-install.

Issue Links

• relates to: CASSANDRA-17713 Javadocs random error