I think the project is really needed, but I'm not sure it's quite ready yet. The OpenJDK 10 build shows 25 November 2017 as it's build date and is Linux and macOS only.
Is it really needed? Maybe I don't understand what it does, but what's the point of downloading openJDK there instead of directly from a package manager?
They're different builds. As far as I can tell, the openjdk builds by Debian for example are not and will not be TCK certified (due to a licensing problem if I understood correctly), whereas AdoptOpenJDK claims some builds are certified https://adoptopenjdk.net/support.html.
In my case the certification probably won't matter, we've been running with OpenJDK from debian for a long time without problems, but I'm curious to test the OpenJDK builds that use OpenJ9 to see if it can outperform Hotspot on some workloads.
Correct, the AdoptOpenJDK builds will pass the TCK as well as other industry test suites. We'll build both OpenJ9 and Hotspot derivatives (and some other esoteric ones as well). We hope to work with the distros to unify the OpenJDK stories there somewhat (but we have a lot of work to do first).
What's the point of avoiding the standard Java installer provided by Oracle then? I thought the only problem with it is that you are not allowed to put it in the distros or automate its downloading.
Since then, due to the bad press i suppose, Oracle has decided to open source most of these features (the others are retired).
The Java Flight Recorder is not yet in the OpenJDK but AppCDS is already integrated in 10.
You mean the new year-based versioning system? I think it's not that bad (until they decide to introduce breaking changes). Indeed, Oracle giving Java EE away and switching to enterprise-hostile release cycle after watching peacefully at major browsers retiring Java applets support suggests it has lost interest in Java (but the trademark and, perhaps, some patents) but I still believe the JVM platform is still very far from its coffin as it provides great base for amazing aspiring languages like Scala and as Java itself keeps its pretty secure place among the most widely used languages.
This is one of the reasons why we created the build farm and will be producing LTS supported builds for OpenJDK. It will be a default place that people can go to get a professionally tested, TSK compliant OpenJDK binary. They can also still choose to go to a vendor for commercial support.
The quality and consistency of the OpenJDK binaries provided by the distros varies. We'll be working with the distros to help give them a consistent experience (they could for example use our infrastructure as code to add an extra level of testing.
I have some hate toward Oracle because I have worked in databases and because I have learned unix with SunOS (and also because Oracle has ruined the security reputation of java applet). Concerning Java, I do not understand. It seems they are blocking updates for non paying customers, but at the same time Oracle is removing differences between OpenJDK builds and Oracle JDK binaries. Is Oracle good or evil (concerning java) ? Is java future doom ?
I'm the chief cat herder over on AdoptOpenJDK. It is a build farm in progress with the end goal of providing OpenJDK LTS support (matching Oracle's timelines) for OpenJDK on all platforms that Java currently runs on (including ARM32/64, zos, AIX, z390 as well as Linux x86, Mac OS X, windows etc). Wee'll also support OpenJDK variants such as Eclipse OpenJ9, SAP OpenJDK, OpenJFX, and some of the early builds of experimental new features.
It's also an infrastructure as code project so OpenJDK vendors have a common place to shared build technology and workflows. For example we currently have IBM, Red Hat, Oracle, SAP and other vendor engineers working on this.
The release builds will be TCK tested, as well as a variety of other common industry test suites. The quality level will be as high if not higher than existing vendors today.
I appreciate there's probably a lot of confusion (especially as this is still a work in progress) so please fire questions my way!
37 comments
[ 3.2 ms ] story [ 86.0 ms ] threadCould have just used "rockstar" https://github.com/avinassh/rockstar
In my case the certification probably won't matter, we've been running with OpenJDK from debian for a long time without problems, but I'm curious to test the OpenJDK builds that use OpenJ9 to see if it can outperform Hotspot on some workloads.
It's nice to be able to install a JDK where you won't be charged oodles of dollars just because you accidentally used the wrong command line argument.
https://www.theregister.co.uk/2016/12/16/oracle_targets_java...
There's a XX:+UnlockCommercialFeatures switch which enables features like the Java Flight Recorder.
Other examples are the MSI Enterprise Installer and JRE Usage Tracking.
This may be nail in Java's coffin if this plays out as implied.
https://www.azul.com/downloads/zulu/
Although android is a kinda java, many things aren't available, such as invokedynamic (only in Android 8+), and javadoc (uses javac).
This is not to mention the functional and other stuff in later javas.
I'm the chief cat herder over on AdoptOpenJDK. It is a build farm in progress with the end goal of providing OpenJDK LTS support (matching Oracle's timelines) for OpenJDK on all platforms that Java currently runs on (including ARM32/64, zos, AIX, z390 as well as Linux x86, Mac OS X, windows etc). Wee'll also support OpenJDK variants such as Eclipse OpenJ9, SAP OpenJDK, OpenJFX, and some of the early builds of experimental new features.
It's also an infrastructure as code project so OpenJDK vendors have a common place to shared build technology and workflows. For example we currently have IBM, Red Hat, Oracle, SAP and other vendor engineers working on this.
The release builds will be TCK tested, as well as a variety of other common industry test suites. The quality level will be as high if not higher than existing vendors today.
I appreciate there's probably a lot of confusion (especially as this is still a work in progress) so please fire questions my way!