3 ms·
IMHO, this is a much stronger case: Nothing in the licensing terms will prevent open source projects from creating and distributing their own compatible open s
by nl 15y ago
IMHO, this is a much stronger case:
Nothing in the licensing terms will prevent open source projects from creating and distributing their own compatible open source implementations of Java SE 6, using standard open source licenses
From JSR-270
http://www.jroller.com/scolebourne/entry/jcp_bonn_meeting_october_2010 http://www.jroller.com/scolebourne/entry/jcp_bonn_meeting_oc...
- wmf 15y agoThat doesn't help because Dalvik is not compatible (and to make it compatible would probably require making it too slow and bloated to run on phones).
- nl 15y agoIt depends what "compatible" means, though, doesn't it? If you include the Java bytecode-to-Dalvik compiler as part of the "system" it could be considered compatible.
- esrauch 15y agoI'm not sure that the Java bytecodoe-to-Dalvik compiler actually completely Java SE 6 compatible (eg that it is a superset), but I think that is irrelevant since their licensing actually prohibits supersets. This is why Sun was able to force Microsoft to discontinue their JVM; it had nonstandard features in it, and therefore their licensing wouldn't be valid.
- nl 15y agobut I think that is irrelevant since their licensing actually prohibits supersets Android/Dalvik isn't a licensed Java implementation so the irrelevance is irrelevant ;) The original statement referred to the license to use a Java compatible API, not to be a Java licencee.
- wmf 15y agoIt depends what "compatible" means, though, doesn't it? It's fairly well defined by JSRs 270 or 216, and Android isn't even close. For example, the GUI libraries are quite different. If you include the Java bytecode-to-Dalvik compiler as part of the "system" it could be considered compatible. I don't think the compiler runs on the phone, so it doesn't count.