[
https://issues.apache.org/jira/browse/CASSANDRA-18717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17757479#comment-17757479
]
Maxim Muzafarov commented on CASSANDRA-18717:
---------------------------------------------
Since the CEPs are related to the new piece of code, I think the amount of
conflict with javadoc will be extremely minimal. Such a technique also
increases the amount of work for the patches that are waiting for the CEPs to
land. The more patches waiting, the more extra work for we would have to do for
no reason.
My suggestion is to go directly to the CEPs (I assume they are all publicly
available) and fix the javadocs there and merge the current patch. I can do
that.
OR
Merge it as is without making the CI fail, as we probably need to ship
compilable javadocs in an earlier aplha version (not only because it is
difficult to maintain such kinds of patches over a long period of time :-) )
Mick outlined the list of CEPs that are waiting to be completed soon, no a big
deal to check all and fix them all.
WDYT?
https://lists.apache.org/thread/znm04w0fc5076ccdo8p3t3ghjox863zz
> Fix errors or remove ant javadoc task
> -------------------------------------
>
> Key: CASSANDRA-18717
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18717
> Project: Cassandra
> Issue Type: Bug
> Components: Documentation/Javadoc
> Reporter: Ekaterina Dimitrova
> Assignee: Maxim Muzafarov
> Priority: Normal
> Fix For: 5.0.x, 5.x
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> As discussed on CASSANDRA-17687, the javadoc task completes successfully, but
> there are errors that deserve to be fixed if we keep the task around.
> If we do not plan to use it, we should remove it and reduce the clutter.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
