hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Haohui Mai <h...@hortonworks.com>
Subject Plans of moving towards JDK7 in trunk
Date Fri, 04 Apr 2014 21:29:16 GMT
Hi,

There have been multiple discussions on deprecating supports of JDK6 and
moving towards JDK7. It looks to me that the consensus is that now hadoop
is ready to drop the support of JDK6 and to move towards JDK7. Based on the
consensus, I wonder whether it is a good time to start the migration.

Here are my understandings of the current status:

1. There is no more public updates of JDK6 since Feb 2013. Users no longer
get fixes of security vulnerabilities through official public updates.
2. Hadoop core is stuck with out-of-date dependency unless moving towards
JDK7. (see http://hadoop.6.n7.nabble.com/very-old-dependencies-td71486.html)
The implementation can also benefit from it thanks to the new
functionalities in JDK7.
3. The code is ready for JDK7. Cloudera and Hortonworks have successful
stories of supporting Hadoop on JDK7.


It seems that the real work of moving to JDK7 is minimal. We only need to
(1) make sure the jenkins are running on top of JDK7, and (2) to update the
minimum required Java version from 6 to 7. Therefore I propose that let's
move towards JDK7 in trunk in the short term.

Your feedbacks are appreciated.

Regards,
Haohui

-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message