[
https://issues.apache.org/jira/browse/HBASE-19267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16259399#comment-16259399
]
Josh Elser commented on HBASE-19267:
------------------------------------
Thanks, [~zghaobac]! That would be very appreciated.
On a fresh import of HBase into Eclipse, you would notice that many of the
modules are missing the "Java Nature" in Eclipse which would result in Eclipse
not actually building the projects. As a result, you'll see lots of compilation
errors (e.g. in hbase-server) because previous modules containing necessary
classes like those from hbase-common or hbase-client would not be found.
With this patch (and a {{mvn clean package -DskipTests}} before trying the
import), Eclipse should import everything correctly and have no errors reported
:)
> 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)
