But maybe Google is really different than most organizations and they actually did a thorough vetting over the lifetime of the project.
Could you be more specific? I'm curious, as this is not something that seems familiar to me, but 'open source' is pretty big.
When I went and reviewed the logs I saw that the review process did happen, but tailed off and then about two years before I began it had completely stopped. Yet I could find new code checked in that GPL'ed.
This particular place was really receptive to my suggestions and actually refactored the code and rewrote some of the code (although I wouldn't call it clean room). But had I not randomly ran across it, they stopped looking at it. Legal and management cared a great deal about this, but the devs on the floor didn't seem to care quite as much. And I'd heard about some that complained that I had apparently come to slow them down by adding extra process.
In any case, this isn't the only example. I think you'd be surprised how much BSD code gets shipped w/o attribution. And I think you'd also be surprised at how much reverse engineering takes place (which is a slightly different issue, but I think related in liberties devs will often take w/o consulting legal).
Apache Harmony is the other side of the coin from this though: it's an open source project with very strict requirements in terms of contributors: http://harmony.apache.org/contribution_policy.html
And I think Google is likely a lot more careful/knowledgeable than some random hardware company trying to ship a product as fast as it possibly can. Also, my guess is that something like Dalvik is not just something you find laying around on the internet...
IANAL and at least he is. I'm not really sure what to think from it. In particular these bullet quoted items: "•Sun open-sourced Java Standard Edition under the GPL in 2006 and 2007, but didn't include a patent or copyright license with the code. In order to get that license, developers have to demonstrate compatibility with the Java specification.
•The only way to demonstrate compatibility with the Java specification is to use Sun's Technology Compatibility Kit, or TCK, and Sun / Oracle and Apache have been bickering about the license for the Java TCK, or JCK, for years. (That's putting it lightly, actually. It's been more like a war.)
•The only license Sun ever offered Apache for the JCK included significant "field of use" restrictions, including a restriction on mobile phones."
This actually makes me believe that Oracle and Google both know what they're doing and this ends up really ugly. Can anyone give a second opinion as to if those bullet points are true?
* Dalvik, as other people point out above, is not Java. It is its own virtual machine, built from the ground up by Google, so Oracle can't claim copyright on it, but is going after it with patents, which seems like a low blow (we can't compete, so we'll sue).
But the Apache stuff seems shadier. It reads like you specifically can't use the Apache stuff for mobile devices due to patent and copyright issues. Clean room implementations don't get you around either of those specific legal issues -- unless I've misunderstood something here.
If that's the case then I agree.
Could it be the case that Oracle is about to actually test this?
Microsoft used "moving target" tactics to avoid having its APIs cloned.
I also believe the BCL is copyrighted too. I suspect that large chunks of Java libraries are as well.
So this doesn't sound plausible to me.