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-8286) Move site back up out of hbase-assembly; bad idea
Date Sun, 07 Apr 2013 05:51:16 GMT

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

stack commented on HBASE-8286:
------------------------------

site passed.  going to commit.
                
> Move site back up out of hbase-assembly; bad idea
> -------------------------------------------------
>
>                 Key: HBASE-8286
>                 URL: https://issues.apache.org/jira/browse/HBASE-8286
>             Project: HBase
>          Issue Type: Task
>            Reporter: stack
>            Assignee: stack
>         Attachments: 8286.txt
>
>
> Redoing the packaging, I thought it smart putting it all under the new hbase-assembly
module.  A few weeks later, it is not looking like a good idea (Enis suggested moving the
site was maybe 'odd').  Here are a few issues:
> + The generated reports will have mention of hbase-assembly because that is where they
are being generated (Elliott pointed out the the scm links mention hbase-assembly instead
of trunk).
> + Doug Meil wants to build and deploy the site but currently deploy is a bit awkward
to explain because site presumes it is top level so staging goes to the wrong place and you
have to come along and do fixup afterward; it shouldn't be so hard.
> A possible downside is that we will break Nicks site check added to hadoopqa because
site is an aggregating build plugin... but lets see.

--
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