Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 185C4FCCA for ; Sat, 6 Apr 2013 23:21:17 +0000 (UTC) Received: (qmail 56525 invoked by uid 500); 6 Apr 2013 23:21:16 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 56418 invoked by uid 500); 6 Apr 2013 23:21:16 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 56311 invoked by uid 99); 6 Apr 2013 23:21:15 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 06 Apr 2013 23:21:15 +0000 Date: Sat, 6 Apr 2013 23:21:15 +0000 (UTC) From: "stack (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HBASE-8286) Move site back up out of hbase-assembly; bad idea MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 stack created HBASE-8286: ---------------------------- Summary: 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 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