The sequence, structure and organization of those method signatures, in those 37 Java packages, were all GPL'd in the OpenJDK in 2007 by Sun. Regardless of whether API's can be copyrighted or not, Google had every right to use the code Sun GPL'd.
That's true, but the availability of OpenJDK (which, after all, Google have now switched to) weakens Oracle's argument on the "Effect on the market" factor.
If the "structure, sequence, and organization" of APIs is a copyrightable work in its own right, then couldn't Google make a GPL-licensed derivative SSO (Android's API) but put their implementation under a separate license? Has anyone done a legal analysis of how the GPL's copyleft provisions would apply to this new kind of copyrighted work?
FYI, Classpath exception does not remove GPL from OpenJDK, or enable anyone to create a non-GPL JDK. It allows you to create Java programs that are themselves not GPL.
