[
https://issues.apache.org/jira/browse/HIVE-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12652343#action_12652343
]
Ashish Thusoo commented on HIVE-81:
-----------------------------------
We talked about this a bit more. Considering that forrest is used by hadoop, we
are fine with following the same route though the advantages of generating
documents in the wiki style, that are available through doxia and maven are
also quite neat. As Zheng mentions, we can address that later, though my guess
is that it will be difficult to make a case to switch to another CMS for the
other subprojects. Anyway, we do not need to reinvent the wheel here so I am
fine with using forrest.
Will take a look at this in the afternoon today and send in my comments.
Preliminarily, I think we should not check in generated code (which I think
this patch is doing) and instead just check in the basic sources. Otherwise, we
will have the same problem that Doug mentioned in a separate thread about small
doc changes generating huge checkins and overwhelming the commit mails and svn
etc...
Can you make the necessary changes so that the docs are created in the build
directory (maybe build/docs and build/site).
Thanks...
> Make forrest docs for Hive web site along the lines of
> http://hadoop.apache.org/core/
> -------------------------------------------------------------------------------------
>
> Key: HIVE-81
> URL: https://issues.apache.org/jira/browse/HIVE-81
> Project: Hadoop Hive
> Issue Type: New Feature
> Components: Documentation
> Reporter: Jeff Hammerbacher
> Attachments: HIVE-81.patch
>
>
> Hive should ship with documentation, like Hadoop, instead of using the wiki
> as the official documentation repository. To get there, we'll need a set of
> xml files to grind through forrest, if we want to reuse the same mechanisms
> as the other sites.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
