Former Sun CEO says Google's Android didn't need license for Java APIs
Jonathan Schwartz (Credit: Stephen Shankland/CNET) — SAN FRANCISCO — Former Sun CEO Jonathan Schwartz took the stand here today as a witness for the defense, and disputed Oracle's claim that Java APIs were proprietary code from Sun.
Context & Ripple Effects
Oracle v. Google has entered its witness phase, and Google's defense put up the one executive who ran Sun when Android's Java use began: Jonathan Schwartz, testifying for the defense that Java APIs were not proprietary Sun code and that Android needed no license for them. The testimony lands three days after CNET reported that Android chief Andy Rubin wrote in a 2006 internal email that the java.lang APIs were copyrighted — so the courtroom fight is now Sun's own former CEO against Google's own Android chief over who treated the APIs as property.
The story traveled widely on pickup — Groklaw, ZDNet, eWeek, Computerworld and four other outlets carried it the same day — because Schwartz is not a hired expert but the man who signed off on Sun's Java strategy, making his denial of Oracle's ownership claim hard for Oracle to wave off as secondhand opinion.
First-order effects
- Schwartz's testimony undercuts Oracle's core premise — that Sun treated the Java APIs as proprietary licensed property — by supplying contrary evidence from inside Sun itself.
- Google gains a credible rebuttal to the Rubin email narrative that Android engineers knew the APIs were protected and used them anyway.
Second-order effects
- Oracle now has to argue its own former CEO mischaracterized Sun's position, shifting its case toward damages framing rather than clear-cut infringement.
- Other companies that reimplemented Java-compatible runtimes without licenses gain a precedent argument: if Sun's chief executive says no license was required for APIs, their exposure shrinks too.
Third-order effects
- If the court accepts that API declarations sit outside copyright — or fall under fair use — the ruling becomes structural cover for interoperable reimplementation across the software industry; if Oracle prevails instead, interface compatibility becomes a licensable asset, changing how platforms price access.
- The verdict will set how much of a platform's value courts recognize as living in its interfaces rather than its implementation, with knock-on effects for every ecosystem built on someone else's spec.
The trend: Software copyright litigation is migrating from copied code to copied interfaces, turning API design into contested legal territory.