karianna

Apologies, you're right. Existing Censum subscriptions will continue to be supported (but not auto-renewed as they were in the past). However, we won't be taking on new customers until the dust settles and the future strategy of the product is decided.

We had started to submit actual patches and work yes, that will now increase at MSFT. (ex jClaritt CEO here)

We're going to discuss that in the next couple of weeks. I personally hope we can continue to provide its core functionality to as many developers and ops folks as possible!

jClarity's CEO here - happy to answer questions here if they happen to pop up, we're obviously pretty chuffed :-).

The AdoptOpenJDK community (a consortium of vendors and users that produce business ready OpenJDK binaries) will work with the Debian maintainers to course correct this going forwards. If you’d like to get involved see https://AdoptOpenJDK.net

Wellington, NZ would like to have a word

Was very happy to see the rename. I participated in the review threads at the OSI and whilst I have a lot of sympathy for Redis, Mongo and others (I’m a closed source software CEO myself) I felt strongly that open source is not a business model and the definition of open source licenses should be kept strict to the OSD freedoms defined by the OSI.

Well done to Redis for making this clear

Hi all - I help run https://adoptopenjdk.net - I genuinely think that the article is spreading some FUD, but I also understand if folks feel strongly about looking at alternatives then you can read the full background https://medium.com/@javachampions/java-is-still-free-c02aef8... and I'm happy to answer Q's here as well

AdoptOpenJDK will be working with Amazon and the other providers to make sure there's some consistency between the binaries, no point in fragmenting all over the place, consumers expect to be able to drop in replacements.

Or AdoptOpenjDK https://www.adoptopenjdk.net

AdoptOpenJDK is the much larger project with broad community backing (We even have Amazon contribute) from IBM, Red Hat, Azul, Ocado, Microsoft etc. It's got a fully open and auditable build and test pipeline and supports a massive number of platforms (arm32/64, AIX, s390, Mac, Windows, Linux x86, PPC etc) and versions (8, 9, 10, 11, amber, 12 beta et al). We've already had over 2M downloads and are definitely in production in a lot of places.

We'll be working with Amazon to make sure there's some consistency between the two, no point in fragmenting.

Corretto is an obvious choice if you're an AWS user, for everything else Adopt is also a decent choice.

Oh dear - the FUD is strong with this one. You’re only required to buy a commercial license if you use Oracle’s JDK beyond their free public updates timeframe and if you want the subsequent security patches etc from Oracle. There are also a whole bunch of $free (and $commercial) OpenJDK alternatives by Azul, RedHat, IBM, AdoptOpenJDK, distrust etc.

I help run OpenJDK advocacy - and yeah we notice . The authors aren’t always able to jump in on threads but we collate feedback for them

For those concerned about being forced to use Oracle’s JDK / support you can definitely just use OpenJDK now. The build farm we have put together at AdoptOpenJDK.net will produce professionally tested OpenJDK binaries for all major versions and platforms with free LTS support. You can then also always go to a commercial vendor like Oracle for extra paid support if that’s what your org needs.

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).

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.

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.

It's a good bot, we'll likely change this mechanism though :-)

Hi all,

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!

We're talking to MS (looking promising) and Amazon (also) promising. Still need to reach out to the Google folks directly, thanks for the reminder!

You're totally correct. We (jClarity) will likely ditch our proprietary, hand rolled metrics gathering (which we built at great pain wince) in favour of FR. I'd be pretty surprised if all of the other vendors don't do something similar (Why NIH).

The aim is for 11 yes.

The goal was to emulate what https://github.com/ojdkbuild/ojdkbuild started many years ago but take it alot further. Adopt will provide completely open transparent infrastructure as code (and infrastructure) for folks to build OpenJDK. We've got Red Hat, IBM, Oracle and SAP + various JUG's participating and I expect it'll become the common build farm for Java going forwards. People are also more than welcome to clone the whole thing and use it internally!

Exactly this. FR will allow APM vendors (and individual teams) to build solutions on top of a continuous lightweight, always on profiler. It's actually a bit of a game changer for Java / JVM performance

I'm the head Cat Herder (so to speak) for the AdoptOpenJDK OpenJDK binary build farm. The OpenJDK builds we are producing pass the regular OpenJDK tests, a series of system tests and the official TCK/JCK. The quality bar is high and once we've stabilised this process for Java 8,9,10, 11+ and all of the platforms (AIX, ARM 32/64, Windows, Mac, Linux, z390, zOS etc) then we'll be broadly advertising its service. Whether or not we earn the trust of enterprise, we'll have to see :-).

Disclaimer: I'm the CEO of jClarity - a Java/JVM APM vendor.

You'll see plenty of APM vendors building on top of this technology. For years we've all tried to build lightweight mechanisms to get vital metrics out of the JVM with regards to Object and Execution profiling and although some strong progress was being made (Honest Profiler, Async Profiler et al), none of them are as comprehensive as Flight Recorder (Oracle did have the advantage of owning Java there).

Our own plans will be to refactor our ML diagnostic engine on top of Flight Recorder data. We're really, really looking forward to this!

Hi all,

I'm one of the authors behind https://www.adoptopenjdk.net (CI at ci.adoptopenjdk.net, project at github/adoptopenjdk) where we are providing nightly and release builds of OpenJ9 (as well as a host of other OpenJDK derivatives). We've recently been granted the TCK (as the London Java Community) and so you'll shortly have professionally tested 'You can call this Java' binaries.

Hi All,

I represent the London Java Community (LJC) on the Java Community Process (JCP) Executive Committee (EC), aka the Java standards body. I also help run the Adopt OpenJDK programme for OpenJDK outreach and onboarding new developers to work on Java itself.

Now that the acronyms are out of the way :-). We're working at the JCP with Oracle to streamline the standardisation process in order to facilitate these faster releases and provide other Java vendors the ability to run their reference implementations against an in flight Technical Compatibility Kit (TCK), which is what you need to pass in order to call yourself Java.

I'm really, really pleased that Oracle is increasing the cadence. Java 9 allows for incubation modules and so if something isn't ready, it can simply be put in there for early testing without it impacting the main release.

Some folks asked about alternative platforms. In terms of providing high quality releases of OpenJDK for alternative platforms we've created a portal at https://www.adoptopenjdk.net with the build farm run via https://ci.adoptopenjdk.net (code in various repos at https://www.github.com/AdoptOpenJDK). We've only just received the Java Test Compatibility Kit J(TCK) from Oracle and once we have the binaries tested against that then folks will be able to get the latest OpenJDK binaries for all of the esoteric platforms (ARM, z360, AMD variants, AIX, Solaris and so forth).

We'd love for folks with devops skills to come and join us (Docker, IaaS, Jenkins, make skills welcome).

If you have any specific questions please throw them my way!

This is actually a huge change for operations / devops. JFR is the only tooling out there today that can accurately and safely gather important performance metrics from the JVM in a low impact manner. All other APM vendors like ourselves (jClarity) have to perform hacks of some sort to try and emulate JFR's capabilities. This high quality data source is something that our engineering team is very excited to have opened up!

I sit on the standards body for Java EE which will be involved in helping make this step - would love to hear opinions on what foundation and licensing they'd like to see this under (and why).

Some Java EE specs are already at Eclipse (long standing historical reasons), so there is a small precedent