[
https://issues.apache.org/jira/browse/HBASE-19267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Elser updated HBASE-19267:
-------------------------------
Attachment: HBASE-19267.002.branch-2.patch
.002 makes the same change for the new maven module hbase-zookeeper.
Planning to commit to branch-2 after checking master (if master requires more
significant work, I'll split that out into another issue). I just re-verified
branch-2 locally.
> 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,
> HBASE-19267.002.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)
