One tricky aspect is the licensing side on MacOS, which could cause
some difficulties, so we'll probably want to stick with an Oracle JDK
there.
Another tricky aspect is the product impact. We're certainly not going
to switch to a totally different JDK in the middle of a release, so
for ICS we'll be sticking with the Oracle JDK as well. This is really
bad when combined with the issue above, as we risk seeing different
behaviors depending on whether Android was built with MacOS or Linux.
Finally, we need to fix the build, and that needs to be done by
someone who understands OpenJDK well enough to figure out why OpenJDK
fails to compile Android. Note that if we need to workaround the
OpenJDK incompatibility in Android, we won't be able to go back in
time and fix past releases and those will continue to require the
Oracle JDK.
JBQ
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-...@googlegroups.com
> To unsubscribe from this group, send email to
> android-buildi...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
--
Jean-Baptiste M. "JBQ" Queru
Software Engineer, Android Open-Source Project, Google.
Questions sent directly to me that have no reason for being private
will likely get ignored or forwarded to a public forum with no further
warning.
JBQ
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-...@googlegroups.com
> To unsubscribe from this group, send email to
> android-buildi...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
--