[jira] [Commented] (HADOOP-8427) Convert Forrest docs to APT

["Tom White (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HADOOP-8427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13492311#comment-13492311 ] 

Tom White commented on HADOOP-8427:
-----------------------------------

Andy, this looks good so far. I generated the site with {{mvn site; mvn site:stage -DstagingDirectory=/tmp/hadoop-site}} and the converted files looked OK. The navigation is not wired up yet though - my patch in HADOOP-8860 sets up the nav correctly so it would help if committed that one first. Does that patch look OK to you? 

Going through the other files in Common that have not been migrated, cluster_setup.xml and single_node_setup.xml are already in hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/apt so can be left, but deployment_layout.xml, index.xml, native_libraries.xml, service_level_auth.xml, and Superusers.xml should all be migrated. They will need to be reviewed and updated, but this can be done separately as Nicholas suggested.

                
> Convert Forrest docs to APT
> ---------------------------
>
>                 Key: HADOOP-8427
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8427
>             Project: Hadoop Common
>          Issue Type: Task
>          Components: documentation
>    Affects Versions: 2.0.0-alpha
>            Reporter: Eli Collins
>            Assignee: Andy Isaacson
>              Labels: newbie
>         Attachments: hadoop8427-1.txt, hadoop8427-3.txt, hadoop8427.txt
>
>
> Some of the forrest docs content in src/docs/src/documentation/content/xdocs has not yet been converted to APT and moved to src/site/apt. Let's convert the forrest docs that haven't been converted yet to new APT content in hadoop-common/src/site/apt (and link the new content into hadoop-project/src/site/apt/index.apt.vm) and remove all forrest dependencies.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira