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

Hudson commented on HBASE-19267:
--------------------------------

FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #4226 (See 
[https://builds.apache.org/job/HBase-Trunk_matrix/4226/])
HBASE-19267 Remove compiler-plugin mapping executions as it breaks Java8 
(elserj: rev 4a1c3b4210b27b04a09e0c4d2f005b2ba7fd884d)
* (edit) hbase-mapreduce/pom.xml
* (edit) hbase-rsgroup/pom.xml
* (edit) hbase-shell/pom.xml
* (edit) hbase-zookeeper/pom.xml
* (edit) hbase-replication/pom.xml
* (edit) hbase-common/pom.xml
* (edit) hbase-backup/pom.xml
* (edit) hbase-thrift/pom.xml
* (edit) hbase-server/pom.xml
* (edit) hbase-external-blockcache/pom.xml
* (edit) hbase-protocol/pom.xml
* (edit) hbase-client/pom.xml
* (edit) hbase-examples/pom.xml
* (edit) hbase-hadoop-compat/pom.xml
* (edit) hbase-hadoop2-compat/pom.xml
* (edit) hbase-it/pom.xml
* (edit) hbase-http/pom.xml


> 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: 3.0.0, 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)

Reply via email to