[
https://issues.apache.org/jira/browse/HBASE-19267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16291528#comment-16291528
]
Josh Elser commented on HBASE-19267:
------------------------------------
Awesome. Thanks for the quick reply, Dave! I'll push this to master.
bq. except hbase-spark and hbase-spark-it, which sounds like they are expected
Yeah, I think that would be some more investigation/digging, especially given
what Mike said earlier. We can revisit that one :)
> 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, HBASE-19267.002.branch-2.patch,
> HBASE-19267.002.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)
