+1.
I also recommend OpenJDK 7 over Oracle when on Linux. Please find below the arguments I used in January on an internal email:
******
I also propose that we switch to OpenJDK 7 (amd64/x86_64) for all Debian and CentOS deployments.
(1) From Java 7, OpenJDK is the Reference Implementation.
http://en.wikipedia.org/wiki/OpenJDK
(2) Using OpenJDK 7 gives us a full open-source stack.
(3) OpenJDK 7 is shipped with Debian and CentOS and is taking over the world, particularly as Oracle JDK >=6u29 including 7 lacks the redistribution licence of Oracle JDK <6u29 and so was kicked from Debian:
http://mrpogson.com/2011/12/14/sun-java-no-longer-welcome-in-debian-gnulinux/
Oracle JDK includes some additional closed-source components that are licensed from third-parties, including audio codecs and fonts. The absence of these components is unlikely to be important for server deployments. OpenJDK also lacks the web browser plugin and webstart; I see this as a feature! The former was notorious for security problems and the latter is awful spaghetti code (a former coworker signed the NDA, ha ha!). Neither are relevant for server deployments (except JNLP Jenkins slaves?).
https://blogs.oracle.com/henrik/entry/java_7_questions_answers
"Q: What is the difference between the source code found in the OpenJDK repository, and the code you use to build the Oracle JDK?
A: It is very close - our build process for Oracle JDK releases builds on OpenJDK 7 by adding just a couple of pieces, like the deployment code, which includes Oracle's implementation of the Java Plugin and Java WebStart, as well as some closed source third party components like a graphics rasterizer, some open source third party components, like Rhino, and a few bits and pieces here and there, like additional documentation or third party fonts. Moving forward, our intent is to open source all pieces of the Oracle JDK except those that we consider commercial features such as JRockit Mission Control (not yet available in Oracle JDK), and replace encumbered third party components with open source alternatives to achieve closer parity between the code bases."
Does anyone have blockers moving to OpenJDK 7? Sure I saw lots of problems with OpenJDK 6, but OpenJDK 7 is a very different beast and much, much closer to Oracle, without any of the encumberances.
******
On 26/03/14 17:21, Andrea Aime wrote:
Hi,
given that java 6 has been out of support for a while now, and java 8 is
out,
how do people feel about upping our minimal java requirement to java 7
on the master branches of GeoTools and GeoServer?
Pro/cons, issues you see?
Cheers
Andrea
--
Meet us at GEO Business 2014! in London! Visit http://goo.gl/fES3aK
for more information.
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
-------------------------------------------------------
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
_______________________________________________
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre