hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Dimiduk (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-15042) refactor so that site materials are in the Standard Maven Place
Date Fri, 03 Nov 2017 17:31:01 GMT

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

Nick Dimiduk commented on HBASE-15042:

Sorry, reading back through the comment history. Any patch that is back-ported must be applied
release line by release line. So, master, branch-1, branch-1.4, branch-1.3, branch-1.2, branch-1.1;
branch-1.1 is the last in line. Branch-1.1 is also the least urgent, as the next release will
likely be the last. I can manually bring back docs updates for that release. RMs for the other
branches would be more intersted in continued parity with master's structure.

> refactor so that site materials are in the Standard Maven Place
> ---------------------------------------------------------------
>                 Key: HBASE-15042
>                 URL: https://issues.apache.org/jira/browse/HBASE-15042
>             Project: HBase
>          Issue Type: Task
>          Components: build, website
>            Reporter: Sean Busbey
>            Assignee: Jan Hentschel
>            Priority: Minor
>             Fix For: 2.0.0
>         Attachments: HBASE-15042.master.001.patch, HBASE-15042.master.002.patch, HBASE-15042.master.002.patch,
> for some reason we currently have our site materials in {{src/main/site}} rather than
the maven prescribed {{src/site}}. 

This message was sent by Atlassian JIRA

View raw message