[
https://issues.apache.org/jira/browse/HBASE-7372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13535445#comment-13535445
]
stack commented on HBASE-7372:
------------------------------
I looked at making an hbase-site module. After messing with it for a while --
in spite of my axiom above -- I think its probably better to leave it as is.
The site generation is made up from all hbase-* content so you want some kinda
of meta perspective when building it. Trying to move the top-level site src
stuff... src/docbkx, etc. -- down into hbase-site would take a bunch of messing
regen'ing the site and messing in poms. I'll leave it as is. We can try it at
another time.
> Check in the generated website so can point apache infrastructure at what to
> publish as our hbase.apache.org
> ------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-7372
> URL: https://issues.apache.org/jira/browse/HBASE-7372
> Project: HBase
> Issue Type: Bug
> Reporter: stack
>
> January 1st is deadline for changing how we publish our website. We may no
> longer rsync out to people.apache.org. Apache infrastructure supplies two
> options here: http://www.apache.org/dev/project-site.html We could redo our
> site in apache cms format. Or we could just use svnpubsub and keep on w/ how
> the site is currently generated and on checkin, have it autopublished. I'll
> go the latter route unless I hear otherwise.
> For svnpubsub, we need to point apache infrastructure at a directory that has
> our checkedin site in it. I was thinking ${hbasedir}/hbase.apache.org
> Let me raise this on the dev list too.
--
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
