hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-7372) Check in the generated website so can point apache infrastructure at what to publish as our hbase.apache.org
Date Tue, 18 Dec 2012 01:15:11 GMT

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

stack commented on HBASE-7372:
------------------------------

[~ndimiduk] It'll be similar to how it currently is.  Check in docbook and xdoc changes as
you go.  Independently, if you thnk it time to publish a new version of website, you'd run
'mvn site site:stage'.  site:stage will copy the generated site to ./hbase.apache.org (if
we apply the patch I'm attaching).  You'd then commit it locally.  That'll trigger the deploy
on apache servers.

Previous, it was about the same amount of gymnastics....we'd do site:deploy instead of site:stage
and it would rsync what was generated by 'mvn site' over to people.apache.org.  From there
it'd be rsync'd automatically out to apache frontends.

I tried to get site:deploy to deploy locally rather than copy over to people.apache.org only,
when I change the target url to be hbase.apache.org, it goes and puts hbase.apache.org in
all sub-modules.... ugly.   When I was young and headstrong rather than as I am now, old and
headstrong, I would try and wrestle maven into doing what I wanted.  I don't do that anymore.
                
> 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

Mime
View raw message