When you install JDK, you generally also install the JRE, which makes installations of the JDK more likely to be susceptible to the same Java SE licensing changes. Many users unwittingly end up running the Java Development Kit, which is intended for developers. Most users who download “Java” are in fact downloading Java RE. Adding more mud to the waters, functionality and entitlements often cross the boundaries between Java versions. You’ve got Java SE, JRE, JDK, EE, ME, the list goes on.
The acronym swamp that comprises the Java landscape doesn’t exactly help the confusion. Any user can download Java from Oracle’s site, the hard part is understanding whether the features you are activating are free or not. Part of the challenge is Oracle makes it easy to unintentionally activate these subscription-based features. If there’s a way to complicate things, Oracle will find it Depending on the number of endpoints you have running Java, the costs can add up quickly. Here’s the crux: In some instances, Java SE is still free, however, if commercial features are enabled, like “auto-updates”, you are now on the hook to purchase a Java SE subscription license. At issue is Java SE (Standard Edition) – a central component of the Java Runtime Environment (JRE) and the Java Development Kit (JDK), among other versions.
But before we go there, a bit about the problem itself.Īlmost a decade after acquiring Sun, Oracle is now moving to monetize what for years had been available free of charge. The good news is Block 64’s Discovery and Analytics platform gathers the data you need to determine your exposure – and quickly. If you’re like many of our clients, you’ve probably lost some sleep over Oracle’s changes to Java SE Licensing and the compliance risks this has created.
Oracle Java SE compliance concerns? Block 64 has you covered.
0 kommentar(er)
