hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-19267) Eclipse project import issues on 2.0
Date Thu, 16 Nov 2017 15:39:00 GMT

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

Josh Elser commented on HBASE-19267:
------------------------------------

[~mdrob], do you have a minute to take this for a spin on branch2? The general steps I took
locally which worked:

* Apply patch
* {{for d in .settings .classpath .project; do find . -name $d | xargs rm -r; done}}
* {{mvn clean package -DskipTests}} (to work around the build plugins that we ignore in the
lifecycle mapping)
* Import as Maven Project

> 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)

Mime
View raw message