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

Duo Zhang commented on HBASE-15624:
-----------------------------------

This is the pre-commit build result with HBASE-16591 applied.

{noformat}
-1 overall

 _____     _ _                _ 
|  ___|_ _(_) |_   _ _ __ ___| |
| |_ / _` | | | | | | '__/ _ \ |
|  _| (_| | | | |_| | | |  __/_|
|_|  \__,_|_|_|\__,_|_|  \___(_)
                                


| Vote |       Subsystem |  Runtime   | Comment
============================================================================
|   0  |         reexec  |  0m 6s     | Docker mode activated. 
|  +1  |      hbaseanti  |  0m 0s     | Patch does not have any anti-patterns. 
|  +1  |        @author  |  0m 0s     | The patch does not contain any @author 
|      |                 |            | tags.
|  -1  |     test4tests  |  0m 0s     | The patch doesn't appear to include any 
|      |                 |            | new or modified tests. Please justify
|      |                 |            | why no new tests are needed for this
|      |                 |            | patch. Also please list what manual
|      |                 |            | steps were performed to verify this
|      |                 |            | patch.
|  +1  |     mvninstall  |  52m 27s   | master passed 
|  +1  |        compile  |  2m 42s    | master passed 
|  +1  |     mvneclipse  |  3m 41s    | master passed 
|  +1  |        javadoc  |  2m 53s    | master passed 
|  +1  |     mvninstall  |  3m 10s    | the patch passed 
|  +1  |        compile  |  2m 47s    | the patch passed 
|  +1  |          javac  |  2m 47s    | the patch passed 
|  +1  |     mvneclipse  |  1m 6s     | the patch passed 
|  +1  |     whitespace  |  0m 0s     | The patch has no whitespace issues. 
|  +1  |            xml  |  0m 1s     | The patch has no ill-formed XML file. 
|  +1  |    hadoopcheck  |  37m 21s   | Patch does not cause any errors with 
|      |                 |            | Hadoop 2.4.0 2.4.1 2.5.0 2.5.1 2.5.2
|      |                 |            | 2.6.1 2.6.2 2.6.3 2.7.1.
|  +1  |    hbaseprotoc  |  1m 28s    | the patch passed 
|  +1  |        javadoc  |  1m 53s    | the patch passed 
|  +1  |     asflicense  |  0m 50s    | The patch does not generate ASF License 
|      |                 |            | warnings.
|      |                 |  110m 30s  | 


|| Subsystem || Report/Notes ||
============================================================================
| Docker | Client=1.12.1 Server=1.12.1 Image:yetus/hbase:7bda515 |
| Optional Tests |  asflicense  javac  javadoc  unit  xml  compile  |
| uname | Linux 9a692c569b5e 3.13.0-96-generic #143-Ubuntu SMP Mon Aug 29 
20:15:20 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | /home/zhangduo/hbase/code/dev-support/hbase-personality.sh |
| git revision | master / 7bda515 |
| Default Java | 1.8.0_101 |
| modules | C: . U: . |
| Powered by | Apache Yetus 0.3.0   http://yetus.apache.org |


============================================================================
============================================================================
                              Finished build.
============================================================================
============================================================================
{noformat}

Seems OK?

> Move master branch/hbase-2.0.0 to jdk-8 only
> --------------------------------------------
>
>                 Key: HBASE-15624
>                 URL: https://issues.apache.org/jira/browse/HBASE-15624
>             Project: HBase
>          Issue Type: Bug
>            Reporter: stack
>            Assignee: stack
>            Priority: Blocker
>             Fix For: 2.0.0
>
>         Attachments: hbase-15624.patch
>
>
> Set build and pom target jvm version as jdk8. We chatted about it here: 
> http://osdir.com/ml/general/2016-04/msg09691.html Set it as blocker on 2.0.0.
> We need to work on YETUS-369 before we can finish up this issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to