[
https://issues.apache.org/jira/browse/HIVE-25799?focusedWorklogId=854800&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-854800
]
ASF GitHub Bot logged work on HIVE-25799:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 04/Apr/23 14:00
Start Date: 04/Apr/23 14:00
Worklog Time Spent: 10m
Work Description: TuroczyX commented on PR #2866:
URL: https://github.com/apache/hive/pull/2866#issuecomment-1496027053
Yes, we had a discussion about it. Because Java 8 is bit old and not sexy
anymore. On the other hand the industry still use it and for some reason the
oracle extended the support till 2030 (?) I would also go ahead personally,
but the big companies who uses hive are way more conservatives. To move even to
JDK 11 for compile it would be make some big pain on them. Even if you are able
to somehow compile it (especially for 11 I think it is possible) I don't think
the community would accept it. Still to many ppl and enterprises use the java8.
Issue Time Tracking
-------------------
Worklog Id: (was: 854800)
Time Spent: 2h 50m (was: 2h 40m)
> Maven should stop early for unsupported java versions
> -----------------------------------------------------
>
> Key: HIVE-25799
> URL: https://issues.apache.org/jira/browse/HIVE-25799
> Project: Hive
> Issue Type: Improvement
> Components: Build Infrastructure
> Reporter: Josh Soref
> Assignee: Josh Soref
> Priority: Trivial
> Labels: pull-request-available
> Time Spent: 2h 50m
> Remaining Estimate: 0h
>
> I made the mistake of using my default java compiler (which apparently is 17)
> to build hive, and it failed. If hive only supports a certain version (or
> ranges of versions) of java, it would be incredibly helpful if maven reported
> this eagerly.
> This is easily achievable using the maven enforcer system (a number of
> enforcers are already deployed in the top level pom):
> [https://maven.apache.org/enforcer/enforcer-rules/requireJavaVersion.html]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
