[
https://issues.apache.org/jira/browse/HBASE-19267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16260434#comment-16260434
]
Guanghao Zhang commented on HBASE-19267:
----------------------------------------
Try it on branch-2. And it worked for me. :-)
Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
2015-11-11T00:41:47+08:00)
Maven home: /opt/soft/apache-maven-3.3.9
Java version: 1.8.0_131, vendor: Oracle Corporation
Java home: /opt/soft/jdk1.8.0_131/jre
Default locale: zh_CN, platform encoding: UTF-8
OS name: "linux", version: "3.13.0-46-generic", arch: "amd64", family: "unix"
Eclipse Version: Version: Oxygen.1a Release (4.7.1a).
Meanwhile, I got the NullPointerException (as [~vrodionov] said) too when use
the old version eclipse(4.4.2).
> Eclipse project import issues on 2.0
> ------------------------------------
>
> Key: HBASE-19267
> URL: https://issues.apache.org/jira/browse/HBASE-19267
> Project: HBase
> Issue Type: Task
> Components: build
> Reporter: Josh Elser
> Assignee: Josh Elser
> Fix For: 2.0.0-beta-1
>
> Attachments: HBASE-19267.001.branch-2.patch
>
>
> Trying to do a fresh import of branch-2 nets some errors..
> It seems like a previous change I made to clean up errors (HBASE-13236),
> specifically adding the maven-compiler-plugin lifecycle mapping for
> m2eclipse, is now causing Eclipse to not compile HBase as Java8. Removing the
> lifecycle mapping fixes this.
> I assume this only needs to happen for 2.0.
> I keep having issues with the JavaNature being ignored. Not yet sure if this
> is a result of something we're doing wrong (or just Eclipse being Eclipse).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
