[
https://issues.apache.org/jira/browse/HDFS-12734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238467#comment-16238467
]
Allen Wittenauer commented on HDFS-12734:
-----------------------------------------
bq. from the comments on that thread, it looks to me that is the direction we
want to go.
It doesn't mean anything until it's been committed. I can point to lots and
lots of issues where this is true... and years later, still open.
bq. If you have a hugo based site, how do you want to generate it?
Why does it need to be hugo-based? We've already got all of
node/npm/bower/yarn sitting there due to the overly heavy yarn-ui.
bq. by asking people to install the build tool each time?
What do you think happens for people who aren't using Docker? Or, what about
platforms where Go doesn't work at all?
In my mind, there is a very big difference between what gets posted on
hadoop.apache.org and the requirements that we place on end users trying to
build Hadoop. Every additional dependency just makes it that much harder.
> Ozone: generate version specific documentation during the build
> ---------------------------------------------------------------
>
> Key: HDFS-12734
> URL: https://issues.apache.org/jira/browse/HDFS-12734
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ozone
> Affects Versions: HDFS-7240
> Reporter: Elek, Marton
> Assignee: Elek, Marton
> Priority: Major
> Attachments: HDFS-12734-HDFS-7240.001.patch
>
>
> HDFS-12664 susggested a new way to include documentation in the KSM web ui.
> This patch modifies the build lifecycle to automatically generate the
> documentation *if* hugo is on the PATH. If hugo is not there the
> documentation won't be generated and it won't be displayed (see HDFS-12661)
> To test: Apply this patch on top of HDFS-12664 do a full build and check the
> KSM webui.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
