Why Are We Here?
Oracle’s opening slide asks: Why are we here? It cites an email from Google’s Tim Lindholm acknowledging Google’s need to get a license for Java&151;something Google never did.
The Crown Jewel
When Oracle acquired Sun Microsystems in 2010, Thomas Kurian, executive vice president of product development, called Java the “crown jewel” of the acquisition.
Google Needed What Java Could Deliver
Google needed to get to market in a hurry with Android, and Java provided just what the doctor ordered.
No Title
Java Is the Right FitGoogle looked at other options and decided that Java met its requirements for Android.
The Build Decision
After assessing options that included Microsoft’s Common Language Runtime (CLR) and C#, Google decided to build on Java.
Suns Ownership
At the time of Google’s decision to build on Java, Sun Microsystems owned the technology along with key copyrights and patents.
Google Realizes Its Position Vis-à-Vis Licensing Java
As this paper trail indicates, Google acknowledges it needs to license Java.
Do It Anyway …
According to this email, Google weighs the option of using Java without a license.
Its On!
According to this email, Google appears poised to go its own way and gird for battle if necessary.
Key Hires
Google beefed up its ranks with key former Sun employees who were familiar with Java in one form or another.
The Open-Source Shield?
According to this email, Google employees realized that though Java was open source, the licensing was such that they would still have to pay royalties.
A Cover-Up?
This email suggests that Google did not want to talk openly about its use of Java.
What Oracle Claims Google Took
Oracle says Google copied Java APIs and code.
Googles Words
Oracle says Google’s own words hurt it in this case.
But Can They Prove It?
Oracle says it will prove that Google willfully copied Oracle’s IP and has benefitted immensely from it.