[
https://issues.apache.org/jira/browse/IGNITE-17930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17627748#comment-17627748
]
Aleksandr commented on IGNITE-17930:
------------------------------------
The standard approach to generate javadoc for Gradle projects is `javadoc` task
that is provided by the java plugin. Now this task cannot be applied to the
sources because it has multiple failures caused by the linter. Fixing this
might introduce a lot of changes into the source code. Merging those changes
into beta1 branch might be difficult now. But there is an option that could
disable the linter.
Another issue with this plugin is that it could not generate aggregated javadoc
for multiple Gradle project. For this purpose, the
`io.freefair.aggregate-javadoc` could be used. But in this case, we cannot
disable the linter because of the bug in this plugin.
I would suggest using the existing maven javadoc generation task for beta1,
fixing all linter issues in the main branch, and after that using aggregated
javadoc task provided by gradle.
> Add javadoc plugin to gradle build
> ----------------------------------
>
> Key: IGNITE-17930
> URL: https://issues.apache.org/jira/browse/IGNITE-17930
> Project: Ignite
> Issue Type: Task
> Components: build
> Reporter: Aleksandr
> Assignee: Aleksandr
> Priority: Major
> Labels: ignite-3
>
> Maven build allows us to generate Javadoc from sources but Gradle does not.
> We have to add Javadoc generation task to the Gradle build and adjust
> DEVNOTES.md.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
