[
https://issues.apache.org/jira/browse/IGNITE-13623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17273428#comment-17273428
]
Maksim Timonin commented on IGNITE-13623:
-----------------------------------------
[~Pavlukhin] , [~alex_pl]
I've tried some ways to fix this and find that it's not easy to just move
javadoc generation to different profile or phase. There are some issues, for
example:
# Javadoc depends on ignite-tools class
org.apache.ignite.tools.javadoc.IgniteLinkTaglet. Maven requires to have a
packaged jar for ignite-tools for running javadoc profile. It's due to maven
dependency management. So we can't move all to prepare-package phase.
# If we run `mvn package -Pjavadoc` then it leads to some strange issues:
ignite-cassandra-store module fails; number of files in root javadoc directory
is bigger then after `mvn initialize -Pjavadoc` command. It's required to make
more investigation.
But I think we can do it in different way. I propose to add a profile
"skip-docs" that disables generation of docs. I've successfully implemented
this configuration. It's pretty simple and does not require changes for current
release process. Also it provides a real benefit for a build time or skipping
all docs for users or customers who need it.
If nobody have objections I will prepare a PR for that.
> Scaladoc not created during release process
> -------------------------------------------
>
> Key: IGNITE-13623
> URL: https://issues.apache.org/jira/browse/IGNITE-13623
> Project: Ignite
> Issue Type: Bug
> Components: build
> Affects Versions: 2.8, 2.9, 2.8.1
> Reporter: Aleksey Plekhanov
> Assignee: Maksim Timonin
> Priority: Blocker
>
> Scaladoc creation is broken (probably by IGNITE-11933). We have 3 release
> assemblies without scaladoc now (2.8, 2.8.1, 2.9).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
