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

Hudson commented on HBASE-20389:
--------------------------------

Results for branch master
        [build #299 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/299/]: (x) 
*{color:red}-1 overall{color}*
----
details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://builds.apache.org/job/HBase%20Nightly/job/master/299//General_Nightly_Build_Report/]




(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://builds.apache.org/job/HBase%20Nightly/job/master/299//JDK8_Nightly_Build_Report_(Hadoop2)/]


(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://builds.apache.org/job/HBase%20Nightly/job/master/299//JDK8_Nightly_Build_Report_(Hadoop3)/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


> Move website building flags into a profile
> ------------------------------------------
>
>                 Key: HBASE-20389
>                 URL: https://issues.apache.org/jira/browse/HBASE-20389
>             Project: HBase
>          Issue Type: Improvement
>          Components: build, website
>            Reporter: Sean Busbey
>            Assignee: Sean Busbey
>            Priority: Minor
>             Fix For: 3.0.0, 2.1.0, 2.0.1
>
>         Attachments: HBASE-20389.0.patch, HBASE-20389.1.patch
>
>
> we have some "magic" in our website building right now. The script that's 
> used bout our automated website build + publish mechanism manually sets a 
> bunch of stuff on the maven command line.
> It'd be better to reflect those settings in a maven profile, so that folks 
> are less likely to be surprised e.g. when trying to debug a failure in the 
> {{site}} goal happens.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to