The open source Java project's 9 April 2026 policy bans AI generated contributions, even as Oracle lets them in at GraalVM, its other open source Java project, under the same legal agreement.
OpenJDK is the public, open-source engine that runs most of the world's Java software, and Oracle co-stewards it. Oracle is now telling contributors that AI cannot write code for that engine, even as the same company asks its own engineers to let AI write code for everything else.
On 9 April 2026, the OpenJDK Governing Board approved an interim policy that forbids contributing any content "generated by large language models, diffusion models, or similar deep-learning systems" into OpenJDK Git repositories, GitHub pull requests, mailing lists, wiki pages, or JBS issues. The Skara tooling that gates OpenJDK contributions will require a checkbox on every pull request affirming compliance. The full policy text is published on the OpenJDK project's legal page.
Private use is permitted and narrower than the prohibition. Developers can still use generative AI to comprehend, debug, and review OpenJDK code, and to do research tied to OpenJDK projects, as long as the generated text itself is not contributed back. The rule is about what enters the shared codebase, not what sits in a developer's terminal.
The carve-out is contractual, not aspirational. Oracle applies the same Oracle Contributor Agreement (OCA) to both OpenJDK and to GraalVM, its other major open-source Java project. Reporting from InfoQ on 12 June documented that under that shared legal instrument, Oracle has banned AI-generated contributions to OpenJDK while allowing them in GraalVM. Same OCA, opposite rules.
Oracle's stated reasons are reviewer burden, safety, and intellectual property. OpenJDK is the implementation that underpins the Java Development Kit used in mission-critical systems, so any defect introduced there is a defect in nearly every Java deployment on the planet. Most generative AI tools are also trained on copyrighted or licensed material whose ownership is contested, and the OCA requires contributors to own the intellectual property they submit. Oracle's policy text itself flags that IP rights in AI output are under active litigation.
Inside Oracle, the posture is the opposite. At Oracle AI World 2025, Larry Ellison framed the company's bet bluntly: "The code that Oracle is writing, Oracle isn't writing. Our AI models are writing. We just tell the model what we want the program to do... the model writes the step-by-step procedure; that thing we commonly think of as a computer program." Co-CEO Mike Sicilia said in March 2026 that Oracle's internal use of AI coding tools is "enabling smaller engineering teams to deliver more complete solutions to our customers more quickly." Oracle has also said agents embedded in its applications can reason, make business decisions, and act on behalf of users, and the company attributed its June 2026 layoff of roughly 21,000 jobs in part to "deployment of AI technologies across our operations."
Oracle said last month it will invest $70 billion over the coming year on datacenter build-out, up from $55.7 billion in fiscal 2026, per The Register's 3 August 2026 reporting. S&P Global Ratings cut Oracle to BBB-/A-3 in late July 2026, one notch above junk, citing an uncertain path to monetizing those investments, and the Financial Times has reported a widening in Oracle's credit-default-swap spread.
The policy is interim. The Skara checkbox will start producing data on who is and is not checking the box, which is the first measurable signal of how the rule is actually lived with. And the GraalVM carve-out, the clearest precedent, is now public: if Oracle later lifts the OpenJDK ban, the shape of that change will tell the Java ecosystem whether the asymmetry was a posture or a contract.