The following text provides a summary of the key 20 Java License Changes from 2018 to 2023, primarily driven by Oracle’s evolving policies:

2019 Commercial Subscription Requirement:

• Oracle announced that starting in April 2020, security updates for Java 8 and later versions would require a subscription, marking a departure from previously free public updates.

Introduction of Java OTN SE Agreement:

• This new agreement prohibited commercial use of Java without a proper license, impacting many organizations that were unaware of compliance requirements.

BCLA Implications:

• The Binary Code License Agreement (BCLA) led to widespread non-compliance due to its complex terms, which many organizations did not fully understand.

2021 NFTC Agreement:

• Oracle introduced the No-Fee Terms and Conditions (NFTC) agreement, allowing free commercial use of Java starting with JDK 17, although it did not apply to older versions.

Free Access to Java 17 and Later:

• As of September 2021, Oracle declared that Java 17 and newer versions would be free for  commercial use, simplifying access for many developers.

Security Patch Licensing:

• Organizations using Java 17 must obtain a license for security patches after September 2024, despite the free usage of the core version. Similarly, Java SE 21 security patches are free till 2027 after which a license has to be obtained.

2023 Employee-Based Licensing Model:

• Oracle replaced the Named User Plus and Processor licensing models with the “Employee for Java SE Universal Subscription,” which charges based on the total number of employees.

Removal of Old Licenses:

• The previous licensing models (Named User Plus and Processor) were phased out, creating a new standard for Java licensing. The old and new licensing models do not exist together

Unified Pricing Structure:

• The 2023 changes introduced a unified subscription fee for all employees, eliminating separate charges for desktop and server deployments.

Continuing Validity of Existing Agreements:

• Despite the new changes, existing licensing agreements such as Java BCL, Java OTN, and Java NFTC remain valid.

Increased Costs for Organizations:

• The new employee-based model could lead to significant cost increases for organizations, with estimates suggesting annual costs could rise by as much as 1,400% for medium-sized companies.

Transition to Subscription Models:

• The shift to subscription-based licensing has made budgeting for Java usage more complex for organizations.

Impact on Older Versions:

• Users of Java versions 1-16 must still navigate licensing requirements, as the NFTC agreement does not apply to them.

Commercial Features Licensing:

• Certain features, such as Java Flight Recorder and Mission Control, require separate licenses, complicating compliance for organizations using these tools.

Changes in License Metrics:

• The new licensing model affects how organizations calculate their licensing needs, focusing on employee counts rather than user or processor metrics.

Audit Risks:

• With the frequent changes in licensing, organizations face increased risks during audits, as they may not be fully compliant with the latest terms.

Cloud Deployment Challenges:

• Licensing Java in cloud environments has become more complicated, requiring organizations to fully understand their usage to ensure compliance.

Employee Count Considerations:

• Companies must account for all employees, including part-time and contractors, in their licensing calculations under the new model.

Frequent Policy Changes:

• The rapid evolution of Oracle’s licensing policies since 2019 has led to confusion and uncertainty among users regarding compliance and costs.

Migration to OpenJDK:

• As a response to the changing licensing landscape, many organizations are considering migrating to OpenJDK, which offers a cost-effective alternative without the complexities of Oracle’s licensing.

These 20-java-license-changes highlight the importance of staying informed about Oracle’s licensing policies and the need for organizations to regularly review their Java usage and compliance strategies.

In case you want to understand the key issues to be considered in choosing between Oracle and non-Oracle Java, you can click here.

You might want to read more about our CEO Sheshagiri Anegondi. He is one of the foremost Oracle license experts globally. You can contact him for a deeper understanding of Oracle licensing.