Re: Not the only Java implementation without a license
No Vic, the error in logic is yours.
Try and follow it...
1) Clean room work has to be done in a clean room. Any outside contamination destroys the fact that it wasa clean room effort. Meaning you can't claim your work was done in a clean room when it wasn't.
2) Google claims they based their work on Apache. APL allows anyone to do anything with their code under very liberal terms.
3) Oracle's smoking gun. Some of the code wasn't part of Apache and could be traced back to Sun.
4) Apache says that code isn't theirs...
This means that Apace did break the clean room, Google did.
And that's a crucial point.
Google admitted that some of the code was added by a third party and it was since removed.
Doesn't matter, the damage was done. Even if the infringement was small, it's all the proof Oracle needs to destroy the clean room defense. The reason the bar is so low, is that it's difficult to find occurrences. I mean Timmy could always pull up a window and look at Sun's code to give him ideas of how to do something. While he may not have cut and pasted the code, such an act would be a violation of a clean room build. Also if you can find one infringing act, it's more than likely another infringing act occurred elsewhere.
Oh and let's look at Google's defense here and elsewhere....
'a third party did this...'
'a rogue programmer did this'
'we did it because we wanted to maintain the users experience'