[
https://issues.apache.org/jira/browse/HBASE-11155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13998891#comment-13998891
]
stack commented on HBASE-11155:
-------------------------------
bq. A better option would be to have the Jenkins job commit a built
hbase-default.xml file from its output and use that as fallback content. I
await guidance.
I'd rather it be plainly broken rather than go stale and we don't notice it.
Should the fallback have a fat label on top saying STALE VIEW?
I tried the patch and then skimmed the patch while looking at generated doc.
All looks good to me. Want me to commit? (I can add 'STALE VIEW' on commit if
you'd like).
> Fix Validation Errors in Ref Guide
> ----------------------------------
>
> Key: HBASE-11155
> URL: https://issues.apache.org/jira/browse/HBASE-11155
> Project: HBase
> Issue Type: Bug
> Components: documentation
> Affects Versions: 0.98.2
> Reporter: Misty Stanley-Jones
> Assignee: Misty Stanley-Jones
> Attachments: HBASE-11155.patch
>
>
> Before I do serious documentation work, I have to fix all of the validation
> errors that are somehow not causing the Ref Guide to break the builds. I will
> attach one patch per file -- that's the easiest way I know how to do it. I
> will try not to make any content changes, only validation changes.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
