[
https://issues.apache.org/jira/browse/SQOOP-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15012288#comment-15012288
]
ASF subversion and git services commented on SQOOP-2694:
--------------------------------------------------------
Commit 3613843a7c52fb872f7365fae58b2410a1047b4b in sqoop's branch
refs/heads/sqoop2 from [~kathleen]
[ https://git-wip-us.apache.org/repos/asf?p=sqoop.git;h=3613843 ]
SQOOP-2694: Sqoop2: Doc: Register structure in sphinx for our docs
(Jarek Jarcec Cecho via Kate Ting)
> Sqoop2: Doc: Register structure in sphinx for our docs
> -------------------------------------------------------
>
> Key: SQOOP-2694
> URL: https://issues.apache.org/jira/browse/SQOOP-2694
> Project: Sqoop
> Issue Type: Sub-task
> Reporter: Jarek Jarcec Cecho
> Assignee: Jarek Jarcec Cecho
> Fix For: 1.99.7
>
> Attachments: SQOOP-2694.patch
>
>
> As proposed in the umbrella JIRA SQOOP-2667, this JIRA covers following two
> points:
> {quote}
> * I'm really missing a table of context on each page to navigate though the
> entire documentation suite (in some side menu or something)
> * On any formatting error, we print out exception to the documentation and
> won't fail the build.
> {quote}
> I was digging into how to accomplish and the best way seems to be to register
> all documents into single tree structure that sphinx uses internally.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
