For what it's worth, this still at least looks like it's mostly code from test frameworks, which doesn't necessarily even run on an Android device itself. So it could likely be dropped from the source distributions without compromising the functionality of any device. (Distributing it would still have been infringement --- but a lot more easily remedied than it might have been otherwise.)
Specifically, if we look at the PDFs from the original source here:
six of the seven Android files are in subpackages of "org.apache.harmony.security.tests". The Android version of Mueller's example number six, strangely, has no package declaration at all, but the name of the class (PolicyNodeImpl) at least is the same as one that has been identified as unit test code the last time it came up in this connection.
(BTW, the "org.apache.harmony" package prefix doesn't necessarily mean that the ASF ever distributed the particular file in question; that PolicyNodeImpl.java file was distributed by Google with an Apache Harmony package declaration, but had never been distributed by the ASF itself.)
About the files with the Oracle copyright header, it seems to be on some remote tree that I can't even browse. Can you opine on whether it was ever actually shipped?
This is the most important post in this thread. It looks like they created their own "conformance tests", in some cases using the Java implementation as the baseline. On the scale of concerns, that is somewhere around 0.
Google should have done everything they could to buy Sun or at least buy the Java IP and Engineering team. Heck they could have bought them out fully and sold the uninteresting parts.
That would have been better for two reasons - Oracle is screwing up bad with the JCP and it's going to hurt Java - May be Google could have been a better steward. Secondly Google relies so much on Java not only for Android but also for many other things - it is almost idiotic not to buy the IP.
I guess they had their reasons to not pursue - I can't imagine what those were.
As I recall, IBM had an offer out for Sun, and Sun fell into Oracle's hands quite suddenly when IBM and Sun management couldn't agree on terms. It might be that Google was expecting that IBM would get Sun, and that they were OK with that, given IBM's generally more, shall we say, less frenzied approach toward monetizing its intellectual property...
Good point, Oracle paid $5.6 billion for Sun, Google could have afforded that, they just offered $6 billion for Groupon. OTOH, that seems like a lot of money to pay just for Java.
> Oracle is screwing up bad with the JCP and it's going to hurt Java
i was far from all this politics, but made a few google searches - is this about ASF leaving JCP? then, as far as i understood, these issues are all related, to Harmony, suing etc.
so maybe Java wouldn't be hurt? just specs would be changed more tyrannically...
From a quick look it definitely looks like copyright infringement, but in a non-critical area of Android. Google may end up paying a small fine over this, but it doesn't address Oracle's central claim that the Dalvik VM infringes their patents.
I wonder if the code was copied before Google bought Android or after. And would they be able to just pay licensing to Oracle for the code?
I don't get one thing. I thought Java is supposedly open-source? How come there's proprietary source code? Or are these files part of a particular Java library developed by Sun that are not part of the Java that they open-sourced?
The issue is not with the open-source portion, it's with relicensing. The implication is that parts of the code that are in Android's Java implementation were copied outright and then relicensed to APL, which is not allowed--the original code is GPL, and must stay GPL, unless the original author decides to license it under a different license.
The timing is irrelevant. It's almost certain that when Google bought Android, they'd have taken on any legal liabilities that went with it. It's possible that the previous owners might have agreed to keep them but it would be very unusual for that to be the case.
As for could the just pay Oracle to license the code - they could have done at the time had Oracle, or Sun as it would have been at the time, agreed but they didn't. It would seem highly unlikely given that Oracle are currently suing them that they'd be willing to enter into such a license with Google now.
I think these are from the Java compliance test suite used to test that a Java implementation conforms to the specification. Sun had committed to releasing the compliance tests, but then dragged its feet and it never happened.
"In Florian's paper, he points these out as Sun PROPRIETARY / CONFIDENTIAL. However, it looks like several of the sources come from Sun's mmademo, linked here [java2s.com]. In this rendition of the document, each source file's license is a permissive one by Sun (i.e., not proprietary / confidential)."
IE, the header in the distribution may read incorrectly that the files are SUN proprietary.
The source code the guy links to comes from Apache Harmony, so if anyone actually has committed copyright infringement it could well be the ASF as the source of the infringement. I wonder if Oracle would go after Apache as well.
There was confusion about this when the first bits of code that were obviously Sun's implementations were found in Android code... However, according to Apache, Google slapped the Apache Harmony license into the headers themselves and the files were never really part of Harmony.
And the reporter is actually an ex-copyright and trademark attorney. So he does at least have rich domain knowledge in the law, and he has been following this case carefully.
The problem is we do not have the full story. For example, there is a certain clause of GPL2 that states if certain conditions are met that the full work does not have to be under GPL2 when a small portion may be under GPL2.
Plus, the aspect of when Java was GPL'd does that pertain to everything in the distribution or does at eh time Sun's disclaimers of some being not GPL'd hold legal weight pertaining to whether its a legal enforceable GPL license.
"If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works."
Correct me if I'm wrong, but it doesn't mean that you can copy small portions of GPLed code as you wish and use them in your projects; it means that the original copyright holder for those small portions can apply any license to them, which means that by default all rights are reserved by the original author of those portions.
These days college students think that one person doing ten people's homework is "collaboration", so I can imagine a lazy Googler decompiling some Sun class files. "After all, they're only tests, not real code."
[+] [-] rst|15 years ago|reply
Specifically, if we look at the PDFs from the original source here:
six of the seven Android files are in subpackages of "org.apache.harmony.security.tests". The Android version of Mueller's example number six, strangely, has no package declaration at all, but the name of the class (PolicyNodeImpl) at least is the same as one that has been identified as unit test code the last time it came up in this connection.(BTW, the "org.apache.harmony" package prefix doesn't necessarily mean that the ASF ever distributed the particular file in question; that PolicyNodeImpl.java file was distributed by Google with an Apache Harmony package declaration, but had never been distributed by the ASF itself.)
[+] [-] spiffworks|15 years ago|reply
[+] [-] ergo98|15 years ago|reply
[+] [-] shinkansen|15 years ago|reply
[deleted]
[+] [-] blinkingled|15 years ago|reply
That would have been better for two reasons - Oracle is screwing up bad with the JCP and it's going to hurt Java - May be Google could have been a better steward. Secondly Google relies so much on Java not only for Android but also for many other things - it is almost idiotic not to buy the IP.
I guess they had their reasons to not pursue - I can't imagine what those were.
[+] [-] rst|15 years ago|reply
[+] [-] guelo|15 years ago|reply
[+] [-] c2|15 years ago|reply
This is bad, but I still don't yet believe buying Sun would have been the better option.
[+] [-] fedd|15 years ago|reply
i was far from all this politics, but made a few google searches - is this about ASF leaving JCP? then, as far as i understood, these issues are all related, to Harmony, suing etc.
so maybe Java wouldn't be hurt? just specs would be changed more tyrannically...
(java my favorite language, don't make me sad :)
[+] [-] mbreese|15 years ago|reply
[+] [-] stevenbedrick|15 years ago|reply
[+] [-] DougBTX|15 years ago|reply
[+] [-] orangecat|15 years ago|reply
[+] [-] piotrSikora|15 years ago|reply
[+] [-] gawker|15 years ago|reply
I don't get one thing. I thought Java is supposedly open-source? How come there's proprietary source code? Or are these files part of a particular Java library developed by Sun that are not part of the Java that they open-sourced?
[+] [-] SeveredCross|15 years ago|reply
[+] [-] Tyrannosaurs|15 years ago|reply
As for could the just pay Oracle to license the code - they could have done at the time had Oracle, or Sun as it would have been at the time, agreed but they didn't. It would seem highly unlikely given that Oracle are currently suing them that they'd be willing to enter into such a license with Google now.
[+] [-] lepton|15 years ago|reply
[+] [-] fluidcruft|15 years ago|reply
[+] [-] slowpoison|15 years ago|reply
http://www.engadget.com/2011/01/21/android-source-code-java-...
[+] [-] joe_the_user|15 years ago|reply
http://tech.slashdot.org/comments.pl?sid=1960862&cid=349...
"In Florian's paper, he points these out as Sun PROPRIETARY / CONFIDENTIAL. However, it looks like several of the sources come from Sun's mmademo, linked here [java2s.com]. In this rendition of the document, each source file's license is a permissive one by Sun (i.e., not proprietary / confidential)."
IE, the header in the distribution may read incorrectly that the files are SUN proprietary.
[+] [-] Sephr|15 years ago|reply
[+] [-] maethorechannen|15 years ago|reply
[+] [-] georgemcbay|15 years ago|reply
https://blogs.apache.org/foundation/entry/read_beyond_the_he...
There was confusion about this when the first bits of code that were obviously Sun's implementations were found in Android code... However, according to Apache, Google slapped the Apache Harmony license into the headers themselves and the files were never really part of Harmony.
[+] [-] yanw|15 years ago|reply
[+] [-] kenjackson|15 years ago|reply
[+] [-] blub|15 years ago|reply
[+] [-] yuhong|15 years ago|reply
[+] [-] kprobst|15 years ago|reply
[+] [-] shareme|15 years ago|reply
Plus, the aspect of when Java was GPL'd does that pertain to everything in the distribution or does at eh time Sun's disclaimers of some being not GPL'd hold legal weight pertaining to whether its a legal enforceable GPL license.
[+] [-] dchest|15 years ago|reply
"If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works."
Correct me if I'm wrong, but it doesn't mean that you can copy small portions of GPLed code as you wish and use them in your projects; it means that the original copyright holder for those small portions can apply any license to them, which means that by default all rights are reserved by the original author of those portions.
[+] [-] RickRoll|15 years ago|reply
[deleted]
[+] [-] sudonim|15 years ago|reply
[+] [-] wmf|15 years ago|reply
[+] [-] grandalf|15 years ago|reply