[
https://issues.apache.org/jira/browse/HBASE-22653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16882833#comment-16882833
]
Peter Somogyi commented on HBASE-22653:
---------------------------------------
It is odd, but I noticed that for branch-1.4 and branch-1 the _General check_
uses 1.7.0_222 java but for branch-1.3 it is 1.8.0_212 as it should be.
The personality file defines MultiJDK setup for _compile_ and _javadoc_ targets
but it only works for branch-1.4 and branch-1 even though the related files
under dev-support are the same. Yetus sets JAVA_HOME
[here|https://github.com/apache/yetus/blob/a3800fbeb49a6e17760a78417ede5dcff39cc361/precommit/src/main/shell/test-patch-docker/launch-test-patch.sh#L44-L51].
Could be something wrong in this method? It always gets the tail -1 element.
My idea is if JAVA_HOME is set correctly then only compile and javadoc would
run using both JDKs and the rest would rely on JDK 8.
> compile failure using JDK7 and errorProne
> -----------------------------------------
>
> Key: HBASE-22653
> URL: https://issues.apache.org/jira/browse/HBASE-22653
> Project: HBase
> Issue Type: Bug
> Components: build
> Affects Versions: 1.5.0, 1.4.11
> Reporter: Peter Somogyi
> Priority: Major
> Fix For: 1.5.0, 1.4.11
>
>
> Nightly JDK7 build fails for branch-1 and branch-1.4 when errorProne profile
> is used.
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.6.1:compile
> (default-compile) on project hbase-common: Execution default-compile of goal
> org.apache.maven.plugins:maven-compiler-plugin:3.6.1:compile failed: An API
> incompatibility was encountered while executing
> org.apache.maven.plugins:maven-compiler-plugin:3.6.1:compile:
> java.lang.UnsupportedClassVersionError: javax/tools/DiagnosticListener :
> Unsupported major.minor version 52.0{noformat}
> https://builds.apache.org/job/HBase%20Nightly/job/branch-1/929/
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
