OpenJDK Banned AI-Generated Code. Here Is Exactly What the Policy Allows
The story hit the Hacker News front page again this week: Oracle bans AI-generated code from OpenJDK. 536 points, 381 comments, and a comment section full of people arguing about a policy most of them had apparently not read. I have run AI coding agents as a core part of my daily workflow for a long time now, so my first reaction was the same as probably yours: a blanket ban? In 2026? For Java,…
OpenJDK has banned AI-generated code, sparking debate across Hacker News. Oracle's decision may seem surprising given the language's widespread use, but upon closer examination, the policy reveals a more nuanced stance. The core rule disallows any content, including code, images, and text, generated by large language models or similar deep-learning systems.
This means AI can be used for reading, reviewing, and researching code, but it cannot contribute anything to the project. The policy cites three main risks: reviewer burden, safety and security, and intellectual property. The latter, particularly the concern around intellectual property rights and Oracle's Oracle Contributor Agreement, appears to be the driving force behind the absolute ban.
Interestingly, GraalVM, another Oracle project, allows AI assistance in coding, provided the final output is authored by the user. This contrast highlights the complexities surrounding AI-generated content and intellectual property, especially when dealing with a major player like Oracle.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
